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: No module named 'brevo_python.models.configuration' in version 1.1.1 #2

Open
ToShareOrNotToShare opened this issue Jul 4, 2024 · 3 comments

Comments

@ToShareOrNotToShare
Copy link

Dear brevo team,
Dear all readers,

When redeploying a Google Cloud Function today (July 4, 2024), I encountered a recurring issue with the brevo-python module.

The error occurred three times consecutively (three re-deployments) with the following message:

ModuleNotFoundError: No module named 'brevo_python.models.configuration'

Steps to Reproduce

  1. Deploy a Google Cloud Function that imports the brevo-python module.
  2. Ensure that brevo-python version is unspecified in requirements.txt.
  3. Deploy the function.

Screenshots

Here are more detailed screenshots of the error messages:

brevo-python1 1 1_No module named 'brevo_python models configuration'_1_of_3 brevo-python1 1 1_No module named 'brevo_python models configuration'_2_of_3 brevo-python1 1 1_No module named 'brevo_python models configuration'_3_of_3

"Move" around

After explicitly setting "brevo_python==1.0.0" in the requirements.txt, the error is gone.
Therefore, I assume the error may have something to do with version 1.1.1

Key Questions

  • Has there been any change in version 1.1.1 that could cause this issue?
  • Specifically, changes related to the brevo_python.models.configuration module?

Thank you everyone and have a great week!

@Artui
Copy link

Artui commented Jul 8, 2024

I think it has to do with this commit
e3210b88bb0d75528c113d6bf544b765aa03fd77
But it wasn't fixed there fully, and lines with from brevo_python.models.configuration import Configuration need to be deleted from the root __init__.py and models/__init__.py

@Artui
Copy link

Artui commented Jul 13, 2024

@mukul-brevo I've created a PR to address this issue, and bumped the version to 1.1.2 there

@Artui
Copy link

Artui commented Jul 16, 2024

@ToShareOrNotToShare I believe the issue is fixed in 1.1.2

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.

2 participants