Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pykern and ruyaml integration work #130

Open
6 tasks
jeinstei opened this issue Aug 10, 2022 · 3 comments
Open
6 tasks

pykern and ruyaml integration work #130

jeinstei opened this issue Aug 10, 2022 · 3 comments

Comments

@jeinstei
Copy link
Member

jeinstei commented Aug 10, 2022

Work in support of changing out module dependencies for more portability in non-RS environments

  • Identify and document current conflicts due to versions and requirements
  • Check version of YAML files; if using ruYAML, can add % YAML 1.1
  • Create branch with pykern removed
  • Check on config and other resource file locations
  • Test branch in production and dev environments
  • Modify documentation to support any changes
@cchall
Copy link
Member

cchall commented Aug 11, 2022

@jeinstei
Copy link
Member Author

It is an interesting situation, it sounds like, as there is also the ruyaml fork to keep maintenance (https://github.com/pycontribs/ruyaml/). I'm ambivalent about which we use as long as the sourceforge ruamel one continues to be maintained

@cchall
Copy link
Member

cchall commented Aug 11, 2022

The page for ruyaml states:

ruyaml package is a fork of ruamel.yaml aimed to made in order to secure the future of the library, mainly by having a pool of maintainers.

Given that it is currently running behind https://pypi.org/project/ruamel.yaml/ I would say that we should continue to just use ruamel.yaml unless there is some sort of statement that the ruamel.yaml developer is ceasing maintenance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

2 participants