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 taleinat
Recipients gpolo, taleinat
Date 2009-03-29.22:01:32
SpamBayes Score 9.7981e-09
Marked as misclassified No
Message-id <1238364094.7.0.485215180018.issue1757057@psf.upfronthosting.co.za>
In-reply-to
Content
Sending a code object back to the parent process and having it deal with
the situation sounds very unpleasant indeed! I think a completely
different type of solution may be possible.

In general, I can't think of any reason for IDLE to pickle "user
objects" from the subprocess and send them to the parent process; it
should merely send back the output (as strings), with special cases for
exceptions and such. By "user objects" I mean objects "inside the
interpreter", as opposed to those used by IDLE itself.

I'll have to unwind the spaghetti in rpc.py, run.py and PyShell.py a bit
more to propose a specific set of changes; I hope to get to that tomorrow.
History
Date User Action Args
2009-03-29 22:01:35taleinatsetrecipients: + taleinat, gpolo
2009-03-29 22:01:34taleinatsetmessageid: <1238364094.7.0.485215180018.issue1757057@psf.upfronthosting.co.za>
2009-03-29 22:01:33taleinatlinkissue1757057 messages
2009-03-29 22:01:32taleinatcreate