Log message:
py-*: remove unused tool dependency

py-setuptools includes the py-wheel functionality nowadays

Log message:
py-ruamel-yaml: updated to 0.18.6

0.18.6
- 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))
- fixed an issue loading dataclasses with `InitVar` fields when `from __future__ \ 
import
  annotations` was used to delay evaluation of typing.

Log message:
py-ruamel-yaml: update to 0.18.5.

[0.18.5, 2023-11-03]:
- 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

[0.18.4, 2023-11-01]:
- 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
- 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)
- fix issue with multiple document intermixing YAML 1.2 and YAML 1.1, the \ 
VersionedResolver
  now resets
- 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)

[0.18.3, 2023-10-29]:
- fix issue with spurious newline on first item after comment + nested block sequence
- additional links in the metadata on PyPI (Reported, with pointers how to fix, by
  [Sorin](https://sourceforge.net/u/ssbarnea/profile/)).

Log message:
py-ruamel-yaml: update to 0.18.2.

[0.18.2, 2023-10-24]:
- calling the deprecated functions now raises an `AttributeError` with the, somewhat
  more informative, orginal warning message. Instead of calling `sys.exit(1)`

[0.18.1, 2023-10-24]:
- calling the deprecated functions now always displays the warning message. (reported
  by [Trend Lloyd](https://sourceforge.net/u/lathiat2/profile/))

[0.18.0, 2023-10-23]:
- 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.
- |-
  `YAML(typ='unsafe')` now issues a `PendingDeprecationWarning`. This will \ 
become deprecated in the 0.18 series
  (probably before the end of 2023).
  You can use `YAML(typ='full')` to dump unregistered Python classes/functions.
  For loading you'll have to register your classes/functions
  if you want the old, unsafe, functionality. You can still load any tag, like \ 
`!!python/name:posix.system', **safely**
  with the (default) round-trip parser.
- 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/)

Log message:
py-ruamel-yaml: updated to 0.17.40

0.17.40
- flow style sets are now preserved ( `!!set {a, b, c} )`. Any values specified when
  loading are dropped, including `!!null ""`.
- |
  potential workaround for issue 484: the long_description_content_type \ 
including the variant specification `CommonMark`
  can result in problems on Azure. If you can install from `.tar.gz` using
  `RUAMEL_NO_LONG_DESCRIPTION=1 pip install ruamel.yaml --no-binary :all:` then \ 
the long description, and its
  offending type, are nog included (in the METADATA).
  (Reported by [Coury Ditch](https://sourceforge.net/u/cmditch/profile/))
- links in documentation update (reported by [David \ 
Hoese](https://sourceforge.net/u/daveydave400/profile/))
- Added some `__repr__` for internally used classes

Log message:
py-ruamel-yaml: updated to 0.17.39

0.17.39:
- update README generation, no code changes

0.17.36:
- fixed issue 480, dumping of a loaded empty flow-style mapping with comment failed
- fixed issue 482, caused by DEFAULT_MAPPING_TAG having changes to being a `Tag()`
  instance, not a string
- updated documentation to use mkdocs

Log message:
py-ruamel-yaml: updated to 0.17.35

0.17.35
- 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>`__ )

0.17.34
- Python 3.12 also loads C version when using `typ='safe'`
- initial support for loading invoking `__post_init__()` on dataclasses that \ 
have that method
  after loading a registered dataclass (`@yaml.register_class\n@dataclass\nclass \ 
...`).

Log message:
py-ruamel-yaml: updated to 0.17.33

0.17.33
- 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

Log message:
py-ruamel-yaml: updated to 0.17.32

0.17.32
- fix issue with scanner getting stuck in infinite loop

Log message:
py-ruamel-yaml: update to 0.17.31.

[0, 17, 31]: 2023-05-31
  - 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/>`__)

[0, 17, 30]: 2023-05-30
  - fix issue 467, caused by Tag instances not being hashable (reported by
    `Douglas Raillard
    <https://bitbucket.org/%7Bcf052d92-a278-4339-9aa8-de41923bb556%7D/>`__)

[0, 17, 29]: 2023-05-30
  - 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.