aliyun / aliyun/aliyun-openapi-python-sdk
aliyun-python-sdk-core : multiple version during build for >=2.13.10
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1k
- Forks
- 578
- PR merge metrics
- No merged PRs in 30d
Description
Hi all
During the build command of the Dynatrace Extension SDK, I got a strange behavior:
- If I force version of aliyun-python-sdk-core <=2.14.0, build command creates an archive containing a single version of aliyun-python-sdk-core ✅
- If I force version of aliyun-python-sdk-core >=2.14.0, build command creates an archive containing 2 versions of aliyun-python-sdk-core : 2.13.10 and the latest one corresponding to the forced version ❌
- If I don't force version of aliyun-python-sdk-core, build command creates an archive containing 2 versions of aliyun-python-sdk-core : 2.13.10 and the latest one available (2.16.0) ❌
Is >=2.14.0 version contains some restriction that needs an older version ?
Thank you
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the Dynatrace Extension SDK build with aliyun-python-sdk-core constrained to versions at or above 2.14.0, and inspect the generated archive's dependency contents. Compare that result with the <=2.14.0 and unconstrained cases; done means the archive contains only one version of aliyun-python-sdk-core.
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
- 35/100