overview for rothaine

[–] [email protected] 5 points 9 months ago (1 children)

do {
  /* something */
} do hast {
  /* something */
}

Get it together in c/[email protected]

[–] [email protected] 4 points 10 months ago

What in the

fucking delicious in c/[email protected]

[–] [email protected] 3 points 10 months ago

Hot take

Crazy bread > cheesy bread

Package managers be like in c/[email protected]

[–] [email protected] -2 points 1 year ago

Sure, for a new project. But when inheriting code I'm not in a position to pick.

The point is that the state of python package managers is a hot fucking mess compared to npm. Claiming that "npm is just as bad" (or worse) honestly seems ridiculous to me.

(And isn't pip/venv the one the requirements.txt one? Completely flat, no way to discern the difference between direct dependencies and sub-dependencies? No hashes? Sucks when it's time for updating? Yeah no thanks, I'd like a proper lock file. Which is probably why there are a dozen other tools.)

dark tower deck supremacy in c/[email protected]

[–] [email protected] 8 points 1 year ago

Knees, actually

Package managers be like in c/[email protected]

[–] [email protected] -2 points 1 year ago (2 children)

More like rtfms. I really didn't feel like learning 20 different tools for repos my team didn't touch very often.

Package managers be like in c/[email protected]

[–] [email protected] -2 points 1 year ago* (last edited 1 year ago) (5 children)

Sorry but nah. My last job we had a couple different python microservices. There was pipenv, venv, virtualenv, poetry, Pipfile.lock, requirements.txt (which is only the top level???), just pure madness

Apparently all this shit is needed because python wants to install shit globally by default? Are you kidding?

Well, we also had a couple node microservices. Here's how it went: npm install. Done.

Afraid you fucked something and want a clean environment? Here's how you do it with node: delete node_modules/. Done.

Want a clean python env? Uhhhhhhhh use docker I guess? Maybe try reinstalling Python using homebrew? (real actual answers from the python devs who set these up)

Well what's currently installed? ls node_modules, or use npm ls if you want to be fancy.

In python land? Uhhhhhh

Let's update some dep--WHY AREN'T PYTHON PACKAGES USING SEMVER

So yeah, npm may do some stuff wrong, but it seems like it does way more shit right. Granted I didn't really put in the effort to figure out all this python shit, but the people who did still didn't have good answers. And npm is just straightforward and "works".