➜

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 thomas.nyberg
Recipients thomas.nyberg
Date 2018-03-01.16:57:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1519923433.61.0.467229070634.issue32980@psf.upfronthosting.co.za>
In-reply-to
Content 
The `_PyFrame_Init()` and `PyByteArray_Init()` functions are called in these two locations in the `_Py_InitializeCore()` function:

	https://github.com/python/cpython/blob/master/Python/pylifecycle.c#L693-L694
	https://github.com/python/cpython/blob/master/Python/pylifecycle.c#L699-L700

But their function definitions appear to do nothing:

	https://github.com/python/cpython/blob/master/Objects/frameobject.c#L555-L561
	https://github.com/python/cpython/blob/master/Objects/bytearrayobject.c#L24-L28

I can understand leaving the functions in the source for backwards-compatibility, but why are they still being called in `_Py_InitializeCore()`? Seems like it just adds noise for those new to the cpython internals (I certainly found it confusing myself).

Ned Batchelder recommended possibly making a change:

	https://mail.python.org/pipermail/python-list/2018-March/731402.html
History
Date User Action Args
2018-03-01 16:57:13thomas.nybergsetrecipients: + thomas.nyberg
2018-03-01 16:57:13thomas.nybergsetmessageid: <1519923433.61.0.467229070634.issue32980@psf.upfronthosting.co.za>
2018-03-01 16:57:13thomas.nyberglinkissue32980 messages
2018-03-01 16:57:13thomas.nybergcreate