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 terry.reedy
Recipients arigo, brett.cannon, eric.snow, ethan.furman, larry, ncoghlan, terry.reedy
Date 2015-06-26.21:05:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1435352719.37.0.597841818603.issue24492@psf.upfronthosting.co.za>
In-reply-to
Content
I view having a string __name__ attribute as part of quacking like a module (or class or function).  Hence pseudonames like '<lambda>' (lambda expression) or <pyshell#n> (the module name for interactive input, where n is the line number).  Is there a good reason for custom 'module' objects to not have a name?  If so, the 'graceful muddle' precedent is to give them a pseudoname, such as <module>, perhaps with a prefix or suffix.
History
Date User Action Args
2015-06-26 21:05:19terry.reedysetrecipients: + terry.reedy, brett.cannon, arigo, ncoghlan, larry, ethan.furman, eric.snow
2015-06-26 21:05:19terry.reedysetmessageid: <1435352719.37.0.597841818603.issue24492@psf.upfronthosting.co.za>
2015-06-26 21:05:19terry.reedylinkissue24492 messages
2015-06-26 21:05:19terry.reedycreate