[issue15727] PyType_FromSpecWithBases tp_new bugfix

2021-10-18 Thread Irit Katriel
Change by Irit Katriel : -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> The danger of PyType_FromSpec() ___ Python tracker ___

[issue15727] PyType_FromSpecWithBases tp_new bugfix

2018-09-11 Thread Petr Viktorin
Petr Viktorin added the comment: Converting static types to heap ones is just one of the reasons to use PyType_FromSpec*. Another ones are writing such classes from scratch, and converting pure-Python classes to C. I don't think PyObject_FailingNew is a good default for either of those. I

[issue15727] PyType_FromSpecWithBases tp_new bugfix

2018-04-09 Thread Petr Viktorin
Change by Petr Viktorin : -- nosy: +Dormouse759 ___ Python tracker ___ ___

[issue15727] PyType_FromSpecWithBases tp_new bugfix

2018-04-08 Thread Nick Coghlan
Change by Nick Coghlan : -- nosy: +encukou, ncoghlan ___ Python tracker ___ ___

[issue15727] PyType_FromSpecWithBases tp_new bugfix

2016-10-02 Thread Serhiy Storchaka
Changes by Serhiy Storchaka : -- type: behavior -> crash versions: +Python 3.5, Python 3.6, Python 3.7 -Python 3.2, Python 3.3, Python 3.4 ___ Python tracker

[issue15727] PyType_FromSpecWithBases tp_new bugfix

2016-10-02 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: Affected modules were tkinter and curses (see issue23815). This was fixed by explicit nullifying tp_new after calling PyType_FromSpec(). Issue26979 was open for documenting this danger effect. -- nosy: +serhiy.storchaka

[issue15727] PyType_FromSpecWithBases tp_new bugfix

2012-12-02 Thread Antoine Pitrou
Antoine Pitrou added the comment: Robin, do you remember which extension types were affected by this issue? -- nosy: +pitrou versions: +Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15727

[issue15727] PyType_FromSpecWithBases tp_new bugfix

2012-11-30 Thread Robin Schreiber
Robin Schreiber added the comment: Here is revised version of the patch. Martin von Löwis and I had discovered a way to reproduce problems with refactored modules, that occur without this patch. This is was several months ago, however I will try to give you a code sample! :-) --

[issue15727] PyType_FromSpecWithBases tp_new bugfix

2012-11-08 Thread Robin Schreiber
Changes by Robin Schreiber robin.schrei...@me.com: -- keywords: +pep3121 -patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15727 ___ ___

[issue15727] PyType_FromSpecWithBases tp_new bugfix

2012-09-09 Thread Jesús Cea Avión
Changes by Jesús Cea Avión j...@jcea.es: -- nosy: +jcea ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15727 ___ ___ Python-bugs-list mailing list

[issue15727] PyType_FromSpecWithBases tp_new bugfix

2012-09-09 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: Can you give an example of the situation that you described? Perhaps you encountered it while refactoring some particular extension module. Which? In your patch new code is commented out. PySpec_New() is not a good name. It should be something like

[issue15727] PyType_FromSpecWithBases tp_new bugfix

2012-08-19 Thread Robin Schreiber
New submission from Robin Schreiber: As with every type, that has been created and initialized, HeapTypes created form PyType_FromSpecWithBases() have to pass through PyType_Ready(). Here the function inherit_special might be called, which, among other things, does the following: 3892