-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drop support for Python 3.4 #32
Comments
I have a machine at work which uses Windows XP 32bit. Thanks a lot |
pyinaturalist
To go back in time and see project info for past versions, you can use the version tags on:
Screenshots for how to get there: GitHubBranches/Tags drop-down in the upper left: ReadthedocsVersion drop-down in the lower left (Note: 'stable' is the current stable release, and 'latest' is the development version/ PyPI |
Would it help if I added a section to the docs that lists the last supported pyinaturalist version for each python version? Or let me know if you have any other suggestions for the documentation. |
Yes, that would be useful. |
Added that info here under 'Python version compatibility': https://pyinaturalist.readthedocs.io/en/latest/user_guide.html#installation |
How could I check the installed version of pyinaturalist from my pyinat.py script at runtime, before importing it? I want to run the script in several machines, some of them with Python 3.8 and some others with 3.4 (so pyinaturalist 0.10) As import syntax was different in old versions I need the script to know which one to use, so I can adapt it to follow the old doc examples when needed. |
Some thoughts on this:
|
Thanks a lot for the recommendations and warnings. |
Great! I'd like to help support your classroom project if I can, and it will be much easier to make bugfixes, new features, etc. if you're using the latest version. |
Python 3.4 reached EOL in March 2019, and it's been adding a bit of extra work to keep compatibility with it. I'd like to drop this in the release after the next one (which would be
v0.11
).Things to clean up/restrictions that would no longer apply:
typing
backport and use the stdlib versionmerge_two_dicts()
and use{**dict, **dict}
and other PEP 448 syntaxjson.JSONDecodeError
requirements.txt
; known minimum required package versions are all specified insetup.py
now, and remaining version pins are not neededThe text was updated successfully, but these errors were encountered: