@kirby @burner @mikuphile You can do a lot with the standard library (since it's "batteries-included") but CPython is just slow as aids by design. And virtual envs and packages are such a mess because of the lack of proper version number specifications as burner mentioned, but also because for a long time, there was no standard way for making a package for python. there was setup.py files, then setup.cfg files, pyproject.toml files to declare package metadata. And various tools to actually do the packaging from setuptools, poetry, hatch, meson, etc. Also because a lot of popular packages rely on C extensions for speed, the packaging process can get sextra complicated. Pip also doesnt do the best version number resolution for installing packages so other tools like conda popped for managing dependencies but that is bloated in its own way and another rabbit hole...

compare this to something like R, where they made sure there was a coherent standard for packaging pretty early on (not that I like R much, but its a comparable language for certain use cases).



Also for requests see stackoverflow.com/questions/62599036/python-requests-is-slow-and-takes-very-long-to-complete-http-or-https-request.