4 ms·
Meanwhile I've been using vanilla pip+virtualenv with possibly a Makefile and direnv (.envrc) for convenience for years and have zero issues with it. When I oc
by p5a0u9l 4y ago
Meanwhile I've been using vanilla pip+virtualenv with possibly a Makefile and direnv (.envrc) for convenience for years and have zero issues with it.
When I occasionally encounter a version compatibility issue, I pin the offender in setup.py, done.
If reproducible builds/distributions are important, then I add a Dockerfile.
I will say that I primarily develop applications, not libraries meant for wider consumption. If I do create a library, it's for my own narrow use case. It seems like some of the value in these modern frameworks is reducing complexity over multiple supported versions and platforms.
I'm not saying my workflow is in the mainstream necessarily, but the standard community tooling has been fine for me.
- iamwpj 4y agoSimilarly I consolidated my Makefile process into a CI. Having a workflow that is: 1. Set up venv of this version or greater 2. Install packs from requirements.txt I think the repeatability and simplicity combo of this is my favorite approach. I'm all for standard tooling wherever possible.
- jefurii 4y agoCame here to say the same thing. Set up a Makefile to build my project using pip&virtualenv, and make .deb packages using FPM. It's totally old-skool but it Just Works(TM).