PR#423: Workaround for CI failures with latest PyYAML and Python 2.6 -

rpkg

#423 Workaround for CI failures with latest PyYAML and Python 2.6

Closed Mar 14, 2019 by onosek. Opened Mar 13, 2019 by merlinm.

Unknown source master

merlinm commented Mar 13, 2019

If this PR passes the CI tests, it is valid workaround for the following errors that recently started causing CI to fail:

17:39:57 Collecting PyYAML (from rpkg==1.57)
...
17:39:57   Downloading https://files.pythonhosted.org/packages/9f/2c/9417b5c774792634834e730932745bc09a7d36754ca00acf1ccd1ac2594d/PyYAML-5.1.tar.gz (274kB)
17:39:58 PyYAML requires Python '>=2.7, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.*' but the running Python is 2.6.9

Please feel free to reject this PR in favor of a better solution.

lsedlar commented Mar 14, 2019

This is good. There's an alternative in #424 that only applies the fix to Python 2.6 environment and uses new PyYAML in all other versions.

onosek commented Mar 14, 2019

Thank you for the effort.

Pull-Request has been closed by onosek

Mar 14, 2019

Metadata

Assignee

None

Tags

No Tags

rpkg

#423 Workaround for CI failures with latest PyYAML and Python 2.6 Closed Mar 14, 2019 by onosek. Opened Mar 13, 2019 by merlinm. Unknown source master

Metadata

#423 Workaround for CI failures with latest PyYAML and Python 2.6

Closed Mar 14, 2019 by onosek. Opened Mar 13, 2019 by merlinm.

Unknown source master