lkpmag.blogg.se - Packaging an os x shell script

PowerShell Execution Policies in Standard Images.It could be more strict than ByPass but I haven't bothered. Ironically it still uses tox for testing :-)

I haven't looked much into this, tho I have came across rituals. Writing a well behaved setup.py is not a walk in the park and a custom test command doesn't bring any advantages. See: substitutions for positional arguments in commands. This is not necessarily tox specific but I'm mentioning it because it can make installing some dependencies so much faster: use wheelhouses preloaded with the deps. There are probably other tools I haven't considered, feel free to comment, if you still think there's something better than tox. Read this terrifying list of Bash pitfalls. Besides them being unportable and hard to read, I'm pretty tired of seeing people doing accidental rm -rf / (because shell scripts don't error or uninitialized variables by default) or having some other obscure bugs.

Shell scripts: this is the worst of the lot.

Invoke (or its alternatives): again, this is not designed for testing python packages - it's something way more generic and you'd have to either write everything yourself or use a 3rd party task libraries.

You'd still need to do lots of shell scripting to achieve what tox does out of the box.

Make: tricky to install on Windows and it's not really designed for testing python packages.

There are some alternatives to tox, however, they have some disadvantages:

Reduces that ugly shell script boilerplate.

It's portable on Linux, OS X and Windows.

Just run tox and you're set - no more reading dozen install, setup and testing instructions just to run the tests. There are several advantages of using tox: