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
{{ message }}
This repository was archived by the owner on Jul 26, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Jul 26, 2026. It is now read-only.
the library supports Python v3.13.x, PyPi throttles to <=3.12. I cannot see this reflected in the github workflow, but the pypi page does so and so does pip for some reason.
Sorry, if I cannot be more specific. I would appreciate, if you could look into this matter.
This is probably just an oversight, as I see no reason why this library wouldn't be supporting any newer python version.
Let's see if anything can be done.
Did the new version help? Even before this, I haven't had any problems installing smmap in environments where Python is 3.13 or even 3.14. The metadata change in the newly released smmap 5.0.3 is just the addition of a trove classifier, which I don't think any package managers--and certainly not pip--are supoosed to regard as binding. The hard restraint has been >=3.7 for some time and was unchanged.
To be clear, this is not an objection--in my view, smmap is known to be compatible with Python 3.13, and adding the trove classifier for it (given that we use trove classifiers for other versions known to work on all platforms) was the right thing to do. But I'm curious if something more subtle is going on, and whether this change was really sufficient to get it working for you.
Activity
Byron commentedon Mar 9, 2026
This is probably just an oversight, as I see no reason why this library wouldn't be supporting any newer python version.
Let's see if anything can be done.
Byron commentedon Mar 9, 2026
Should be fixed via #66 .
cmeesters commentedon Mar 9, 2026
Thank you so much!
EliahKagan commentedon Mar 9, 2026
Did the new version help? Even before this, I haven't had any problems installing
smmapin environments where Python is 3.13 or even 3.14. The metadata change in the newly released smmap 5.0.3 is just the addition of a trove classifier, which I don't think any package managers--and certainly notpip--are supoosed to regard as binding. The hard restraint has been>=3.7for some time and was unchanged.To be clear, this is not an objection--in my view,
smmapis known to be compatible with Python 3.13, and adding the trove classifier for it (given that we use trove classifiers for other versions known to work on all platforms) was the right thing to do. But I'm curious if something more subtle is going on, and whether this change was really sufficient to get it working for you.