Can the python packaging story get much worse? It's a huge blemish and way too much fragmentation and after market solutions, and of course the mental overhead of virtualenvs or else you clobber your environment.
One thing I keep hoping will get advanced in is PEP-582 to incorporate a local __pymodules__ folder since it would be nice if getting a python project up and running was as easy as node or php.
We don't currently have any plans to address this issue specifically -- this is a good use-case for using a general package manager like conda rather than something Python-specific like pip.
I don't think any language actually solves this, and to be honest I'm in favour of the "it's someone else's problem" approach. Python packaging is complex enough without having Python try to actually solve this massively complicated secondary problem.
Hopefully the role prioritizes blessing existing good practices and creating migration paths and decent interop vs creating new things and pulling an xkcd 927.
I know everyone's got their favourite thing to be fed up about in the Python packaging ecosystem, but for me it's definitely `setup.cfg` vs `pyproject.toml`.
I'm happy to see this. The python packaging ecosystem is frustratingly nonstandardized, particularly the split between conda and pip. Now that the Python 2->3 migration has mostly been dealt with, hopefully the community is able to improve the packaging situation.
Python shared to two or more computers utterly devastating. I left python a long time ago when I couldn't get my code to easily repeat on three of my computers at three locations for work. I also tried a simple program to use on 100 computers at 40 different locations was a disaster (Luckily no one knew)
I actually used Racket and it was a the easiest packaging system I ever used and had smooth sailing on projects that I used for pet projects that saved me tons of time.
Is the need for a project manager or a product manager?
I’m pretty sure that python is going to have an ongoing need for attention to be paid to its packaging ecosystem. Approached holistically, this would include the documentation and other aspects of developer experience.
is there any good reference article/blog that talks about various python package managers, their history, use cases and the current trends in industry? Is there any specific tool that's becoming more accepted standard among developers?
40 comments
[ 4.0 ms ] story [ 91.6 ms ] threadI expect that corporations will get even more power with full time employees and very little will be accomplished.
One thing I keep hoping will get advanced in is PEP-582 to incorporate a local __pymodules__ folder since it would be nice if getting a python project up and running was as easy as node or php.
Of course it can get much worse, see where Python packaging was ~5 years ago.
This is a very strong statement. Do you have any details about what you're claiming or supporting evidence?
This joins our other open position for a CPython Developer-in-Residence: https://pyfound.blogspot.com/2021/04/the-psf-is-hiring-devel...
Note that this is for a full-time project and community manager, not a developer (although there may be some overlap).
Also I'm not sure how much he'd enjoy being a project manager. :)
E.g. install psycopg2 <- requires apt-get install libpq (and that's just on Debian) but python packaging has no consistent way of managing this.
I know everyone's got their favourite thing to be fed up about in the Python packaging ecosystem, but for me it's definitely `setup.cfg` vs `pyproject.toml`.
https://www.python.org/dev/peps/pep-0621/
https://github.com/python/mypy/issues/5205#issuecomment-4102...
I really don't like how projects are being broken
Python shared to two or more computers utterly devastating. I left python a long time ago when I couldn't get my code to easily repeat on three of my computers at three locations for work. I also tried a simple program to use on 100 computers at 40 different locations was a disaster (Luckily no one knew)
I actually used Racket and it was a the easiest packaging system I ever used and had smooth sailing on projects that I used for pet projects that saved me tons of time.
I’m pretty sure that python is going to have an ongoing need for attention to be paid to its packaging ecosystem. Approached holistically, this would include the documentation and other aspects of developer experience.
This is long overdue.
I have always envisaged that it would only happen if a corp steps in and wished I had the means.
Kudos to Bloomberg for stepping up and hope other corps add to the effort for actual programming