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

Conflicts between footmark and aliyun-python-sdk-core #34

Open
NeolithEra opened this issue Jul 17, 2019 · 1 comment
Open

Conflicts between footmark and aliyun-python-sdk-core #34

NeolithEra opened this issue Jul 17, 2019 · 1 comment

Comments

@NeolithEra
Copy link

Hi, users are unable to run footmark due to dependency conflict with aliyun-python-sdk-core package.
As shown in the following full dependency graph of footmark , footmark requires aliyun-python-sdk-core >=2.9.5,<2.9.6,while aliyun-python-sdk-ess requires aliyun-python-sdk-core=2.11.5.
According to pip’s “first found wins” installation strategy, aliyun-python-sdk-core 2.9.5 is the actually installed version. However, aliyun-python-sdk-core 2.9.5 does not satisfy >=2.11.5, which leads to a build error.

Dependency tree------

footmark<version range:>
| +-aliyun-python-sdk-core<version range:>=2.9.5,<2.9.6>
| +-aliyun-python-sdk-ecs<version range:>=4.11.0,<4.11.1>
| +-aliyun-python-sdk-ess<version range:>=2.1.3>
| | +-aliyun-python-sdk-core<version range:>=2.11.5>
| +-aliyun-python-sdk-rds<version range:>=2.1.0>
| | +-aliyun-python-sdk-core<version range:>=2.11.5>
| +-aliyun-python-sdk-slb<version range:<3.2.8,>=2.0.21>
| | +-aliyun-python-sdk-core<version range:>=2.11.5>
| +-aliyun-python-sdk-vpc<version range:>=3.0.2,<3.0.3>
| +-importlib<version range:>
| +-oss2<version range:>=2.3.3>

Thanks for your help.
Best,
Neolith

@NeolithEra
Copy link
Author

NeolithEra commented Jul 17, 2019

Solution

@xiaozhu36 Could you upgrade aliyun-python-sdk-core from >=2.9.5,<2.9.6 to >2.11.5 ?

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

1 participant