3.13 support

[clin1234]

Trying to build it from Git yields two stumbling blocks:

• watchfiles:

  - Installing watchfiles (0.22.0): Failed

  IsolatedBuildError

  Backend subprocess exited when trying to invoke build_wheel

  Running `maturin pep517 build-wheel -i C:\Users\ךינשגכהד\AppData\Local\Temp\tmpgj4ow0ys\.venv\Scripts\python.exe --compatibility off`
  📦 Including license file "C:\Users\0BAC~1\AppData\Local\Temp\tmpe6y9gh6d\watchfiles-0.22.0\LICENSE"
  🍹 Building a mixed python/rust project
  🔗 Found pyo3 bindings
  🐍 Found CPython 3.13 at C:\Users\ךינשגכהד\AppData\Local\Temp\tmpgj4ow0ys\.venv\Scripts\python.exe
  📡 Using build options bindings from pyproject.toml
     Compiling target-lexicon v0.12.14
     Compiling cc v1.0.96
     Compiling windows_x86_64_msvc v0.52.5
     Compiling once_cell v1.19.0
     Compiling autocfg v1.3.0
     Compiling proc-macro2 v1.0.81
     Compiling unicode-ident v1.0.12
     Compiling cfg-if v1.0.0
     Compiling windows_x86_64_msvc v0.48.5
     Compiling libc v0.2.154
     Compiling parking_lot_core v0.9.10
     Compiling crossbeam-utils v0.8.19
     Compiling heck v0.4.1
     Compiling scopeguard v1.2.0
     Compiling smallvec v1.13.2
     Compiling portable-atomic v1.6.0
     Compiling indoc v2.0.5
     Compiling unindent v0.2.3
     Compiling log v0.4.21
     Compiling lock_api v0.4.12
     Compiling memoffset v0.9.1
     Compiling python3-dll-a v0.2.9
     Compiling windows-targets v0.52.5
     Compiling windows-targets v0.48.5
     Compiling windows-sys v0.52.0
     Compiling quote v1.0.36
     Compiling windows-sys v0.48.0
     Compiling crossbeam-channel v0.5.12
     Compiling syn v2.0.60
     Compiling parking_lot v0.12.2
     Compiling winapi-util v0.1.8
     Compiling filetime v0.2.23
     Compiling pyo3-build-config v0.21.2
     Compiling same-file v1.0.6
     Compiling walkdir v2.5.0
     Compiling notify v6.1.1
     Compiling pyo3-macros-backend v0.21.2
     Compiling pyo3-ffi v0.21.2
     Compiling pyo3 v0.21.2
  error: failed to run custom build command for `pyo3-ffi v0.21.2`

  Caused by:
    process didn't exit successfully: `C:\Users\0BAC~1\AppData\Local\Temp\tmpe6y9gh6d\watchfiles-0.22.0\target\release\build\pyo3-ffi-0808435ce7d1e2b4\build-script-build` (exit code: 1)
    --- stdout
    cargo:rerun-if-env-changed=PYO3_CROSS
    cargo:rerun-if-env-changed=PYO3_CROSS_LIB_DIR
    cargo:rerun-if-env-changed=PYO3_CROSS_PYTHON_VERSION
    cargo:rerun-if-env-changed=PYO3_CROSS_PYTHON_IMPLEMENTATION
    cargo:rerun-if-env-changed=PYO3_PRINT_CONFIG
    cargo:rerun-if-env-changed=PYO3_USE_ABI3_FORWARD_COMPATIBILITY

    --- stderr
    error: the configured Python interpreter version (3.13) is newer than PyO3's maximum supported version (3.12)
    = help: please check if an updated version of PyO3 is available. Current version: 0.21.2
    = help: set PYO3_USE_ABI3_FORWARD_COMPATIBILITY=1 to suppress this check and build anyway using the stable ABI
  warning: build failed, waiting for other jobs to finish...
  💥 maturin failed
    Caused by: Failed to build a native library through cargo
    Caused by: Cargo build finished with "exit code: 101": `"cargo" "rustc" "--message-format" "json-render-diagnostics" "--manifest-path" "C:\\Users\\0BAC~1\\AppData\\Local\\Temp\\tmpe6y9gh6d\\watchfiles-0.22.0\\Cargo.toml" "--release" "--lib"`
  Error: command ['maturin', 'pep517', 'build-wheel', '-i', 'C:\\Users\\ךינשגכהד\\AppData\\Local\\Temp\\tmpgj4ow0ys\\.venv\\Scripts\\python.exe', '--compatibility', 'off'] returned non-zero exit status 1

