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 eric.snow
Recipients brett.cannon, cheryl.sabella, eric.snow, ncoghlan, pje
Date 2019-04-10.14:41:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1554907273.22.0.658200338533.issue19476@roundup.psfhosted.org>
In-reply-to
Content
Thanks for checking in, Cheryl!

Clearly no one picked up this banner. :)  Furthermore, I'm not aware of any reload-related complaints coming from the community.  I know of only a couple major use cases for reload():  refresh parts of a running app during development and reload a config (e.g. SIGHUP).  Those use cases seem to be mostly stable.  Given ~4.5 years of zero activity here, I think it's safe to say nothing further is going to happen. :)

So I'm closing this issue.  At this point I don't see much value in keeping it open.  If someone later finds a concrete motivator for more detail about module-reloading in the language reference (or decide they want to drive this effort) then they can re-open this issue (or create a new one) at that point.
History
Date User Action Args
2019-04-10 14:41:13eric.snowsetrecipients: + eric.snow, brett.cannon, pje, ncoghlan, cheryl.sabella
2019-04-10 14:41:13eric.snowsetmessageid: <1554907273.22.0.658200338533.issue19476@roundup.psfhosted.org>
2019-04-10 14:41:13eric.snowlinkissue19476 messages
2019-04-10 14:41:12eric.snowcreate