@SynAck btw, @glyph makes this topic engaging and coherent: https://youtu.be/kcfERM6fcgU I know it's beyond your use case, but if the author of the the code you downloaded had seen this, your life today might be easier.
@SynAck@blaise there is unfortunately a lot of diversity in different approaches and even more unfortunately there are actually good reasons for using different tools in different circumstances. But as @hynek explains in his project layout 2025 video, you can get started with a standards-based approach and avoid going too deep on any particular tool, then use uv for basic setup unless you have a more specialized need https://www.youtube.com/watch?v=mFyE9xgeKcA
@blaise I'm actually just working through code from a book and am trying to get a handle on which environment tool I should use to give me a good leg-up when I start writing my own programs and projects. This book is fairly basic, with a more advanced one to follow.
I'm just trying to get used to the environment and "how things are generally done" these days in Python-land. :bec_wink:
@SynAck@blaise personally my projects revolve more around a pip-compile/manually making my own virtualenvs with pip workflow right now, but as long as everything is described with a pyproject.toml that enumerates dependencies, switching around between that and uv or poetry or pdm or flit is only a few minutes’ work if I need to do that for some reason