Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for newer Python versions (3.12.x and 3.13.x) #1473

Open
erikspears opened this issue Oct 17, 2024 · 4 comments
Open

Support for newer Python versions (3.12.x and 3.13.x) #1473

erikspears opened this issue Oct 17, 2024 · 4 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@erikspears
Copy link

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 😄

@omri374
Copy link
Contributor

omri374 commented Oct 21, 2024

Thanks for the suggestion! We'll look into it

@jsburckhardt
Copy link

jsburckhardt commented Jan 28, 2025

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'

Image

Going to 3.11:

docker run --rm -it mcr.microsoft.com/devcontainers/python:3.11 pip install presidio-analyzer
# no error

Image

@omri374
Copy link
Contributor

omri374 commented Jan 30, 2025

@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

@andrewisplinghoff
Copy link
Contributor

@omri374 It truly is a spaCy issue: explosion/spaCy#13658

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

4 participants