Conflicts between footmark and aliyun-python-sdk-core
- Dominant language
- Python
- Stars
- 15
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
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
| +-aliyun-python-sdk-core=2.9.5,<2.9.6>
| +-aliyun-python-sdk-ecs=4.11.0,<4.11.1>
| +-aliyun-python-sdk-ess=2.1.3>
| | +-aliyun-python-sdk-core=2.11.5>
| +-aliyun-python-sdk-rds=2.1.0>
| | +-aliyun-python-sdk-core=2.11.5>
| +-aliyun-python-sdk-slb=2.0.21>
| | +-aliyun-python-sdk-core=2.11.5>
| +-aliyun-python-sdk-vpc=3.0.2,<3.0.3>
| +-importlib
| +-oss2=2.3.3>
```
Thanks for your help.
Best,
Neolith
Contributor guide
No contributing guide indexed for this repository
Research direction
Review footmark's dependency declarations alongside the listed aliyun-python-sdk-core, aliyun-python-sdk-ess, ECS, RDS, SLB, and VPC requirements. Reproduce the installation conflict and verify that the dependency constraints resolve to versions accepted by all listed SDK packages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100