3 ms·
I think that the "real" problem here is that Python's package management and apt/yum don't really interface well. I've built .debs for Python packages before, a
by pyre 11y ago
I think that the "real" problem here is that Python's package management and apt/yum don't really interface well. I've built .debs for Python packages before, and it was a huge pain in the ass, even with the scripts and automations that I was able to find for it.
It's 'simple' for me to build a virtualenv in a directory with `pip install -r requirements.txt` in my source repo, but everything I've read about making those virtualenvs portable (even moving them between directories on the same server you built them on) is that it is a path fraught with peril.
- teacup50 11y agoThe 'real' problem is that you shouldn't have to install dependencies in OS-level locations for an application-level product. In other words, the app should be able to bundle dependencies without having to use a crazy opaque container system, and those dependencies should be easily auditable. This is the case for Java, where dependencies are 1) bundled with the application, 2) declared explicitly, 3) signed, 4) centrally managed with maven repository software.
- pyre 11y agoIn Python, you get similar things with the exception of "bundled with the application" and IIRC "signed" only happens when uploading to the Python Package Index.