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
pixax-stripe uses stripe>=2.0 as dependency, as defined here. This causes that deployments of the code without changing dependencies could break because they are incompatible with the deployed code.
Steps to Reproduce
It can't be downloaded and reproduced, because your project will break as stripe changes they Python Library API.
In my case, the issue caused the following problem
Use stripe.CardError
Someday after a deployment, my server re-installed the dependencies and I got AttributeError: module 'stripe' has no attribute 'CardError'
What were you expecting to happen?
Every version of pinax-stripe should be expected to work with only one version of stripe.
What actually happened?
The text was updated successfully, but these errors were encountered:
martinvol
added a commit
to martinvol/pinax-stripe
that referenced
this issue
Aug 9, 2018
I think the problem is that it was not pinned previously, which was done in bb25a05.
Maybe you updated stripe before pinax-stripe already?
Would be good to have your full traceback to see if it is from pinax-stripe, or maybe even your own app.
I think this issue can be closed, with further discussion in #584.
Issue Summary
A short summary of the issue
pixax-stripe uses
stripe>=2.0
as dependency, as defined here. This causes that deployments of the code without changing dependencies could break because they are incompatible with the deployed code.Steps to Reproduce
It can't be downloaded and reproduced, because your project will break as stripe changes they Python Library API.
In my case, the issue caused the following problem
AttributeError: module 'stripe' has no attribute 'CardError'
What were you expecting to happen?
Every version of pinax-stripe should be expected to work with only one version of stripe.
What actually happened?
The text was updated successfully, but these errors were encountered: