Support for newer Python versions (3.12.x and 3.13.x)
erikspears opened this issue ยท 8 comments
Hi all,
Opening this out of curiosity regarding newer Python version support for MS Presidio. Python 3.13.0 is now the latest stable, and the Presidio docs still list 3.11 as the last version fully supported. We've got Presidio running on some versions of Python 3.12.x (up thru .6, but .7 isn't happy), but obviously having more official support would be ideal. Any chance that is coming in a near-term update?
Thanks ๐
Thanks for the suggestion! We'll look into it
In the main readme it says 3.13. I'm working on mcr.microsoft.com/devcontainers/python:latest
which comes with 3.13.1 and i can't install the pip packages. I had to pull 3.11 for it to work.
docker run --rm -it mcr.microsoft.com/devcontainers/python:latest pip install presidio-analyzer
Pip install error:
Collecting spacy!=3.7.0,<4.0.0,>=3.4.4 (from presidio-analyzer)
Using cached spacy-3.8.2.tar.gz (1.3 MB)
Installing build dependencies: started
Installing build dependencies: finished with status 'error'
Going to 3.11:
docker run --rm -it mcr.microsoft.com/devcontainers/python:3.11 pip install presidio-analyzer
# no error
@jsburckhardt 3.13 is still not officially supported. I also did a test and it's failing on spaCy deps (thinc, preshed). We'll look into this but it could be a spaCy issue.
It's true that readme says 3.13
@omri374 It truly is a spaCy issue: explosion/spaCy#13658
Seems that this would be solved by upgrading to a newer spaCy version. From the thread @andrewisplinghoff pointed at, at least 2.5.1 should be fixed.
Closing the issue for now, please report back if there are any additional. BTW, if you're interested, here's Matthew Honnibal's video on upgrading some spaCy elements to Python 3.13: https://www.youtube.com/watch?v=TTEWWJ2PmZQ&list=PLBmcuObd5An5_iAxNYLJa_xWmNzsYce8c
@omri374 perhaps it would be better to close this until there's a new presidio release that includes the fixes?
A new version is released