please consider supporting current PyYAML #392
Comments
|
I have been trying to support Python 2 for as long as possible, but it's time to finally leave it behind. I plan to make a release in the next month. After that I'm going to make Python 3.7 the minimum version. That will allow me to finally use f-strings and DataClasses as well as update the PyYAML version. |
ltaylor16
added a commit
that referenced
this issue
Feb 18, 2025
The current limit on the PyYAML version does not work with newer versions of Python. setup.py provides syntax to specify dependencies based on python_version. Also make a fix for Python 3.10 for collections.abc.Mapping. Tested Python 2.7. It has rotted some and is not working. Added a few fixes. Found a recursive import: statements - whelpers - statements Added a kludge by passing in statements module to the function in whelpers that needed it. Import fc-statements.py with pyYAML instead of json to avoid unicode issues. #392
|
The release was dragging out more than I planned. I found the syntax for setup.py to allow a different PyYAML version for Python3. I tested with Python 3.12. But spits out a warning about setup.py be deprecated. I'll add that to the list. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
setup.py requires PyYAML<6:
but I didn't manage to install old PyYAML on a new system with Python 3.13.
PyYAML 5.4.1 has binary wheel only for Python<=3.9. So pip tried to build PyYAML from source, but it didn't work, probably due to incompatibility with Cython. The error looked like this one: yaml/pyyaml#601
In the end my workaround was to use Python 3.9 for shroud.
The text was updated successfully, but these errors were encountered: