René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"`ruamel.yaml` might be abandoned (from PyPI)","articleBody":"https://pypi.org/project/ruamel.yaml/\n\nAs of the 0.18.7 release:\n\n\u003e If you are interested in future upgrades of ruamel.yaml please check the [documentation on installing](https://yaml.dev/doc/ruamel.yaml/install/), since at some point I might not be able to upload a new version to PyPI with updated information.\n\n\u003e 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.\n\nThis dependency is causing other issues (see #1038, #1037, #283, #147).\n\nI think there are really five pathways forward here:\n\n- Status quo. Keep rolling with `ruamel.yaml` despite its introduction of breaking changes without notice e.g. `0.18.13` and unclear future\n- Fork `ruamel.yaml`, with the view only to maintain it specifically for usethis\n- Vendor v0.18.12 of `ruamel.yaml` in usethis, and then maintain indefinitely. \n- Create a new YAML roundtripping library for Python.\n   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.\n- Give up on roundtripping in `usethis` entirely :(\n","author":{"url":"https://github.com/nathanjmcdougall","@type":"Person","name":"nathanjmcdougall"},"datePublished":"2025-12-19T03:14:15.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/1190/usethis-python/issues/1190"}