➜

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 pablogsal
Recipients Mark.Shannon, Xtrem532, erlendaasland, gvanrossum, hroncok, jpe, pablogsal, petr.viktorin, rhettinger, scoder, vstinner
Date 2021-09-22.10:05:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1632305113.97.0.420535333616.issue43760@roundup.psfhosted.org>
In-reply-to
Content 
I discussed this particular instance with the Steering Council and the conclusion was that this field (use_tracing) is considered an implementation detail and therefore its removal it's justified so we won't be restoring it.

I'm therefore closing PR28498

Notice that this decision only affects this particular issue and should not be generalized to other fields or structures. We will try to determine and open a discusion in the future about what is considered public/private in these ambiguous cases and what can users expect regarding stability and backwards compatibility.
History
Date User Action Args
2021-09-22 10:05:14pablogsalsetrecipients: + pablogsal, gvanrossum, rhettinger, jpe, scoder, vstinner, petr.viktorin, Mark.Shannon, hroncok, erlendaasland, Xtrem532
2021-09-22 10:05:13pablogsalsetmessageid: <1632305113.97.0.420535333616.issue43760@roundup.psfhosted.org>
2021-09-22 10:05:13pablogsallinkissue43760 messages
2021-09-22 10:05:13pablogsalcreate