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 ncoghlan
Recipients brett.cannon, eric.snow, ncoghlan
Date 2016-01-17.02:24:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1452997451.95.0.445766275955.issue21762@psf.upfronthosting.co.za>
In-reply-to
Content
That approach sounds good to me.

The main problem cases I'm aware of are:

__name__:

* reliably wrong in __main__
* the attribute you mess with if you want __qualname__ on functions and classes to be different so that pickle will import them from somewhere else (e.g. a parent package)

__path__:

* used for dynamic package definitions (including namespace package emulation)

__package__:

* AFAIK, mainly useful as a workaround for other people doing "bad things" (TM), like running package submodules directly as __main__ rather than using the -m switch
History
Date User Action Args
2016-01-17 02:24:11ncoghlansetrecipients: + ncoghlan, brett.cannon, eric.snow
2016-01-17 02:24:11ncoghlansetmessageid: <1452997451.95.0.445766275955.issue21762@psf.upfronthosting.co.za>
2016-01-17 02:24:11ncoghlanlinkissue21762 messages
2016-01-17 02:24:10ncoghlancreate