{"author":"Anthon van der Neut","author_email":"a.van.der.neut@ruamel.eu","bugtrack_url":null,"classifiers":["Development Status :: 4 - Beta","Intended Audience :: Developers","License :: OSI Approved :: MIT License","Operating System :: OS Independent","Programming Language :: Python","Programming Language :: Python :: 3.10","Programming Language :: Python :: 3.11","Programming Language :: Python :: 3.12","Programming Language :: Python :: 3.13","Programming Language :: Python :: 3.8","Programming Language :: Python :: 3.9","Programming Language :: Python :: Implementation :: CPython","Topic :: Software Development :: Libraries :: Python Modules","Topic :: Text Processing :: Markup","Typing :: Typed"],"description":"# ruamel.yaml\n\n`ruamel.yaml` is a YAML 1.2 loader/dumper package for Python.\n\n| | |\n| - | - |\n| version |0.18.10 |\n| updated |2025-01-06 |\n| documentation |https://yaml.dev/doc/ruamel.yaml |\n| repository |https://sourceforge.net/projects/ruamel-yaml |\n| pypi |https://pypi.org/project/ruamel.yaml |\n\n\n## breaking changes, that may make future uploads to PyPI impossible\n\n*If you are interested in future upgrades of `ruamel.yaml`\nplease check the [documentation on installing](https://yaml.dev/doc/ruamel.yaml/install/),\nsince at some point I might not be able to upload a new version to PyPI with updated information.*\n\n`ruamel.yaml` was intentionally named as `yaml` in a namespace `ruamel`. The namespace allows the installation\nname to correspond unchanged to how the package is imported, reduces the number of links I have to create\nin site-packages of a Python install during development, as well as providing a recognisable set of packages\nmy company releases to the public. \n\nHowever, after uploading version 0.18.7, I got an email from PyPI, about having to change the project name\nto `ruamel_yaml` to comply with PEP 625, sometime in the future. The email doesn't say if namespace packages are\nno longer allowed, or how to deal with the very real clash with the pre-existing package `ruamel_yaml`.\n\nI might not be able to adapt `ruamel.yaml`, in\na way that does not negatively affect the 0.5 million daily downloads (and my own usage of the package) in time. \nMy experience with other such service downgrades (Bitbucket, Readthedocs), has not been entirely positive. \n\n-----\n\n\n\nAs announced, in 0.18.0, the old PyYAML functions have been deprecated.\n(`scan`, `parse`, `compose`, `load`, `emit`, `serialize`, `dump` and their variants\n(`_all`, `safe_`, `round_trip_`, etc)). If you only read this after your program has \nstopped working: I am sorry to hear that, but that also means you, or the person \ndeveloping your program, has not tested with warnings on (which is the recommendation \nin PEP 565, and e.g. defaulting when using `pytest`). If you have troubles, explicitly use\n```\npip install \"ruamel.yaml<0.18.0\"\n```\nor put something to that effects in your requirments, to give yourself\nsome time to solve the issue.\n\nThere will be at least one more potentially breaking change in the 0.18 series: `YAML(typ='unsafe')`\nnow has a pending deprecation warning and is going to be deprecated, probably before the end of 2023.\nIf you only use it to dump, please use the new `YAML(typ='full')`, the result of that can be *safely*\nloaded with a default instance `YAML()`, as that will get you inspectable, tagged, scalars, instead of\nexecuted Python functions/classes. (You should probably add constructors for what you actually need, \nbut I do consider adding a `ruamel.yaml.unsafe` package that will re-add the `typ='unsafe'` option.\n*Please adjust/pin your dependencies accordingly if necessary.*\n\n\nThere seems to be a CVE on `ruamel.yaml`, stating that the `load()` function could be abused \nbecause of unchecked input. `load()` was never the default function (that was `round_trip_load()`\nbefore the new API came into existence. So the creator of that CVE was ill informed and\nprobably lazily assumed that since `ruamel.yaml` is a derivative of PyYAML (for which\na similar CVE exists), the same problem would still exist, without checking. \nSo the CVE was always inappropriate, now just more so, as the call\nto the function `load()` with any input will terminate your program with an error message. If you \n(have to) care about such things as this CVE, my recommendation is to stop using Python\ncompletely, as `pickle.load()` can be abused in the same way as `load()` (and like unlike `load()` \nis only documented to be unsafe, without development-time warning. \n\nVersion 0.18.9 was the last one tested to be working with Python 3.7\nVersion 0.17.21 was the last one tested to be working on Python 3.5 and 3.6
\nThe 0.16.13 release was the last that was tested to be working on Python 2.7.\n\n\nThere are two extra plug-in packages\n(`ruamel.yaml.bytes` and `ruamel.yaml.string`)\nfor those not wanting to do the streaming to a\n`io.BytesIO/StringIO` buffer themselves.\n\nIf your package uses `ruamel.yaml` and is not listed on PyPI, drop me an\nemail, preferably with some information on how you use the package (or a\nlink to the repository) and I'll keep you informed when the status of\nthe API is stable enough to make the transition.\n\n\n

\n\n0.18.10 (2025-01-06):\n\n- implemented changes to the setup.py for Python 3.14 as suggested by [Miro Hrončok](https://sourceforge.net/u/hroncok/profile/) in merge requests (MR not merged as those files are copied in from `develop` config)\n\n0.18.9 (2025-01-05):\n\n- fix issue with roundtripping 0 in YAML 1.1 reported by [Peter Law](https://sourceforge.net/u/peterjclaw/profile/)\n\n0.18.8 (2025-01-02):\n\n- added warning to README.md that PyPI might block updates due to breaking changes\n\n0.18.7 (2024-12-30):\n\n- fixes for README (reported by [Kees Bakker](https://sourceforge.net/u/keesb/profile/))\n- fixes preserving anchor on scalar integer `0` (issue reported by (Mor Peled)[https://sourceforge.net/u/morp/profile/] and also in a question by [Ravi](https://stackoverflow.com/users/6550398/ravi) on [Stackoverflow](https://stackoverflow.com/a/79306830/1307905))\n- fix for formatting of README suggested by [Michael R. Crusoe](https://sourceforge.net/u/crusoe/profile/)\n\n0.18.6 (2024-02-07):\n\n- fixed an issue with dataclass loading when the fields were collections (bug found as a result of a question by [FibroMyAlgebra](https://stackoverflow.com/users/6855070/fibromyalgebra) on [StackOverflow](https://stackoverflow.com/a/77485786/1307905))\n- fixed an issue loading dataclasses with `InitVar` fields when `from __future__ import annotations` was used to delay evaluation of typing.\n\n0.18.5 (2023-11-03):\n\n- there is some indication that dependent packages have been pinned to use specific (tested) and just install the latest even in Python versions that have end-of-life\n\n0.18.4 (2023-11-01):\n\n- YAML() instance has a `doc_infos` attribute which is a cumulative list of DocInfo instances (one for `load()`, one per document for `load_all()`). DocInfo instances contain version information (requested, directive) and tag directive information\n- fix issue that the YAML instance tags attribute was not reset between documents, resulting in mixing of tag directives of multiple documents. Now only provides tag directive information on latest document after loading. This means tags for dumping must be set **again** after a document is loaded with the same instance. (because of this tags will be removed in a favour of a different mechanism in the future)\n- fix issue with multiple document intermixing YAML 1.2 and YAML 1.1, the VersionedResolver now resets\n- fix issue with disappearing comment when next token was Tag (still can't have both a comment before a tag and after a tag, before node)\n\n0.18.3 (2023-10-29):\n\n- fix issue with spurious newline on first item after comment + nested block sequence\n- additional links in the metadata on PyPI (Reported, with pointers how to fix, by [Sorin](https://sourceforge.net/u/ssbarnea/profile/)).\n\n0.18.2 (2023-10-24):\n\n- calling the deprecated functions now raises an `AttributeError` with the, somewhat more informative, orginal warning message. Instead of calling `sys.exit(1)`\n\n0.18.1 (2023-10-24):\n\n- calling the deprecated functions now always displays the warning message. (reported by [Trend Lloyd](https://sourceforge.net/u/lathiat2/profile/))\n\n0.18.0 (2023-10-23):\n\n- the **functions** `scan`, `parse`, `compose`, `load`, `emit`, `serialize`, `dump` and their variants (`_all`, `safe_`, `round_trip_`, etc) have been deprecated (the same named **methods** on `YAML()` instances are, of course, still there.\n- `YAML(typ='unsafe')` now issues a `PendingDeprecationWarning`. This will become deprecated in the 0.18 series\n(probably before the end of 2023).\nYou can use `YAML(typ='full')` to dump unregistered Python classes/functions. \nFor loading you'll have to register your classes/functions\nif you want the old, unsafe, functionality. You can still load any tag, like `!!python/name:posix.system', **safely** \nwith the (default) round-trip parser.\n- fix for `bytes-like object is required not 'str' while dumping binary streams`. This was reported, analysed and a fix provided by [Vit Zikmund](https://sourceforge.net/u/tlwhitec/profile/)\n\n0.17.40 (2023-10-20):\n\n- flow style sets are now preserved ( `!!set {a, b, c} )`. Any values specified when loading are dropped, including `!!null \"\"`.\n- potential workaround for issue 484: the long_description_content_type including the variant specification `CommonMark`\ncan result in problems on Azure. If you can install from `.tar.gz` using\n`RUAMEL_NO_LONG_DESCRIPTION=1 pip install ruamel.yaml --no-binary :all:` then the long description, and its\noffending type, are nog included (in the METADATA). \n(Reported by [Coury Ditch](https://sourceforge.net/u/cmditch/profile/))\n- links in documentation update (reported by [David Hoese](https://sourceforge.net/u/daveydave400/profile/))\n- Added some `__repr__` for internally used classes\n\n0.17.39 (2023-10-19):\n\n- update README generation, no code changes\n\n0.17.36 (2023-10-19):\n\n- fixed issue 480, dumping of a loaded empty flow-style mapping with comment failed (Reported by [Stéphane Brunner](https://sourceforge.net/u/stbrunner/profile/))\n- fixed issue 482, caused by DEFAULT_MAPPING_TAG having changes to being a `Tag()` instance, not a string (reported by [yan12125](https://sourceforge.net/u/yan12125/profile/))\n- updated documentation to use mkdocs\n\n0.17.35 (2023-10-04):\n\n- support for loading dataclasses with `InitVar` variables (some special coding was necessary to get the, unexecpected, default value in the corresponding instance attribute ( example of usage in [this question](https://stackoverflow.com/q/77228378/1307905))\n\n0.17.34 (2023-10-03):\n\n- Python 3.12 also loads C version when using `typ='safe'`\n- initial support for loading invoking\n`__post_init__()` on dataclasses that have that\nmethod after loading a registered dataclass.\n(Originally\n[asked](https://stackoverflow.com/q/51529458/1307905) on\nStackoverflow by\n[nyanpasu64](https://stackoverflow.com/users/2683842/nyanpasu64)\nand as\n[ticket](https://sourceforge.net/p/ruamel-yaml/tickets/355/) by\n[Patrick Lehmann](https://sourceforge.net/u/paebbels/profile/))\n\n```\n@yaml.register_class\n@dataclass\nclass ...\n```\n\n0.17.33 (2023-09-28):\n\n- added `flow_seq_start`, `flow_seq_end`, `flow_seq_separator`, `flow_map_start`, `flow_map_end`, `flow_map_separator` **class** attributes to the `Emitter` class so flow style output can more easily be influenced (based on [this answer](https://stackoverflow.com/a/76547814/1307905) on a StackOverflow question by [Huw Walters](https://stackoverflow.com/users/291033/huw-walters)).\n\n0.17.32 (2023-06-17):\n\n- fix issue with scanner getting stuck in infinite loop\n\n0.17.31 (2023-05-31):\n\n- added tag.setter on `ScalarEvent` and on `Node`, that takes either a `Tag` instance, or a str (reported by [Sorin Sbarnea](https://sourceforge.net/u/ssbarnea/profile/))\n\n0.17.30 (2023-05-30):\n\n- fix issue 467, caused by Tag instances not being hashable (reported by [Douglas Raillard](https://bitbucket.org/%7Bcf052d92-a278-4339-9aa8-de41923bb556%7D/))\n\n0.17.29 (2023-05-30):\n\n- changed the internals of the tag property from a string to a class which allows for preservation of the original handle and suffix. This should result in better results using documents with %TAG directives, as well as preserving URI escapes in tag suffixes.\n\n0.17.28 (2023-05-26):\n\n- fix for issue 464: documents ending with document end marker\nwithout final newline fail to load (reported by [Mariusz\nRusiniak](https://sourceforge.net/u/r2dan/profile/))\n\n0.17.27 (2023-05-25):\n\n- fix issue with inline mappings as value for merge keys (reported by Sirish on [StackOverflow](https://stackoverflow.com/q/76331049/1307905))\n- fix for 468, error inserting after accessing merge attribute on `CommentedMap` (reported by [Bastien gerard](https://sourceforge.net/u/bagerard/))\n- fix for issue 461 pop + insert on same `CommentedMap` key throwing error (reported by [John Thorvald Wodder II](https://sourceforge.net/u/jwodder/profile/))\n\n0.17.26 (2023-05-09):\n\n- fix for error on edge cage for issue 459\n\n0.17.25 (2023-05-09):\n\n- fix for regression while dumping wrapped strings with too many backslashes removed (issue 459, reported by [Lele Gaifax](https://sourceforge.net/u/lele/profile/))\n\n0.17.24 (2023-05-06):\n\n- rewrite of `CommentedMap.insert()`. If you have a merge key in the YAML document for the mapping you insert to, the position value should be the one as you look at the YAML input. This fixes issue 453 where other keys of a merged in mapping would show up after an insert (reported by [Alex Miller](https://sourceforge.net/u/millerdevel/profile/)). It also fixes a call to `.insert()` resulting into the merge key to move to be the first key if it wasn't already and it is also now possible to insert a key before a merge key (even if the fist key in the mapping).\n- fix (in the pure Python implementation including default) for issue 447. (reported by [Jack Cherng](https://sourceforge.net/u/jfcherng/profile/), also brought up by brent on [StackOverflow](https://stackoverflow.com/q/40072485/1307905))\n\n0.17.23 (2023-05-05):\n\n- fix 458, error on plain scalars starting with word longer than width. (reported by [Kyle Larose](https://sourceforge.net/u/klarose/profile/))\n- fix for `.update()` no longer correctly handling keyword arguments (reported by John Lin on [StackOverflow]( https://stackoverflow.com/q/76089100/1307905))\n- fix issue 454: high Unicode (emojis) in quoted strings always\nescaped (reported by [Michal\nČihař](https://sourceforge.net/u/nijel/profile/) based on a\nquestion on StackOverflow).\n- fix issue with emitter conservatively inserting extra backslashes in wrapped quoted strings (reported by thebenman on [StackOverflow](https://stackoverflow.com/q/75631454/1307905))\n\n0.17.22 (2023-05-02):\n\n- fix issue 449 where the second exclamation marks got URL encoded (reported and fixing PR provided by [John Stark](https://sourceforge.net/u/jods/profile/))\n- fix issue with indent != 2 and literal scalars with empty first line (reported by wrdis on [StackOverflow](https://stackoverflow.com/q/75584262/1307905))\n- updated `__repr__` of CommentedMap, now that Python's dict is ordered -> no more `ordereddict(list-of-tuples)`\n- merge MR 4, handling OctalInt in YAML 1.1 (provided by [Jacob Floyd](https://sourceforge.net/u/cognifloyd/profile/))\n- fix loading of `!!float 42` (reported by Eric on [Stack overflow](https://stackoverflow.com/a/71555107/1307905))\n- line numbers are now set on `CommentedKeySeq` and `CommentedKeyMap` (which are created if you have a sequence resp. mapping as the key in a mapping)\n- plain scalars: put single words longer than width on a line of\ntheir own, instead of after the previous line (issue 427, reported\nby [Antoine\nCotten](https://sourceforge.net/u/antoineco/profile/)). Caveat:\nthis currently results in a space ending the previous line.\n- fix for folded scalar part of 421: comments after \">\" on first\nline of folded scalars are now preserved (as were those in the\nsame position on literal scalars). Issue reported by Jacob Floyd.\n- added stacklevel to warnings\n- typing changed from Py2 compatible comments to Py3, removed various Py2-isms\n\n0.17.21 (2022-02-12):\n\n- fix bug in calling `.compose()` method with `pathlib.Path` instance.\n\n0.17.20 (2022-01-03):\n\n- fix error in microseconds while rounding datetime fractions >= 9999995 (reported by [Luis Ferreira](https://sourceforge.net/u/ljmf00/))\n\n0.17.19 (2021-12-26):\n\n- fix mypy problems (reported by [Arun](https://sourceforge.net/u/arunppsg/profile/))\n\n0.17.18 (2021-12-24):\n\n- copy-paste error in folded scalar comment attachment (reported by [Stephan Geulette](https://sourceforge.net/u/sgeulette/profile/))\n- fix 411, indent error comment between key empty seq value (reported by [Guillermo Julián](https://sourceforge.net/u/gjulianm/profile/))\n\n0.17.17 (2021-10-31):\n\n- extract timestamp matching/creation to util\n\n0.17.16 (2021-08-28):\n\n- 398 also handle issue 397 when comment is newline\n\n0.17.15 (2021-08-28):\n\n- fix issue 397, insert comment before key when a comment between key and value exists (reported by [Bastien gerard](https://sourceforge.net/u/bagerard/))\n\n0.17.14 (2021-08-25):\n\n- fix issue 396, inserting key/val in merged-in dictionary (reported by [Bastien gerard](https://sourceforge.net/u/bagerard/))\n\n0.17.13 (2021-08-21):\n\n- minor fix in attr handling\n\n0.17.12 (2021-08-21):\n\n- fix issue with anchor on registered class not preserved and those classes using package attrs with `@attr.s()` (both reported by [ssph](https://sourceforge.net/u/sph/))\n\n0.17.11 (2021-08-19):\n\n- fix error baseclass for `DuplicateKeyError` (reported by [Łukasz Rogalski](https://sourceforge.net/u/lrogalski/))\n- fix typo in reader error message, causing `KeyError` during reader error (reported by [MTU](https://sourceforge.net/u/mtu/))\n\n0.17.10 (2021-06-24):\n\n- fix issue 388, token with old comment structure != two elements (reported by [Dimitrios Bariamis](https://sourceforge.net/u/dbdbc/))\n\n0.17.9 (2021-06-10):\n\n- fix issue with updating CommentedMap (reported by sri on [StackOverflow](https://stackoverflow.com/q/67911659/1307905))\n\n0.17.8 (2021-06-09):\n\n- fix for issue 387 where templated anchors on tagged object did get set resulting in potential id reuse. (reported by [Artem Ploujnikov](https://sourceforge.net/u/flexthink/))\n\n0.17.7 (2021-05-31):\n\n- issue 385 also affected other deprecated loaders (reported via email by Oren Watson)\n\n0.17.6 (2021-05-31):\n\n- merged type annotations update provided by [Jochen Sprickerhof](https://sourceforge.net/u/jspricke/)\n- fix for issue 385: deprecated round_trip_loader function not\nworking (reported by [Mike\nGouline](https://sourceforge.net/u/gouline/))\n- wasted a few hours getting rid of mypy warnings/errors\n\n0.17.5 (2021-05-30):\n\n- fix for issue 384 `!!set` with aliased entry resulting in broken YAML on rt reported by [William Kimball](https://sourceforge.net/u/william303/))\n\n0.17.4 (2021-04-07):\n\n- prevent (empty) comments from throwing assertion error (issue 351 reported by [William Kimball](https://sourceforge.net/u/william303/)) comments (or empty line) will be dropped\n\n0.17.3 (2021-04-07):\n\n- fix for issue 382 caused by an error in a format string (reported by [William Kimball](https://sourceforge.net/u/william303/))\n- allow expansion of aliases by setting `yaml.composer.return_alias = lambda s: copy.deepcopy(s)`\n(as per [Stackoverflow answer](https://stackoverflow.com/a/66983530/1307905))\n\n0.17.2 (2021-03-29):\n\n- change -py2.py3-none-any.whl to -py3-none-any.whl, and remove 0.17.1\n\n0.17.1 (2021-03-29):\n\n- added 'Programming Language :: Python :: 3 :: Only', and\nremoving 0.17.0 from PyPI (reported by [Alasdair\nNicol](https://sourceforge.net/u/alasdairnicol/))\n\n0.17.0 (2021-03-26):\n\n- removed because of incomplete classifiers\n- this release no longer supports Python 2.7, most if not all Python 2 specific code is removed. The 0.17.x series is the last to support Python 3.5 (this also allowed for removal of the dependency on `ruamel.std.pathlib`)\n- remove Python2 specific code branches and adaptations (u-strings)\n- prepare % code for f-strings using `_F`\n- allow PyOxidisation ([issue 324](https://sourceforge.net/p/ruamel-yaml/tickets/324/) resp. [issue 171](https://github.com/indygreg/PyOxidizer/issues/171))\n- replaced Python 2 compatible enforcement of keyword arguments with '*'\n- the old top level *functions* `load`, `safe_load`, `round_trip_load`, `dump`, `safe_dump`, `round_trip_dump`, `scan`, `parse`, `compose`, `emit`, `serialize` as well as their `_all` variants for multi-document streams, now issue a `PendingDeprecationning` (e.g. when run from pytest, but also Python is started with `-Wd`). Use the methods on `YAML()`, which have been extended.\n- fix for issue 376: indentation changes could put literal/folded\nscalar to start before the `#` column of a following comment.\nEffectively making the comment part of the scalar in the output.\n(reported by [Bence Nagy](https://sourceforge.net/u/underyx/))\n\n\n------------------------------------------------------------------------\n\nFor older changes see the file\n[CHANGES](https://sourceforge.net/p/ruamel-yaml/code/ci/default/tree/CHANGES)\n","description_content_type":"text/markdown; charset=UTF-8; variant=CommonMark","docs_url":null,"download_url":null,"downloads":{"last_day":-1,"last_month":-1,"last_week":-1},"dynamic":null,"home_page":null,"keywords":"yaml 1.2 parser round-trip preserve quotes order config","license":"MIT license","license_expression":null,"license_files":null,"maintainer":null,"maintainer_email":null,"name":"ruamel.yaml","package_url":"https://pypi.org/project/ruamel.yaml/","platform":null,"project_url":"https://pypi.org/project/ruamel.yaml/","project_urls":{"Documentation":"https://yaml.dev/doc/ruamel-yaml","Home":"https://sourceforge.net/p/ruamel-yaml/","Source":"https://sourceforge.net/p/ruamel-yaml/code/ci/default/tree/","Tracker":"https://sourceforge.net/p/ruamel-yaml/tickets/"},"provides_extra":null,"release_url":"https://pypi.org/project/ruamel.yaml/0.18.10/","requires_dist":["ruamel.yaml.clib>=0.2.7; platform_python_implementation == \"CPython\" and python_version < \"3.13\"","ryd; extra == \"docs\"","mercurial>5.7; extra == \"docs\"","ruamel.yaml.jinja2>=0.2; extra == \"jinja2\""],"requires_python":">=3.7","summary":"ruamel.yaml is a YAML parser/emitter that supports roundtrip preservation of comments, seq/map flow style, and map key order","version":"0.18.10","yanked":false,"yanked_reason":null}

Dependency	Optional
ruamel.yaml.clib	false
mercurial	true
ruamel.yaml.jinja2	true
ryd	true

Package search

ruamel.yaml

project_urls

Dependencies

All package metadata

Releases