{Storage} Remove pkg_resource usage in azure-multiapi-storage#31683
{Storage} Remove pkg_resource usage in azure-multiapi-storage#31683
Conversation
️✔️AzureCLI-FullTest
|
|
Hi @calvinhzy, |
️✔️AzureCLI-BreakingChangeTest
|
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR. Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions). pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>
|
There was a problem hiding this comment.
Pull Request Overview
This PR updates the version of azure-multiapi-storage from 1.4.0 to 1.4.1 across setup.py and platform-specific requirements files to remove deprecated pkg_resource usage.
- Updates version in setup.py
- Updates version in requirements.py3.windows.txt, requirements.py3.Linux.txt, and requirements.py3.Darwin.txt
Reviewed Changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| src/azure-cli/setup.py | Bump azure-multiapi-storage version from 1.4.0 to 1.4.1 |
| src/azure-cli/requirements.py3.windows.txt | Bump azure-multiapi-storage version from 1.4.0 to 1.4.1 |
| src/azure-cli/requirements.py3.Linux.txt | Bump azure-multiapi-storage version from 1.4.0 to 1.4.1 |
| src/azure-cli/requirements.py3.Darwin.txt | Bump azure-multiapi-storage version from 1.4.0 to 1.4.1 |
Related command
Description
Because of the deprecation warning for pkg_resource, bump version to remove pkg_resource usage in azure-multiapi-storage
Azure/azure-multiapi-storage-python@3c0ef60
Related issue: #31591
Testing Guide
History Notes
[Component Name 1] BREAKING CHANGE:
az command a: Make some customer-facing breaking change[Component Name 2]
az command b: Add some customer-facing featureThis checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.