Support Python 3.13

[Goldziher]

Python 3.13 is in the works and will be released in the nearish future. It would be great to have it supported.

TODOs

• aaz-dev supports 3.13
  • Support Python 3.13 aaz-dev-tools#495
• azdev supports 3.13
  • Support Python 3.13 azure-cli-dev-tools#527
• Dependencies are updated to the Python 3.13 compatible version
  • {Packaging} Bump cffi to 1.17.1 #31822
  • {Packaging} Bump PyWin32 to 311 #31823
• CI passes with Python 3.13
  • {Core} aaz: Wrap functools.partial in staticmethod() to remove FutureWarning #31973
  • [Packaging] Support Python 3.13 #31895
  • [Packaging] Bump embedded Python to 3.13.7 #31928
  • {CI} Update pipeline to use Python 3.13 azure-cli-extensions#9056
• Extension compatible with Python 3.13
  • webpubsub: ModuleNotFoundError: No module named 'cgi' [WebPubSub] Support python 3.13 azure-cli-extensions#8993
  • azure-sphere: from pathlib import Path, os ImportError: cannot import name 'os' from 'pathlib' [azure-sphere] Update index.json azure-cli-extensions#9025
  • [ServiceConnector-passwordless] bump version for psycopg2-binary azure-cli-extensions#9075

[yonzhan]

Thank you for opening this issue, we will look into it.

[Goldziher]

Thank you! i would like to point out that typing is a major point of improvement for the v3.12 and 3.13. Especially the new generic syntax etc.

[XhmikosR]

Any news about this? Fedora Workstation 41 ships with Python 3.13 and there are failures with v2.62.

[dmilith]

It's 3.13.1 already, but this still fails like this:

ERROR: Ignored the following yanked versions: 0.13.11, 0.13.13, 0.14.1
ERROR: Could not find a version that satisfies the requirement pymsalruntime<0.18,>=0.17; (python_version >= "3.8" and platform_system == "Darwin") and extra == "broker" (from msal[broker]) (from versions: 0.3.0, 0.3.1, 0.3.2, 0.4.0, 0.5.0, 0.6.0, 0.7.0, 0.8.0, 0.8.1, 0.9.0, 0.10.0, 0.11.0, 0.11.2, 0.12.4, 0.13.0, 0.13.1, 0.13.2, 0.13.9, 0.13.12, 0.14.0, 0.14.2a1, 0.14.2, 0.15.0a1)
ERROR: No matching distribution found for pymsalruntime<0.18,>=0.17; (python_version >= "3.8" and platform_system == "Darwin") and extra == "broker"

[zippy1981]

Currently, pip install azure-cli on Python 3.13.1 on windows fails for me because it tries to compile pymsalruntime. I will get a machine with a C++ compiler and test that.

I'm not an expert on pip dependencies, bit it seems that the ABI changes per release, and a compiled version of that upstream dependency needs to be pushed to pypi.

Building wheels for collected packages: pymsalruntime
  Building wheel for pymsalruntime (pyproject.toml) ... error
  error: subprocess-exited-with-error

  × Building wheel for pymsalruntime (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [10 lines of output]
      running bdist_wheel
      running build
      running build_py
      creating build\lib.win-amd64-cpython-313\pymsalruntime
      copying pymsalruntime\__init__.py -> build\lib.win-amd64-cpython-313\pymsalruntime
      copying pymsalruntime\PyMsalRuntime.pyi -> build\lib.win-amd64-cpython-313\pymsalruntime
      copying pymsalruntime\msalruntime.dll -> build\lib.win-amd64-cpython-313\pymsalruntime
      running build_ext
      building 'pymsalruntime.pymsalruntime' extension
      error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for pymsalruntime
Failed to build pymsalruntime
ERROR: ERROR: Failed to build installable wheels for some pyproject.toml based projects (pymsalruntime)

[bebound]

@zippy1981 Compiling wheel is complex on Windows. We'll wait for the pymsalruntime release wheel package.

[sbreit-tomra]

Any news about this? Fedora Workstation 41 ships with Python 3.13 and there are failures with v2.62.

Same with Arch, still Python 3.13 related failures in 2.67.0.

[sodul]

The pymsalruntime package is owned by Microsoft and used to authenticate against Azure.

The bug has been opened on the pymsalruntime side since December and it was prioritized last week; so it will take a while before a new working release is available.

Now an other issue is that the azure cli requirements might pin to a specific release which means that we would also need azure-cli to accept this future release.

https://github.com/search?q=org%3Aazure+pymsalruntime+&type=code

For example azure-cli/requirements.py3.windows.txt has pymsalruntime==0.16.2 which means that it will prevent the use of the new release when it comes out.

It might be a good idea for Microsoft maintainers of Azure-cli to talk to the Microsoft maintainers of pymsalruntime so that paying Microsoft customers (through Azure bills) can get support sooner.

[sbreit-tomra]

With Python 3.13, I get this error: /opt/azure-cli/lib/python3.13/site-packages/azure/cli/core/aaz/_command.py:135: FutureWarning: functools.partial will be a method descriptor in future Python versions; wrap it in staticmethod() if you want to preserve the old behavior

I reckon this too is a Python 3.13 related issue, not a different one?