Re:Java at 30: The Genius Behind the Code That Changed Tech
by icedchai on Friday May 16, 2025 @06:44PM
(#44010444)
I rarely run into issues when using Poetry. If you use pip, add packages to requirements.txt willy-nilly and don't pin versions then you are asking for trouble.
[ Parent
| on HN ]
Re:Java at 30: The Genius Behind the Code That Changed Tech
by myko on Friday May 16, 2025 @09:45PM
(#44011417)
i like poetry though i've moved to uv - both work really well
Re:Java at 30: The Genius Behind the Code That Changed Tech
by icedchai on Friday May 16, 2025 @10:58PM
(#44011708)
I've heard great things about uv. I plan to try it for my next project.
Re:Java at 30: The Genius Behind the Code That Changed Tech
by bornfreddy on Saturday May 17, 2025 @12:18AM
(#44012013)
I use pipenv and it kind-of-works. Will try uv or poetry though - which one would you recommend?
Re:Java at 30: The Genius Behind the Code That Changed Tech
by dwood_dev on Saturday May 17, 2025 @01:50AM
(#44012310)
UV. Using it as the exec target for python (UV script) is great. Dependencies declared at the top, now I have executable files in something better than bash.
I no longer shy away from writing <500 LOC utility/glue scripts in python thanks to uv.
Re:Java at 30: The Genius Behind the Code That Changed Tech
by myko on Saturday May 17, 2025 @11:00PM
(#44018681)
I can't recommend uv enough. It's so fast, and uvx is so useful to run a random Python CLI tool. If you want to do things like you're accustomed to with pip you just `uv pip ...`
Re:Java at 30: The Genius Behind the Code That Changed Tech
by LtWorf on Saturday May 17, 2025 @01:37AM
(#44012264)
Poetry doesn't fix the fact that python removes modules from the standard library every release.