3 ms·
The tl;dr: * pip is the tool for installing packages * pipenv is the tool for managing an environment in which you develop a package (and wraps pip and virtua
by ubernostrum 9y ago
The tl;dr:
* pip is the tool for installing packages
* pipenv is the tool for managing an environment in which you develop a package (and wraps pip and virtualenv to make that convenient)
* twine is the tool for uploading packages to the Python Package Index
- Rotareti 9y agopip, pipenv, pipfile, pipfile.lock, twine, project.toml, setup.py, setup.cfg, setuptools, requirements.txt... I'd prefer a proper package manager.
- ubernostrum 9y agoSo build one. If it's good, people will use it!
- Rotareti 9y agoLuckily I don't have to! I rather contribute to this, which looks promising: https://github.com/sdispater/poetry https://github.com/sdispater/poetry
- no_wizard 9y agoOh man I did not know this existed I am completely aligned with this. Easily this is what I love About the python community is that so many awesome folks just step up and do something when they seen deficiencies vs waiting for someone else to get around to it (lookin at you Swift) I myself am prototyping a tool chain that will compile python to static C code and then compile that (with the interpreter embedded) into a binary that can be easily distributed. Nothing on GitHub yet but it’s what I hope one day soon will fix the distribution story once and for all!
- BerislavLopac 9y agoI'd love to see something like what you're describing, but why C? How about Rust or something similar, closer to Python's paradigms?