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 Saimadhav.Heblikar, Todd.Rovito, philwebster, taleinat, terry.reedy
Date 2019-08-12.04:00:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1565582456.95.0.909350343976.issue18766@roundup.psfhosted.org>
In-reply-to
Content
The import-on-demand would be executed in the Shell's execution process namespace, so it works with the current implementation.  I said above that this puts names 'where they don't belong', but I feel a little differently now.  A variant idea might be to execute all imports as entered in the editor in the shell.

A pie-in-the-sky idea is to give each editor its own execution process and execute each line as entered, or something like that.  But I have put off researching what other editors do until we get what we have working better.
History
Date User Action Args
2019-08-12 04:00:56terry.reedysetrecipients: + terry.reedy, taleinat, Todd.Rovito, philwebster, Saimadhav.Heblikar
2019-08-12 04:00:56terry.reedysetmessageid: <1565582456.95.0.909350343976.issue18766@roundup.psfhosted.org>
2019-08-12 04:00:56terry.reedylinkissue18766 messages
2019-08-12 04:00:56terry.reedycreate