as someone fairly new to larger python projects, working in a team too - why does it seem like I’m always in dependency hell? Sometimes things work with venv until I forget and a notebook needs something else. Or a diff type of proj because mlflow wanted another kind of env manager?

[–] Incblob@lemmy.world 8 points 1 month ago (1 children)

6 years of python and I've never really had that problem, also working on larger projects. Use poetry or uv and you'll probably be fine. Unless you're doing something strange with your dependencies. The only thing I would say is non trivial is updating the dependencies. And if a library has a bug or something you have to downgrade for. You can specify dev dependencies for notebooks and such. I've not heard of mlflow having a problem with a manager. Perhaps you're in a cloud environment and don't have access to poetry for example?

[–] flandish@lemmy.world 1 points 1 month ago (1 children)

never used poetry. just venv, virtualenv and such. I guess I just don’t know the current era’s idiomatic way of doing things. I’m more familiar with java/mvn, rust, etc. It seems like every manning book on a pythonic tool has a different way the author setup the env. to be expected sure. I just need to grok and settle into my own. :)

just learning is all. :) appreciate the reply!

[–] sugar_in_your_tea@sh.itjust.works 5 points 1 month ago

Poetry/uv is similar to Rust's cargo. You specify your direct dependencies in a TOML file and their version constraints and the tool takes care of the rest.

load more comments (11 replies)