> I don't want to have virtual environments and learn what the difference between pip, poetry and uv is. I don't care. I just want to run the code.
The author is right that every user approaching Python shouldn't need to figure this out. However, I do strongly believe every blogger setting out to write an opinion piece on this topic should at least attempt to figure this out before writing their article.
Obvious ignorance does not a compelling point make. Especially when uv solves literally all of the problems you're describing.
> Especially when uv solves literally all of the problems you're describing.
How does uv solve the “write once, run anywhere” problem like go?
(I’m not being sarcastic, I don’t know that much about uv and perhaps am lacking the mental model for understanding this)