[
https://issues.apache.org/jira/browse/ARIA-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tal Liron updated ARIA-429:
---------------------------
Description:
The new API is recommended for various reasons mentioned here:
http://yaml.readthedocs.io/en/latest/api.html#reason-for-api-change
But more specifically, it intrinsically solves the problem for which we created
a workaround n ARIA-422.
Also, it seems the new API automatically tries to initialize the
{{CSafeLoader}} (see {{parsing/reading/yaml.py}}). We need to verify that this
is true.
If all is good, we need to move all our uses of ruamel to this new API and
centralize them in our {{utils/yaml.py}}.
was:
The new API is recommended for various reasons mentioned here:
http://yaml.readthedocs.io/en/latest/api.html#reason-for-api-change
But more specifically, it intrinsically solves the problem for which we created
a workaround n ARIA-422.
Also, it seems the new API automatically tries to initialize the CSafeLoader
(see `parsing/reading/yaml.py`). We need to verify that this is true.
If all is good, we need to move all our uses of ruamel to this new API and
centralize them in our `utils/yaml.py`.
> Change our usage of ruamel.yaml to the new API
> ----------------------------------------------
>
> Key: ARIA-429
> URL: https://issues.apache.org/jira/browse/ARIA-429
> Project: AriaTosca
> Issue Type: Story
> Reporter: Tal Liron
>
> The new API is recommended for various reasons mentioned here:
> http://yaml.readthedocs.io/en/latest/api.html#reason-for-api-change
> But more specifically, it intrinsically solves the problem for which we
> created a workaround n ARIA-422.
> Also, it seems the new API automatically tries to initialize the
> {{CSafeLoader}} (see {{parsing/reading/yaml.py}}). We need to verify that
> this is true.
> If all is good, we need to move all our uses of ruamel to this new API and
> centralize them in our {{utils/yaml.py}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
