3 ms·
I 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 d
by zbentley 4y ago
I 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".
- Kwpolska 4y ago"virtualenvs suck, why can't it be like NPM?" is a specific problem and a specific solution. The problem being having to manage venvs (which have many gotchas and pitfalls, and no standarization), and the solution is to replace those with packages being installed into the project folder with standardized and well-known tools.
- qbasic_forever 4y agoKeep an eye on https://peps.python.org/pep-0582/ https://peps.python.org/pep-0582/ it's a proposal to add local directory/node_modules-like behavior to package installs. It stalled out a few years ago but I heard there is a lot more discussion and push to get it in now. I think if this PEP makes it in then like 90% of people's pain with pip just completely goes away almost overnight. Love it or hate it the NPM/node_modules style of all dependencies dumped in a local directory solves a _ton_ of problems in the packaging world. It would go a long way towards making the experience much smoother for most python users.
- jogjayr 4y agoI did a proof-of-concept for this a few years ago: https://github.com/jogjayr/pykg https://github.com/jogjayr/pykg It literally uses npm, the NPM registry, and node_modules for Python dependency management.