Re:Learning Go as a Python Developer: The Good and the Bad
by pletnes on Monday July 18, 2022 @03:23PM
(#32142370)
Sure can pin versions, it’s easy too, if you just use «pip freeze».
[ Parent
| on HN ]
Re:Learning Go as a Python Developer: The Good and the Bad
by pid-1 on Monday July 18, 2022 @04:36PM
(#32143323)
Now you lost track of which are your top level dependencies and which are dependencies of dependencies.
Re:Learning Go as a Python Developer: The Good and the Bad
by _Wintermute on Tuesday July 19, 2022 @06:20AM
(#32149618)
Then use pip compile.
Re:Learning Go as a Python Developer: The Good and the Bad
by pid-1 on Tuesday July 19, 2022 @07:43AM
(#32150182)
Sure. Or poetry, or pipenv, or whatever third party packaging system you enjoy.
The whole point of GP is that python lacks a native sane packaging system, which I agree.
Re:Learning Go as a Python Developer: The Good and the Bad
by pletnes on Tuesday July 19, 2022 @10:52AM
(#32152357)
Python has several. It’s overall a good thing. It’s the reason you can package both one-file scripts and huge C++ / Fortran packages, which is the reason it has become a huge language in HPC / ML / AI / astronomy / data science / …
I agree that it makes life more confusing for newbies, though.
Re:Learning Go as a Python Developer: The Good and the Bad
by ska on Monday July 18, 2022 @05:32PM
(#32144125)
That only solves part of the problem.
something like poetry's approach is the right one here; you need a list of core dependencies (not derived ones), you need a solver for when anything changes to find a new set of viable versions, and you need a lock file of some sort to uniquely & reproducible construct an environment.