Pypi.org is running a survey on the state of Python packaging
1–10 of 193 posts
Re: Pypi.org is running a survey on the state of Python packaging
#2I imagine many of you have feedback that could be useful to folks making decisions about the future of Python packaging, a common subject of complaint in many discussions here.
Remember not to just complain, but to offer specific problems/solutions--i.e. avoid statements like "virtualenvs suck, why can't it be like NPM?" and prefer instead feedback like "the difference between Python interpreter version and what virtualenv is being used causes confusion".
Re: Pypi.org is running a survey on the state of Python packaging
#3The survey is at https://www.surveymonkey.co.uk/r/M5XKQCT.
Re: Pypi.org is running a survey on the state of Python packaging
#4Is there any hope that even if there emerges a consensus package management solution going forward, old packages will be easily portable to it?
Re: Pypi.org is running a survey on the state of Python packaging
#5I am pretty happy with PyPi/pip, it is an easy way to distribute Python and C++ code wrapped in a Python extension to others. For a C++ developer it is becoming harder to distribute native executables, since MacOS and Windows require signing binaries. Python package version conflicts and backwards incompatibility can be an issue.
Re: Pypi.org is running a survey on the state of Python packaging
#6Is there any hope that even if there emerges a consensus package management solution going forward, old packages will be easily portable to it?
Nothing will improve as long as the Python powers insist on packaging being an exercise for the community.
Re: Pypi.org is running a survey on the state of Python packaging
#7XKCD's opinion:
Re: Pypi.org is running a survey on the state of Python packaging
#8I wish there is some package manager in middle of conda and pip. Conda is too strict and often get stuck in SAT solving. pip doesn't even ask when reinstalling a version currently being used.
Edit: Typo: reinstalling a version of package currently being used
Re: Pypi.org is running a survey on the state of Python packaging
#9I wish there is some package manager in middle of conda and pip. Conda is too strict and often get stuck in SAT solving. pip doesn't even ask when reinstalling a version currently being used. Edit: Typo: reinstalling a version of package currently being used
> pip doesn't even ask when reinstalling a version currently being used.
Just as an explanation: a "version" in Python packaging can come from one of many potential distributions, including a local distribution (such as a path on disk) that might different from a canonical released distribution on PyPI. Having `pip install ...` always re-install based on its candidate selection rules is generally good (IMO), since an explicit run of `pip install` implies user intent to search for a potentially new or changed distribution.
Re: Pypi.org is running a survey on the state of Python packaging
#10Is there any hope that even if there emerges a consensus package management solution going forward, old packages will be easily portable to it?
Is there a problem with the package format itself though? There are lots of serious problems tied to distribution rather than package format which would make the experience way easier especially for beginners and people used to other package managers...
lacking binary wheels on PyPI, problems with shipping project with dependencies, confusion about there being multiple "package managers" (pip, pip-tools, poetry, pipenv, conda) and multiple formats of dependency lists (setup.py, setup.cfg, requirements.txt, pyproject.toml, ...), sys.path associated confusion (global packages, user-level packages, and anything specified in PYTHONPATH, ...)