On Sep 7, 2017, at 14:04, Fred Drake <f...@fdrake.net> wrote: > > On Thu, Sep 7, 2017 at 4:52 PM, Terry Reedy <tjre...@udel.edu> wrote: >> Environmental variables tend to be a pain on Windows and nigh unusable by >> beginners. Leaving that aside, I see these problems with trying to use one >> for IDLE's *current* debugger. >> >> pdb is universal, in the sense of working with any python run with actual or >> simulated stdin and stdout. IDLE's idb is specific to working with IDLE. So >> one could not set an EV to 'idlelib.idb.start' and leave it while switching >> between IDLE and console. > > Would it work for IDLE to set the environment variable for the child process?
That’s exactly how I envision the environment variable would be used. If the process being debugged is run in an environment set up by the IDE, this would be the way for the IDE to communicate to the subprocess under debug, how it should behave in order to communicate properly with the debugger. > The user certainly should not need to be involved in that. Right. > That doesn't address the issue of setting up the communications > channel before breakpoint() is called, but allows the breakpointhook > that gets used to work with whatever has been arranged. Right again! I think setting up the communication channel is outside the scope of this PEP. Cheers, -Barry
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
