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 I install it via uv it doesn't even install for the same reason.
To Reproduce
Create a new virtual environment and run pip install parsons==3.1.0
Your Environment
Version of Parsons used (if you know): v3.1.0
Environment name and version (e.g. Chrome 39, node.js 5.4):
Operating System and version (desktop or mobile): Pop!_OS 22.04 LTS
Additional Context
In a fork I'm playing around with, braintree==4.26.0 and google-cloud-bigquery==3.18.0 were needed to get pytests passing. I'm not sure why that isn't the case on this repo but it seems like these versions might be safe to update.
Priority
For me it's low because I don't use braintree but "critical bugs" makes it sound rather serious for people who use that integration.
The text was updated successfully, but these errors were encountered:
bmos
added
the
bug
Impact - something is currently broken in Parsons and needs to be fixed
label
Mar 6, 2024
bmos
changed the title
[Bug] Can't Install parsons 3.1.0
[Bug] Parsons 3.1.0 targets yanked 4.0.0 version of braintree with critical bugs
Mar 6, 2024
Parsons 3.1.0 depends on braintree 4.0.0 which has been yanked due to critical bugs.
Detailed Description
When I install parsons 3.1.0 via pip, I get this message:
When I install it via uv it doesn't even install for the same reason.
To Reproduce
Create a new virtual environment and run
pip install parsons==3.1.0
Your Environment
Additional Context
In a fork I'm playing around with, braintree==4.26.0 and google-cloud-bigquery==3.18.0 were needed to get pytests passing. I'm not sure why that isn't the case on this repo but it seems like these versions might be safe to update.
Priority
For me it's low because I don't use braintree but "critical bugs" makes it sound rather serious for people who use that integration.
The text was updated successfully, but these errors were encountered: