vphilippon
commented
2 years ago Bonus:
If you can manage to somehow update correctly the metadata on pypi, instead of publishing a 30.1 and yank 29.0 and 30.0, it would be a wonderful gift for me.
If not, that's ok, no worries, that situation I have is on me.
(For your potential curiosity: I'm stuck in a position where I am still using devpi<6 (for unfortunate reasons), which didn't recognize the yank metadata, and that's in no way your responsibility. But if in this very specific case the metadata can be updated by a republish or something, since the property is there in the code, I'd be saved a pass through a bunch of projects on my end to put a bunch of downpins :) .)
miketheman
Hello!
I see that the
python_requires=">=3.6"is there in the setup.py, but if you look on Pypi, the "Requires: Python >=3.6" metadata is missing. See https://pypi.org/project/readme-renderer/30.0/ And this is not only a visual bug: My recent enough version of pip on Python 2.7 (20.3.4, so aware of pypi metadata) will hapilly installreadme-renderer 30.0(ex: when installingtwine:) ).I'm not 100% sure of the cause, but in other projects I've seen this happen when the pipeline (or the maintainer) was using an outdated version of
twineIIRC (although you're all likely more aware of how this works than me :P ).In terms of impact right now,
twine 1.15.0(my main usage example, latest version supporting py2.7) still works even with the "unsupported"readme-renderer 30.0installed. So nothing seems on fire at the moment from my POV. Still something worth adressing for the future I think.Let me know if I can help with any more details. Cheers and good luck!