https://pypi.org/project/ruamel.yaml/
As of the 0.18.7 release:
If you are interested in future upgrades of ruamel.yaml please check the documentation on installing, since at some point I might not be able to upload a new version to PyPI with updated information.
However, after uploading version 0.18.7, I got an email from PyPI, about having to change the project name to ruamel_yaml to comply with PEP 625, sometime in the future. The email doesn't say if namespace packages are no longer allowed, or how to deal with the very real clash with the pre-existing package ruamel_yaml.
This dependency is causing other issues (see #1038, #1037, #283, #147).
I think there are really five pathways forward here:
- Status quo. Keep rolling with
ruamel.yaml despite its introduction of breaking changes without notice e.g. 0.18.13 and unclear future
- Fork
ruamel.yaml, with the view only to maintain it specifically for usethis
- Vendor v0.18.12 of
ruamel.yaml in usethis, and then maintain indefinitely.
- Create a new YAML roundtripping library for Python.
I'm very tempted to do this! I would just wrap Rust libraries I think, and perhaps try and use a similar API as ruamel.yaml for simpler migration. On the other hand, it might be better to design from the ground up.
- Give up on roundtripping in
usethis entirely :(
https://pypi.org/project/ruamel.yaml/
As of the 0.18.7 release:
This dependency is causing other issues (see #1038, #1037, #283, #147).
I think there are really five pathways forward here:
ruamel.yamldespite its introduction of breaking changes without notice e.g.0.18.13and unclear futureruamel.yaml, with the view only to maintain it specifically for usethisruamel.yamlin usethis, and then maintain indefinitely.I'm very tempted to do this! I would just wrap Rust libraries I think, and perhaps try and use a similar API as
ruamel.yamlfor simpler migration. On the other hand, it might be better to design from the ground up.usethisentirely :(