-
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
[#379] Make use of Python3.11 #380
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #380 +/- ##
=======================================
Coverage 94.84% 94.84%
=======================================
Files 135 135
Lines 4657 4657
=======================================
Hits 4417 4417
Misses 240 240 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's discuss in the refinement? I think strange to approve it while Objecttypes still doesn't support Django4.2 yet
Afaik the first prio is to switch to django4.2 for Objecttypes, ON and OZ
And we also started switching to open-api-framework
Should we make some epic with some roadmap to upgrade\patch all APIs ?
Makes sense, this was just because I'm running Py3.11 locally but ideally it should be done together with Django4.2 |
ced51b8
to
a7f3b22
Compare
@alextreme I think the time has come :) |
fixes #379 (Objects API part)