Zoltan Kochan
417601da4a
Every file an index lists is parsed when a distribution's candidates are read, so one release publishing a `Requires-Python` that is not a version specifier aborted the whole resolution. `openpyxl` 3.0.0 through 3.0.7 publish `>=3.6,`, which put `openpyxl` out of reach of every project, at any version: a release is immutable, so nothing the project does can correct the value. An unreadable `Requires-Python` is now read as if the release declared no interpreter range, which is what pip does. All three readers of the field agree on that: the index page a candidate comes from, the wheel metadata a resolution steps through, and the marker a solved lockfile writes. Closes pnpm/pnpm#14910
322 B
322 B
pacquet, @pnpm/pnpr
| pacquet | @pnpm/pnpr |
|---|---|
| patch | patch |
Python resolution no longer fails on a release whose Requires-Python is not a version specifier, such as the trailing comma in openpyxl 3.0.x. pnpm now reads such a value as if the release declared no interpreter range #14910.