azure-cli: add pip resource

[p-linnane]

• Have you followed the guidelines for contributing?
• Have you ensured that your commits follow the commit style guide?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
• Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
• Does your build pass brew audit --strict <formula> (after doing HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

---

azure-cli needs pip with Python 3.12+ in order for az extension add to work: Azure/azure-cli#29922

[github-actions]

🤖 An automated task has requested bottles to be published to this PR.

[bebound]

@p-linnane Do you know why setuptools is not in the venv? It has been a dependency of azure-cli: Azure/azure-cli#27196

/home/linuxbrew/.linuxbrew/Cellar/azure-cli/2.65.0_1/libexec/bin/python -m pip list | grep setuptools returns empty.

[erik-bershel]

Hey @carlocab and @p-linnane!
Last couple of bottles of az cli are not usable with almost any extensions at the moment due to the bump to [email protected] which blocked image updates completely. Is it something you are aware of?

I also opened an issue in the initial repo:
Azure/azure-sdk-for-python#37979

[p-linnane]

@erik-bershel It seems like we need to downgrade back to Python 3.11 despite 3.12 being listed as supported for packaging so that we can unblock you.

@bebound We aren't able to determine the correct resources with the current project set up:

╰─ brew update-python-resources -v azure-cli
==> Retrieving PyPI dependencies for "https://github.com/Azure/azure-cli/archive/refs/tags/azure-cli-2.65.0.tar.gz"...
ERROR: https://github.com/Azure/azure-cli/archive/refs/tags/azure-cli-2.65.0.tar.gz does not appear to be a Python project: neither 'setup.py' nor 'pyproject.toml' found.

So the best thing we can do is run pipgrip under Python 3.12 and then manually update the resources.

[erik-bershel]

3.12 being listed as supported for packaging

Yeah, for now it seams to be very brave statement

[bebound]

@bebound We aren't able to determine the correct resources with the current project set up:

╰─ brew update-python-resources -v azure-cli
==> Retrieving PyPI dependencies for "https://github.com/Azure/azure-cli/archive/refs/tags/azure-cli-2.65.0.tar.gz"...
ERROR: https://github.com/Azure/azure-cli/archive/refs/tags/azure-cli-2.65.0.tar.gz does not appear to be a Python project: neither 'setup.py' nor 'pyproject.toml' found.

So the best thing we can do is run pipgrip under Python 3.12 and then manually update the resources.

I don't know the logic of brew update-python-resources. azure-cli-2.65.0.tar.gz consists of 3 python projects, and there is no'setup.py' and 'pyproject.toml' in root folder.

---

Well, I figured out why setuptools is missing. Brew calls pip with --no-deps, we need to manually add setuptools and pip in resource.

https://github.com/Homebrew/brew/blob/cd651094878e88cb710bc24e253bff8b3595258e/Library/Homebrew/formula.rb#L1855

[bebound]

3.12 being listed as supported for packaging

Yeah, for now it seams to be very brave statement

We've already used 3.12 in Azure Linux 3. Including pip and setuptools in package is a bit tricky in Homebrew, so we don't bump to 3.12 in 2.65.0. 🥲

[branchvincent]

I don't know the logic of brew update-python-resources. azure-cli-2.65.0.tar.gz consists of 3 python projects, and there is no 'setup.py' and 'pyproject.toml' in root folder.

I've opened #195315 to ensure azure-cli works with our brew update-python-resources by changing the formula url to the PyPI sdist azure-cli (which depends on the other 2 projects azure-cli-core and azure-cli-telemetry also on PyPI, meaning they are automatically included as a resource). With that change, you no longer need to generate the resources yourself or have a custom script to create version bump PR's, you can use brew bump instead. I think this is a far more maintainable solution