Skip to content

Conversation

@r-burns
Copy link

@r-burns r-burns commented Jan 8, 2026

The future package is not compatible with python 3.13+, so we need to replace any imports of the past module.

As far as I can tell, it's only used for basestring, which is trivial to implement using the same logic the future module uses: https://github.com/PythonCharmers/python-future/blob/2d56f83adab5a0957cfc5abbe62db1e2d1912b61/src/past/types/basestring.py#L25-L26

The `future` package is not compatible with python 3.13+, so we need to
replace any imports of the `past` module.

As far as I can tell, it's only used for basestring, which is trivial
to implement using the same logic the future module uses:
https://github.com/PythonCharmers/python-future/blob/2d56f83adab5a0957cfc5abbe62db1e2d1912b61/src/past/types/basestring.py#L25-L26
@peterbarker
Copy link
Contributor

How was this tested?

@r-burns
Copy link
Author

r-burns commented Jan 9, 2026

Nothing beyond verifying that it's importable now. Behavior should be the exact same as before, this is exactly how the basestring instance check was implemented.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants