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

ModuleNotFoundError #160

Open
dw-ryoung opened this issue Jan 29, 2025 · 6 comments
Open

ModuleNotFoundError #160

dw-ryoung opened this issue Jan 29, 2025 · 6 comments

Comments

@dw-ryoung
Copy link

after installing the latest version of braintree I'm getting errors importing the library into my code.

At the top of my file I have:

import braintree

and the error I'm getting is:

File "/home/ryoung/git/virtualenv/dws/lib/python3.12/site-packages/braintree/__init__.py", line 11, in <module> from braintree.braintree_gateway import BraintreeGateway File "/home/ryoung/git/virtualenv/dws/lib/python3.12/site-packages/braintree/braintree_gateway.py", line 9, in <module> from braintree.customer_session_gateway import CustomerSessionGateway File "/home/ryoung/git/virtualenv/dws/lib/python3.12/site-packages/braintree/customer_session_gateway.py", line 7, in <module> from braintree.graphql import ( File "/home/ryoung/git/virtualenv/dws/lib/python3.12/site-packages/braintree/graphql/__init__.py", line 1, in <module> from braintree.graphql.enums import ( ModuleNotFoundError: No module named 'braintree.graphql.enums'

I do not get this issue on the previous version of the library

cedk added a commit to cedk/braintree_python that referenced this issue Jan 29, 2025
cedk added a commit to cedk/braintree_python that referenced this issue Jan 29, 2025
cedk added a commit to cedk/braintree_python that referenced this issue Jan 29, 2025
@skept
Copy link

skept commented Jan 29, 2025

I'm having the same issue

@Leggendario12
Copy link

Leggendario12 commented Jan 30, 2025

An entire module is missing. The init file shows all the issues.

Image Image

@jeremyakriska
Copy link

@Leggendario12

it looks like there is a PR that addresses it from 4 hours ago #161, it's just not merged yet

@cedk
Copy link

cedk commented Jan 31, 2025

If #161 can not be merged and released quickly, could at least the release 4.33.0 be yanked from PyPI?

@saralvasquez
Copy link
Contributor

This is on our radar. Fix incoming

@saralvasquez
Copy link
Contributor

Hello! Thank you for bringing this to our attention. We have released a patch version that resolves the error causing the import issues. We have also yanked the version that introduced this problem. Version 4.33.1 should be safe to upgrade to now.

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 a pull request may close this issue.

6 participants