| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Yes, since it's just relaxing an overly strict check, if we can get it into beta 3 this'd be fine. |
Sorry, something went wrong.
|
Thanks @encukou for the PR 🌮🎉.. I'm working now to backport this PR to: 3.12. |
Sorry, something went wrong.
…NULL (pythonGH-105386) (cherry picked from commit 2b90796) Co-authored-by: Petr Viktorin <encukou@gmail.com>
|
GH-105697 is a backport of this pull request to the 3.12 branch. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
It would be safe, and useful in some cases, to allow creating types whose metaclass has tp_new=NULL (i.e. the metaclass can't be instantiated from Python).
@Yhg1s, is it OK to backport this to 3.12? (No rush, sorry for bothering you on release day.)
It relaxes a check that newly raises DeprecationWarning in 3.12 (or TypeError from a function that's new in 3.12). It's one line in Objects/typeobject.c, the rest are tests/docs.
📚 Documentation preview 📚: https://cpython-previews--105386.org.readthedocs.build/