Message 189163 - 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	gvanrossum
Recipients	brett.cannon, eli.bendersky, ethan.furman, gvanrossum, ncoghlan, rhettinger, vstinner
Date	2013-05-13.18:37:03
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1368470223.77.0.892473170027.issue17963@psf.upfronthosting.co.za>
In-reply-to

Content
As I explained in issue 17947, I think that any Python implementation worth its salt should be able to implement sys.get_calling_module_name() (), at least for the case where the caller is top-level code in a module body. That is a much weaker requirement than being able to implement sys._getframe(). We should just add this to CPython 3.4 and require that conforming implementations support it, at least in the stated context (top-level caller). () Please pick a somewhat shorter name for it.

As I explained in issue 17947, I think that any Python implementation worth its salt should be able to implement sys.get_calling_module_name() (*), at least for the case where the caller is top-level code in a module body.  That is a much weaker requirement than being able to implement sys._getframe().  We should just add this to CPython 3.4 and require that conforming implementations support it, at least in the stated context (top-level caller).

(*) Please pick a somewhat shorter name for it.

History
Date	User	Action	Args
2013-05-13 18:37:03	gvanrossum	set	recipients: + gvanrossum, brett.cannon, rhettinger, ncoghlan, vstinner, eli.bendersky, ethan.furman
2013-05-13 18:37:03	gvanrossum	set	messageid: <1368470223.77.0.892473170027.issue17963@psf.upfronthosting.co.za>
2013-05-13 18:37:03	gvanrossum	link	issue17963 messages
2013-05-13 18:37:03	gvanrossum	create