I'm currently looking at what packages on conda-forge have a dependency on the non-maintained ruamel_yaml package.
I'd like us to remove ruamel_yaml from future builds.
To be able to do this with good conscience, it'd be good if ommprotocol could be updated to use upstream ruamel.yaml always.
ommprotocol.io already uses a try: ... except ImportError: ... construct with ruamel.yaml as a fallback, which is good.
It would, however, need ruamel.yaml<0.18 since it uses the deprecated top-level ruamel.yaml.load function.
(Details for the upstream change can be read at https://pypi.org/project/ruamel.yaml/0.18.3/ .)
Would it be possible for you to update ommprotocol.io to be compatible with ruamel.yaml=0.18 and change the dependency from ruamel_yaml to ruamel.yaml?
I'm currently looking at what packages on conda-forge have a dependency on the non-maintained
ruamel_yaml
package.I'd like us to remove
ruamel_yaml
from future builds. To be able to do this with good conscience, it'd be good ifommprotocol
could be updated to use upstreamruamel.yaml
always.ommprotocol.io
already uses atry: ... except ImportError: ...
construct withruamel.yaml
as a fallback, which is good. It would, however, needruamel.yaml<0.18
since it uses the deprecated top-levelruamel.yaml.load
function. (Details for the upstream change can be read at https://pypi.org/project/ruamel.yaml/0.18.3/ .)Would it be possible for you to update
ommprotocol.io
to be compatible withruamel.yaml=0.18
and change the dependency fromruamel_yaml
toruamel.yaml
?xref: https://github.com/conda-forge/ommprotocol-feedstock/issues/1