-
-
Notifications
You must be signed in to change notification settings - Fork 746
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
Bump pyyaml
and orjson
#6029
base: master
Are you sure you want to change the base?
Bump pyyaml
and orjson
#6029
Conversation
Changed | ||
~~~~~~~ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's already a Changed
sub-section below under in development
Changed | ||
~~~~~~~ | ||
|
||
* Bumped `pyyaml` to `6.0.1` and `orjson` to `3.9.7` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* Bumped `pyyaml` to `6.0.1` and `orjson` to `3.9.7` | |
* Bumped `pyyaml` to `6.0.1` and `orjson` to `3.9.7`. #6029 |
Thanks for the contribution!
Additionally, there are more py lock files that need a regeneration. |
Yeah, I'm not sure this'll ever work on Python 3.6, support was dropped in orjson==3.6.2. |
A workaround might be, first, |
If 3.9.7 is not available for python 3.6 then we can't bump to that version, as we are still using pip and therefore the same requirement files are used for python 3.6 and 3.8. There are some instructions in: #5789, and also in the st2/lockfiles/st2-constraints.txt and st2/pants-requirements.txt |
This is what I'm currently seeing under Python 3.8.10 with PyYAML 5.4.1: