Hacker News new | past | comments | ask | show | jobs | submit login

This is very bad advice. Lots of nontrivial things aren't automatically compatible with the latest Python minor version. PyTorch for instance doesn't support Python 3.10 and it's been five months since the stable release (ten months since the first beta). For anything nontrivial, you almost always want to specify a minor Python version.



Why is this bad advice?

The PyTorch scenario is an exception, not the rule, and the users of PyTorch should know not to use unsupported versions.

> For anything nontrivial, you almost always want to specify a minor Python version.

Depends on how you define "trivial".


It’s non-optimal advice because PyTorch is not the only library that runs into problems like this, because Python does not follow semver. You should pin to an X.Y release, and let .Z releases update automatically (which is where your security updates fall)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: