Closed pawamoy closed 2 years ago
I literally just found out about a pretty sizeable chunk of things not working in 3.7 2 days ago. Not sure if they are "worth" fixing, as a lot of it will introduce redundant reimplementations of things that are already part of stdlib Python in later versions, but doing it in a less efficient manner.
It seems that 3.7 EOL is set in about a year, so there is probably still a lot of people using it. Of course, it would be ideal to support it but I don't want to restrict the rest of the users as a result.
Is there any way you can use >=3.8
for now?
Sure, I'm just testing docs building on 3.7 up to 3.11. I can drop 3.7 for this one project :slightly_smiling_face:
You should still update python_requires
in setup.py (whether you add support for 3.7 later or not) :smile:
Yeah, it's a big conundrum at the moment. pypistats
reports 5% of downloads of the project on 3.7, though 50% is annotated as null. This issue, as far as I know, should be present for releases months back, so the fact that no one has pointed it out until this thread seems to suggest either a very quiet population of developers, or practically no usage.
Describe the bug
cached_property
was only introduced in functools in Python 3.8. To support Python 3.7, you'd need to add"cached_property; python_version < '3.8'"
to your setup.pyinstall_requires
.Example PDM traceback