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 MLModel, asvetlov, cben, gpolo, kbk, terry.reedy
Date 2015-05-18.21:50:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1431985801.28.0.0280479666335.issue5233@psf.upfronthosting.co.za>
In-reply-to
Content
Related issue #22893 is about __future__ statements in startup code having effect on future interactive input in the same way as it does with Python itself. I think a pure Shell start/restart (cntl-F6) should be handled separately from a restart that is a side-effect of running an editor file.  There is a separate proposal to specify an individual file's startup condition (sys.args + STARTUP file).  For Shell restart, a possible reason might be to get rid of the effect of a STARTUP file.  Since ^F6 is rarely used (I think), asking whether to include the STARTUP might not be too intrusive.

I think default behaviors should follow Python, though we can add more.  On the other hand, Python has startup options not currently available with Idle.
History
Date User Action Args
2015-05-18 21:50:01terry.reedysetrecipients: + terry.reedy, kbk, cben, gpolo, MLModel, asvetlov
2015-05-18 21:50:01terry.reedysetmessageid: <1431985801.28.0.0280479666335.issue5233@psf.upfronthosting.co.za>
2015-05-18 21:50:01terry.reedylinkissue5233 messages
2015-05-18 21:50:00terry.reedycreate