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, adamtj, asuffield, asvetlov, ncoghlan, neologix, pitrou, python-dev, rosslagerwall, scoder, serhiy.storchaka, vstinner
Date 2013-12-13.13:22:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwZ4AykQ3KzmfqsR8tT42z9_CSnjTRMDaqZFN5OYF=qmFg@mail.gmail.com>
In-reply-to <CADiSq7deeDop-qgR8JGpsnv6nzP_oRiXr9OK2dTE3YzfbNQfWg@mail.gmail.com>
Content
> I agree that this is an improvement, but isn't it a bit late for removing a public field from a public header file in 3.4, without any preceding deprecation?

The header is not public, it is private. The structure in not
documented (in Doc/c-api/*.rst). There is only one public documented
method: PyFrame_GetLineNumber().

If you rely on such implement detail (PyFrameObject field), you have
to be prepared for breakage between Python releases (3.x).

Do you know applications relying on the field?

How don't see how you would like to deprecate the field since it's
private and not documented.
History
Date User Action Args
2013-12-13 13:22:38vstinnersetrecipients: + vstinner, ncoghlan, pitrou, scoder, asvetlov, adamtj, neologix, Mark.Shannon, rosslagerwall, python-dev, serhiy.storchaka, asuffield
2013-12-13 13:22:38vstinnerlinkissue14432 messages
2013-12-13 13:22:38vstinnercreate