Conflicts between baiji-serialization and pyyaml

[NeolithEra]

Hi, users are unable to run baiji-serialization due to dependency conflict with pyyaml package. As shown in the following full dependency graph of baiji-serialization, baiji-serialization requires pyyaml >=3.11，while baiji requires pyyaml >=3.11,<4.

According to pip’s “first found wins” installation strategy, pyyaml 5.1.2 is the actually installed version. However, pyyaml 5.1.2 does not satisfy >=3.11,<4

Dependency tree-----------

baiji-serialization - 1.2.1
| +- baiji(install version:2.10.0 version range:*)
| | +- boto(install version:2.49.0 version range:>=2.38.0,<3)
| | +- plumbum(install version:1.6.8 version range:>=1.6.2,<2)
| | +- progressbar(install version:2.5 version range:>=2.3,<3)
| | +- pyspin(install version:1.1.1 version range:>=1.1.1,<2)
| | | +- futures(install version:3.3.0 version range:*)
| | +- pyyaml(install version:3.13 version range:>=3.11,<4)
| | +- requests(install version:2.22.0 version range:<3,>=2.9.1)
| | | +- certifi(install version:2019.9.11 version range:>=2017.4.17)
| | | +- chardet(install version:3.0.4 version range:<3.1.0,>=3.0.2)
| | | +- idna(install version:2.8 version range:>=2.5,<2.9)
| | | +- urllib3(install version:1.25.7 version range:<1.26,>=1.21.1)
| +- pyyaml(install version:5.1.2 version range:>=3.11)
| +- simplejson(install version:3.17.0 version range:>=3.8.2)

Thanks for your help.
Best,
Neolith

[NeolithEra]

Suggested Solution

1. Fix your direct dependency to be pyyaml >=3.11, <4. I have checked this revision will not affect your downstream projects now.
2. Ask your upstream project baiji to loose the version range of pyyaml.

Hi, @algrs, Which solution do you prefer, 1 or 2?
Please let me know your choice. I can submit a PR to solve this issue.

[paulmelnikow]

Hey @NeolithEra, I've got an active fork of this project going at https://github.com/metabolize/baiji-serialization and https://github.com/metabolize/baiji. I've been seeing the conflict warnings for a long time now and would be happy to merge a fix. I think loosening baiji to pyyaml >=3.11 is a good way to go.