6 ms·
> I'm saying that the build tool should run unit tests Building in Python is little more than creating a .tar.gz (or other format) of your source directory. Te
by orf 11y ago
> I'm saying that the build tool should run unit tests
Building in Python is little more than creating a .tar.gz (or other format) of your source directory. Testing is very different and is very specific per project.
Anyway, this whole discussion is pointless, you just need to run 'python setup.py test' before you run 'python setup.py bdist'. Is that so hard? If you really want you can edit your setup.py to do this first.
- lmm 11y agoI can edit my setup.py but I can't edit everyone else's. Defaults matter. My experience is that the average quality of random PyPI package is... not great, and I can't help thinking the anemic state of python build/project tooling is partly to blame.
- ubernostrum 11y agoThe tooling is fine for that kind of stuff. In fact there's an almost embarrassing number of different ways to do what you want (you can use your own local build/test/release, probably scripted with tox and other tools, or you can have Travis CI do it for you automatically, or...). I personally take a sort of halfway approach: I use Travis heavily for public documentation of the fact that my packages are fully tested and passing, but stop short of having it automatically release to PyPI for me when I tag a new version. But in general, the tools can't fix the fact that PyPI is not heavily curated. Any non-curated package repository will have the issues you're complaining about, even if the tools default to doing what you want them to do.
- lmm 11y agoMaybe. Maven Central isn't really curated, but by being associated with maven it encourages packages to run tests as part of the release process, and also to follow some standards in terms of e.g. package metadata pointing to the source repository and release tag in a standard format.