this post was submitted on 16 Jul 2023
659 points (92.3% liked)

Programmer Humor

32571 readers
506 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
 

No offence

you are viewing a single comment's thread
view the rest of the comments
[–] abraxas@lemmy.ml 1 points 1 year ago (1 children)

How so? The companies I worked for were using venv's but nothing that could help with standards.

Using a private npm repo, I can actually do aninstall of a library I want to use and it'll refuse to install if that library isn't already approved for use by the organization, and if it is/does, it will install only the approved version. Further, I still don't have any of the libraries installed I don't want (even secure-seeming unnecessary code is a potential risk and unnecessary). The last 2 places I worked that used python used venv's, but the pip requirements.txt file was still fairly hard to keep regulated.

[–] Bruce@lemmy.ml 2 points 1 year ago* (last edited 1 year ago) (1 children)

From approved environments: pip freeze > requirements.txt ?

[–] abraxas@lemmy.ml 1 points 1 year ago

So let's say I want to add a library not currently being used in this project, but that might have been approved for another project in another repo? How does pip freeze solve that problem? Do python users endorse a "every single python app in the entire org should use the same requirements.txt" mindset? Or what am I missing?