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

Please pin pyyaml to 3.13 until the pyyaml 5.1 fixes are done for python 3.7 support #1407

Closed
bryder opened this issue May 27, 2019 · 1 comment

Comments

@bryder
Copy link

bryder commented May 27, 2019

pyyaml-3.12 will not build the c extensions when using python 3.7 so I can not build curator using python 3.7.

pyyaml-3.13 added support for python-3.7 but curator is pinned to 3.12 at the moment.

reference to changes in pyyaml

This relates to #1368

Expected Behavior

pyyaml-3.13 should be the requirement so curator can be used with python 3.7

Actual Behavior

I can not build curator using python 3.7 if the requirements are respected

Steps to Reproduce the Problem

I use an internal build system behind a firewall so can't easily show the steps here.

I suspect installing python 3.7 and building with pip will show the error when trying to build pyyaml-3.12 which emit the same errors I've been getting but unfortunately I can't do that from where I am.

Specifications

  • Version: curator 5.7.6
  • Platform: ubuntu 16.04/18.04, Python 3.7.3
@untergeek
Copy link
Member

This is done. Curator 5.8 is currently pinned ti pyyaml=3.13

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

No branches or pull requests

2 participants