• httptools:

  - Installing httptools (0.6.1): Failed

  IsolatedBuildError

  Backend subprocess exited when trying to invoke build_wheel

  C:\Users\ךינשגכהד\AppData\Local\Temp\tmplczi7iec\.venv\Lib\site-packages\setuptools\_distutils\dist.py:268: UserWarning: Unknown distribution option: 'test_suite'
    warnings.warn(msg)
  running bdist_wheel
  running build
  running build_py
  creating build
  creating build\lib.win-amd64-cpython-313
  creating build\lib.win-amd64-cpython-313\httptools
  copying httptools\_version.py -> build\lib.win-amd64-cpython-313\httptools
  copying httptools\__init__.py -> build\lib.win-amd64-cpython-313\httptools
  creating build\lib.win-amd64-cpython-313\httptools\parser
  copying httptools\parser\errors.py -> build\lib.win-amd64-cpython-313\httptools\parser
  copying httptools\parser\__init__.py -> build\lib.win-amd64-cpython-313\httptools\parser
  running egg_info
  writing httptools.egg-info\PKG-INFO
  writing dependency_links to httptools.egg-info\dependency_links.txt
  writing requirements to httptools.egg-info\requires.txt
  writing top-level names to httptools.egg-info\top_level.txt
  reading manifest file 'httptools.egg-info\SOURCES.txt'
  reading manifest template 'MANIFEST.in'
  adding license file 'LICENSE'
  writing manifest file 'httptools.egg-info\SOURCES.txt'
  C:\Users\ךינשגכהד\AppData\Local\Temp\tmplczi7iec\.venv\Lib\site-packages\setuptools\command\build_py.py:215: _Warning: Package 'httptools.parser' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'httptools.parser' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'httptools.parser' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'httptools.parser' to be distributed and are
          already explicitly excluding 'httptools.parser' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  running build_ext
  building 'httptools.parser.parser' extension
  creating build\temp.win-amd64-cpython-313
  creating build\temp.win-amd64-cpython-313\Release
  creating build\temp.win-amd64-cpython-313\Release\httptools
  creating build\temp.win-amd64-cpython-313\Release\httptools\parser
  creating build\temp.win-amd64-cpython-313\Release\vendor
  creating build\temp.win-amd64-cpython-313\Release\vendor\llhttp
  creating build\temp.win-amd64-cpython-313\Release\vendor\llhttp\src
  "C:\Program Files\Microsoft Visual Studio\2022\Preview\VC\Tools\MSVC\14.41.34117\bin\HostX86\x64\cl.exe" /c /nologo /O2 /W3 /GL /DNDEBUG /MD -IC:\Users\0BAC~1\AppData\Local\Temp\tmpfjza0ffr\httptools-0.6.1\vendor\llhttp\include -IC:\Users\0BAC~1\AppData\Local\Temp\tmpfjza0ffr\httptools-0.6.1\vendor\llhttp\src -IC:\Users\ךינשגכהד\AppData\Local\Temp\tmplczi7iec\.venv\include -IC:\Users\ךינשגכהד\scoop\apps\python-alpha\3.13.0b4\include -IC:\Users\ךינשגכהד\scoop\apps\python-alpha\3.13.0b4\Include "-IC:\Program Files\Microsoft Visual Studio\2022\Preview\VC\Tools\MSVC\14.41.34117\include" "-IC:\Program Files\Microsoft Visual Studio\2022\Preview\VC\Auxiliary\VS\include" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.26100.0\ucrt" "-IC:\Program Files (x86)\Windows Kits\10\\include\10.0.26100.0\\um" "-IC:\Program Files (x86)\Windows Kits\10\\include\10.0.26100.0\\shared" "-IC:\Program Files (x86)\Windows Kits\10\\include\10.0.26100.0\\winrt" "-IC:\Program Files (x86)\Windows Kits\10\\include\10.0.26100.0\\cppwinrt" /Tchttptools/parser/parser.c /Fobuild\temp.win-amd64-cpython-313\Release\httptools/parser/parser.obj -O2
  parser.c
  httptools/parser/parser.c(849): warning C4996: 'Py_UNICODE': deprecated in 3.13
  httptools/parser/parser.c(850): warning C4996: 'Py_UNICODE': deprecated in 3.13
  httptools/parser/parser.c(3531): warning C4090: '=': different 'const' qualifiers
  httptools/parser/parser.c(9938): error C2198: 'int _PyLong_AsByteArray(PyLongObject *,unsigned char *,size_t,int,int,int)': too few arguments for call
  httptools/parser/parser.c(10134): error C2198: 'int _PyLong_AsByteArray(PyLongObject *,unsigned char *,size_t,int,int,int)': too few arguments for call
  error: command 'C:\\Program Files\\Microsoft Visual Studio\\2022\\Preview\\VC\\Tools\\MSVC\\14.41.34117\\bin\\HostX86\\x64\\cl.exe' failed with exit code 2

The repo hasn't been updated in months.

[JimDabell]

It looks like it’s not possible to install uvicorn with the [standard] dependencies using Python 3.13 due to httptools being incompatible with Python 3.13. The httptools issue is tracked here: MagicStack/httptools#104

The issue hasn’t had any response from maintainers and there hasn’t been any activity in the repo for a year. Is this dependency unmaintained? Are there better alternatives?

[Kludex]

No, the dependency is not unmaintained. They should update it soon.

[Kludex]

The alternative is to not install httptools and use h11.

[JimDabell]

I’d rather stick to [standard] due to this issue: #2167

[Kludex]

standard just means it included uvloop and httptools. If you read more than the title of the issue, you can see that the issue is related to asyncio - in contrast with uvloop - and that the HTTP parser (h11, or httptools) is not related to it.

[JimDabell]

Thanks! I prefer to use [standard] over adding the other dependencies separately. I know the uvloop package gets installed either way, but the dependency is clearer when it’s explicit.

[Kludex]

Uvicorn will support 3.13 when httptools does the bump.

[rsommer]

https://github.com/MagicStack/httptools/releases/tag/v0.6.2