![]() The problem with Joe is that he’s never been that keen on writing documentation. He commits the code to the team’s version control system. He’s a responsible ninja, so he writes some tests, and he creates a requirements.txt file. Let’s say that 10X Ninja Techlead Joe Smith writes a Python library to help his team do something - say a CLI tool for the team’s To explain more it’s useful to consider a scenario. Or its slightly more sophisticated cousin virtualenvwrapper? Surely you don’t want me to learn yet another tool? ![]() Which can provoke the knee-jerk reaction of…what’s wrong with plain old virtualenv? Tox is a generic virtualenv management and test command line tool Which sounds great and all, but doesn’t tell us much. ![]() It is part of a larger vision of easing the packaging, testing and release process of Python software. Tox aims to automate and standardize testing in Python. ![]() The value of tox is pretty opaque at first. Here is the accompanying code repo on Github In this detailed post I’m going to delve into why tox can save you time and pain, how it works, and then go through some concrete code examples. tox fixes this problem (and quite a few others). But that’s probably not good enough when teammates and build servers need to run your Python code. Most people in tech will have heard the classic “it works on my machine” excuse response, one so classic that it has
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |