Message 358128 - Python tracker

➜

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	BTaskaya
Recipients	BTaskaya, Michel Desmoulin, ammar2, gregory.p.smith, lukasz.langa, ncoghlan, r.david.murray, vstinner, xtreak
Date	2019-12-09.18:57:37
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to

Content
I am not sure that if co_filename can break backwards compability or not (because until CodeType.replace; it was usual to break code object construction, people who are using code objects may take this too) but yes PR 17534 was necessary. My initial patch (PR 13527) proposed a future directive to do this (and poorly implemented the concept) which can be helpful (yet it needs a PEP).

I am not sure that if co_filename can break backwards compability or not (because until CodeType.replace; it was usual to break code object construction, people who are using code objects may take this too) but yes PR 17534 was necessary. 

My initial patch (PR 13527) proposed a future directive to do this (and poorly implemented the concept) which can be helpful (yet it needs a PEP).

History
Date	User	Action	Args
2019-12-09 18:57:38	BTaskaya	set	recipients: + BTaskaya, gregory.p.smith, ncoghlan, vstinner, r.david.murray, lukasz.langa, Michel Desmoulin, ammar2, xtreak
2019-12-09 18:57:38	BTaskaya	set	messageid: <[email protected]>
2019-12-09 18:57:38	BTaskaya	link	issue20443 messages
2019-12-09 18:57:37	BTaskaya	create