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
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
Deploy a Google Cloud Function that imports the brevo-python module.
Ensure that brevo-python version is unspecified in requirements.txt.
Deploy the function.
Screenshots
Here are more detailed screenshots of the error messages:
"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!
The text was updated successfully, but these errors were encountered:
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
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
Screenshots
Here are more detailed screenshots of the error messages:
"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
Thank you everyone and have a great week!
The text was updated successfully, but these errors were encountered: