This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients Mark.Shannon, christian.heimes, jdemeyer, lukasz.langa, methane, miss-islington, pablogsal, petr.viktorin, pitrou, vstinner
Date 2019-09-27.20:08:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> I haven't been able to verify that the last patches are sufficient to prevent Python from segfaulting. We need to wait until rc1 is out. I need a proper release or RPM build to run the tests on our internal test infrastructure.

I pushed two fixes in the 3.8 branch for FreeIPA:

* I removed func_clear() which triggered the bug
* I fixed a reference cycle... in the weakref module :-)

As Pablo wrote, this issue is still open since the real deepest root issue is not fixed yet.

I was busy with random other stuff last weeks, so I didn't find time to dig into this issue again.

IMHO fixing the root issue can wait for Python 3.9 (and Python 3.8.1).

FreeIPA should now work fine on the current Python 3.8 branch.
Date User Action Args
2019-09-27 20:08:19vstinnersetrecipients: + vstinner, pitrou, christian.heimes, petr.viktorin, methane, lukasz.langa, Mark.Shannon, jdemeyer, pablogsal, miss-islington
2019-09-27 20:08:19vstinnersetmessageid: <>
2019-09-27 20:08:19vstinnerlinkissue38006 messages
2019-09-27 20:08:19vstinnercreate