3 ms·
For what it’s worth – A small technical fact: It is entirely possible to use poetry to determine the precise set of packages to install and write a requirement
by AnthonBerg 2y ago
For what it’s worth – A small technical fact:
It is entirely possible to use poetry to determine the precise set of packages to install and write a requirements.txt, and then shotgun install those packages in parallel. I used a stupidly simple fish shell for loop that ran every requirements line as a pip install with an “&” to background the job and a “wait” after the loop. (iirc) Could use xargs or parallel too.
This is possible at least. Maybe it breaks in some circumstances but I haven’t hit it.
- macinjosh 2y agoThat poor package server getting 39 simultaneous pulls at the same time from one user.
- AnthonBerg 2y agoThis is indeed something to consider! Not as an excuse for bad behavior but rather to consider infrastructure and expectations: The packages might be cached locally. There might be many servers – a CDN and/or mirrors. Each server might have connection limits. (The machine downloading the packages miiiiiight be able to serve as a mirror for others.) If these are true, then it’s altruistically self-interested for everyone that the downloader gets all the packages as quickly as possible to be able to get stuff done. I don’t know if they are true. I’d hope that local caching, CDNs and mirrors as well as reasonable connection limits were a self-evident and obviously minimal requirement for package distribution in something as arguably nation-sized as Python. And… just… everywhere, really.