Skip to content
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

Python 3.10 vs pyxb EoL #151

Closed
rbour opened this issue Dec 11, 2021 · 7 comments
Closed

Python 3.10 vs pyxb EoL #151

rbour opened this issue Dec 11, 2021 · 7 comments

Comments

@rbour
Copy link

rbour commented Dec 11, 2021

Python 3.10 has moved abstract base classes from collections to collections.abc available since Python 3.3. This has broken pyxb and, therefore, imports for authorizenet/sdk-python.

There has been a pyxb pull request pending for nearly 3 years that would likely fix this specific problem, but the pyxb author has indicated that the project is at end-of-life without funding or transfer of ownership.

It seems the path to supporting Python 3.10 would involve either:

  1. Replace pyxb in the authorizenet/sdk-python project
  2. Work with the pyxb author to get that project up to date

Any chance of supporting Python 3.10 in the near future?

@rhimmelbauer
Copy link

Or any sort of timeline/road map would be valued.

@yashsamit
Copy link

Any plans?

@sunsoftdev
Copy link

any update for the support for Python 3.10. is this library still active?

@scottie
Copy link

scottie commented Nov 27, 2023

This has been open since 2021..... whats going on guys ??? Pretty disgusting actually.

@codeyash
Copy link

At this point using requests lib with direct URL makes more sense!

@dvlprb2
Copy link

dvlprb2 commented Feb 14, 2024

Adding these two lines of code just before importing authorize.net resolves the error without requiring any modifications to the package's source files.

import collections
collections.MutableSequence = collections.abc.MutableSequence

Screenshot (1)

@gnongsie
Copy link
Contributor

The Python SDK has been tested successfully on v3.6 to v3.12.
We have replaced the offending serialization library with a newer one, which will hopefully not cause more issues like this.
Closing this issue based on that.

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

No branches or pull requests

8 participants