search

mosquito / aiohttp-xmlrpc

XMLRPC for aiohttp
MIT License
34 stars 19 forks source link

declare support for only py>=3.5 #32

Closed graingert closed 4 years ago

graingert commented 4 years ago

it might be worth re-releasing 0.7.7 as 0.8.2 then releasing this PR as 0.9.0

or yanking the 0.8.1 release https://www.python.org/dev/peps/pep-0592/

graingert commented 4 years ago

from PEP-0592

One of the main scenarios where this may happen, is when dropping support for a particular version of Python. The python-requires metadata allows for dropping support for a version of Python in a way that is not disruptive to users who are still using that Python. However, a common mistake is to either omit or forget to update that bit of metadata. When that mistake has been made, a project really only has three options:

    Prevent that version from being installed through some mechanism (currently, the only mechanism is by deleting the release entirely).
    Re-release the version that worked as a higher version number, and then re-release the version that dropped support as an even higher version number with the correct metadata.
    Do nothing, and document that people using that older Python have to manually exclude that release.

With this PEP, projects can choose the first option, but with a mechanism that is less likely to break the world for people who are currently successfully using said project.