4 ms·
Great read! I see a few approaches I'd be interested in adopting. Nox sounds particularly useful for tooling consistency across development environments. It's
by languagehacker 6y ago
Great read! I see a few approaches I'd be interested in adopting. Nox sounds particularly useful for tooling consistency across development environments.
It's worth noting that this a rather opinionated toolset, and that we shouldn't mistake opinionated for hypermodern. You could replace poetry for pipenv (particularly now that it's being maintained again...), and I tend to prefer unittest to pytest. The further into it you get, the more opinionated it is -- for instance, code coverage support and CI/CD is not one-size-fits-all, but the choices of CodeCov and GitHub Actions are nicely illustrative.
- kingosticks 6y agoI often end up frustrated when jumping back from pytest to old projects that are still using unitest I really like pytests's fixtures and it's caplog stuff. Out of interest, what do you prefer in unittest?
- fastball 6y agoPlease no pipenv. A horribly managed project with worse design choices than Poetry. And a confusing name to boot (it makes it sound like a clean bridge between pip and pyenv, but it's definitely not). On top of everything you can throw in Ken Reitz's ego. Literally the only reason pipenv gained traction is because there are still an unnerving number of people in the Python community that think Ken Reitz shits gold, when he is clearly more of a one-hit-wonder (love requests btw). Even the testimonials are self-important. > Pipenv is finally an abstraction meant to engage the mind instead of merely the filesystem. Like, really? I want to interpret that as a joke, but I don't think it is. Poetry should be the future of Python dependency management. I'd like to forget pipenv ever happened. Unfortunately since PyPA took pipenv under its wing, that might not happen.