Closed Volodimirich closed 2 years ago
Thanks for reporting! @snk4tr can you please take a look?
@zakajd I'm on it 👍
The problem is that this string is not a valid semver version. It seems that PyTorch follows a much broader versioning protocol PEP-440 and uses versions from the broader scope for automated releases (such as NGC container ones). I am implementing a broader parser to handle that.
Lol, it is even funnier. Actually, PEP 440 versions do not include all valid Simver versions and vice versa e.g.:
"1.2.3-alpha.1.2+build.11.e0f985a"
is a valid Semver but not PEP 440"1.10.0a0+ecc3718"
is a valid PEP 440 but not SemverHence, since PyTorch mixes up both systems, we gotta have parsers for both systems.
Bug in __version_tuple() function, for pytorch version 1.10.0a0+ecc3718
Steps to reproduce the behavior:
Screenshot: