-
Notifications
You must be signed in to change notification settings - Fork 10
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
Upgrade to Python3.11 #379
Closed
1 of 2 tasks
alextreme opened this issue
Mar 21, 2024
· 0 comments
· Fixed by #380 or maykinmedia/objecttypes-api#117
Closed
1 of 2 tasks
Upgrade to Python3.11 #379
alextreme opened this issue
Mar 21, 2024
· 0 comments
· Fixed by #380 or maykinmedia/objecttypes-api#117
Labels
Comments
alextreme
added a commit
that referenced
this issue
Mar 21, 2024
alextreme
added a commit
that referenced
this issue
Mar 21, 2024
alextreme
added a commit
that referenced
this issue
Mar 21, 2024
annashamray
pushed a commit
that referenced
this issue
Jun 21, 2024
annashamray
added a commit
that referenced
this issue
Jun 21, 2024
annashamray
added a commit
to maykinmedia/objecttypes-api
that referenced
this issue
Jun 21, 2024
annashamray
added a commit
that referenced
this issue
Jun 21, 2024
annashamray
added a commit
to maykinmedia/objecttypes-api
that referenced
this issue
Jun 21, 2024
github-project-automation
bot
moved this from Implemented
to Done
in Data en API fundament
Jun 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the objects API runs on Py3.10, with Py3.11 I get an lxml error.
I'll create a PR to make use of Py3.11 as I think it's an unwritten rule at Maykin to only use odd versions of Python (and to at least make use of the current version in Debian stable)
The text was updated successfully, but these errors were encountered: