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 Ramchandra Apte, alex.rodas, philwebster, roger.serwy, terry.reedy, zach.ware
Date 2017-10-28.01:38:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The part about startup files in my last message is probably wrong.  If one starts IDLE by 'import idlelib.idle' after setting 'sys.ps1 = 'me ', then the setting is recognized.  However, a startup file that runs in the user process will not affect sys.ps1 in the IDLE process.  We could add a command line option -p "prompt", but I don't see this as sufficiently important.

At least some shells and consoles recognize special characters in a prompt string to create the prompt.  For instance, the default setting on Windows is "$P$G", which I presume stands for 'working directory path' and 'greater than symbol', with a result such as "F:/dev/3x>".  (I have no idea where this is documented.)  Python and IDLE will print the literal string instead.  Custom prompts therefore seem like an advanced feature, not one aimed at beginners.
Date User Action Args
2017-10-28 01:38:37terry.reedysetrecipients: + terry.reedy, roger.serwy, Ramchandra Apte, zach.ware, alex.rodas, philwebster
2017-10-28 01:38:37terry.reedysetmessageid: <>
2017-10-28 01:38:37terry.reedylinkissue13657 messages
2017-10-28 01:38:36terry.reedycreate