You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have created a fork at https://github.com/isodate/isodate/ and uploaded to PyPI temporarily as https://pypi.org/project/isodate2/. I've fixed it for Python 3.10, plus some other issues. I've modernised things: dropped EOL Python, added automated release notes and deploys, converted all the tests to pytest, formatted with Black and isort, added pre-commit and linters.
Project to be claimed
isodate
: https://pypi.org/project/isodateYour PyPI username
hugovk
: https://pypi.org/user/hugovkReasons for the request
I believe the project has been abandoned.
The original package hasn't had a commit in three years and no release in four years.
It is incompatible with the recent Python 3.10 release (October 2021), as reported in multiple issues:
And there are multiple unmerged PRs to fix it:
An issue asking if the project is still unmaintained or needs new maintainers hasn't been answered by the maintainers:
I have created a fork at https://github.com/isodate/isodate/ and uploaded to PyPI temporarily as https://pypi.org/project/isodate2/. I've fixed it for Python 3.10, plus some other issues. I've modernised things: dropped EOL Python, added automated release notes and deploys, converted all the tests to pytest, formatted with Black and isort, added pre-commit and linters.
Maintenance or replacement?
Maintenance
Source code repositories URLs
Original: https://github.com/gweis/isodate
Fork: https://github.com/isodate/isodate
Contact and additional research
On 13th September, I commented on gweis/isodate#65 asking for a new release and offering to help.
On 15th September, I emailed the maintainer's address listed at https://pypi.org/project/isodate/ but it bounced: "user unknown".
On 16th September, I found and emailed a potential, alternative address but got no reply.
On 25th October, I sent a follow-up, but no reply.
Code of Conduct
The text was updated successfully, but these errors were encountered: