-
Notifications
You must be signed in to change notification settings - Fork 326
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
Python 3.11 support #1245
Labels
Comments
We will, but not until one of our core dependencies (Stanza) does. But we have no idea when Stanza will be ready and our codebase will be updated.
Meanwhile I recommend you do everything in 3.10 and/or write your processed data to a file, then pick it up in 3.11 (if that is where your main work is done).
Jan 15, 2024 at 07:20 by ***@***.***:
…
Hello,
May I ask if you are planning to support Python 3.11 in the near future?
Thanks in adavance!
—
Reply to this email directly, > view it on GitHub <#1245>> , or > unsubscribe <https://github.com/notifications/unsubscribe-auth/AAOE36EQF452HG3F3BRQYO3YOVCL3AVCNFSM6AAAAABB3OFE7SVHI2DSMVQWIX3LMV43ASLTON2WKOZSGA4DEMRUGM2DAMA>> .
You are receiving this because you are subscribed to this thread.> Message ID: > <cltk/cltk/issues/1245> @> github> .> com>
|
Hello @MarjorieBurghart, I'm going to check again but support of Python 3.11 has been possible since version 1.1.7. Did you encounter an issue with Python 3.11 and CLTK? |
I definitely encountered a dependency problem with 3.11 … something to do with incompatibility of torch.
If anyone has a code patch that can make it work, we will gladly accept it. You can pull the code locally, change the defaults in pyproject.toml, then run make build
Jan 16, 2024 at 05:44 by ***@***.***:
…
Hello > @MarjorieBurghart <https://github.com/MarjorieBurghart>> ,
I'm going to check again but support of Python 3.11 has been possible since version > 1.1.7 <https://github.com/cltk/cltk/releases/tag/v1.1.7>> . Did you encounter an issue with Python 3.11 and CLTK?
—
Reply to this email directly, > view it on GitHub <#1245 (comment)>> , or > unsubscribe <https://github.com/notifications/unsubscribe-auth/AAOE36FLEIXABPLP53SRDI3YOZ75RAVCNFSM6AAAAABB3OFE7SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJTG43TEMRVGY>> .
You are receiving this because you commented.> Message ID: > <cltk/cltk/issues/1245/1893772256> @> github> .> com>
|
Is it solved now? I think so. If not, let's reopen it. |
yes I think it's solved, thanks!
…On Fri, 17 May 2024, 23:21 Clément Besnier, ***@***.***> wrote:
Is it solved now? I think so. If not, let's reopen it.
—
Reply to this email directly, view it on GitHub
<#1245 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADTSO5OEZIDAR66724GKHTDZCZYDZAVCNFSM6AAAAABB3OFE7SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJYGM4TOMJXGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
May I ask if you are planning to support Python 3.11 in the near future?
Thanks in adavance!
The text was updated successfully, but these errors were encountered: