- Python Home
- About
- News
- Documentation
- Downloads
- Community
- Foundation
- Developer's Guide
- Issue Tracker
- Issues
- Summaries
- User
- Administration
- Help
Message330163
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 | atuining, eric.snow, izbyshev, lemburg, scoder, serhiy.storchaka, tim.peters, vstinner |
| Date | 2018-11-20.23:20:10 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1542756010.5.0.788709270274.issue35081@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Stefan Behnel: > Making _PyGC_FINALIZED() internal broke Cython (https://github.com/cython/cython/issues/2721). It's used in the finaliser implementation (https://github.com/cython/cython/blob/da657c8e326a419cde8ae6ea91be9661b9622504/Cython/Compiler/ModuleNode.py#L1442-L1456), to determine if an object for which tp_dealloc() is called has already been finalised or whether we have to do it. I'm not sure how to deal with this on our side now. Any clue? I wrote PR 10626 to add _PyGC_FINALIZED() back to the C API. My intent was only to remove _PyObject_GC_TRACK(o) and _PyObject_GC_UNTRACK(o) from the public C API. I didn't expect that anyone would use _PyGC_FINALIZED() :-) |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-11-20 23:20:10 | vstinner | set | recipients: + vstinner, lemburg, tim.peters, atuining, scoder, eric.snow, serhiy.storchaka, izbyshev |
| 2018-11-20 23:20:10 | vstinner | set | messageid: <1542756010.5.0.788709270274.issue35081@psf.upfronthosting.co.za> |
| 2018-11-20 23:20:10 | vstinner | link | issue35081 messages |
| 2018-11-20 23:20:10 | vstinner | create | |

