“Python's batteries are leaking”

Re:“Python's batteries are leaking” by porker on Sunday May 19, 2019 @04:29AM (#19952192)

> and so (nowadays) you're going to set up requirements.txt and virtualenv and whatever anyway

If only that were the norm amongst long-tail python users. Heck I don't do it; I have the anaconda distribution installed on Windows and when I need to do a bit of data analysis hope I have the correct version of packages installed.

Making this core to the python workflow (bundling virtualenv? updating all docs to say "Set up a virtualenv first"?) is the first required change, before thinking about unbundling stdlib

[ Parent | on HN ]

Re:“Python's batteries are leaking” by schlenk on Sunday May 19, 2019 @06:25AM (#19952548)

I develop in python since 10+ years. And setting up a virtualenv only happens when developing patches for 3rd party packages. (due to the other commercial environment that doesn't work with venvs).

And it is a totally miserable experience on Windows, every single time.

[ Parent | on HN ]

Re:“Python's batteries are leaking” by pas on Sunday May 19, 2019 @06:28AM (#19952561)

The stdlib would still ship with Python I presume, it would be simply updatable. But that doesn't mean it wouldn't work without a "requirements.txt" (use Pipenv which is light-years ahead).

[ Parent | on HN ]