Message84425
| Author |
gpolo |
| Recipients |
gpolo, taleinat |
| Date |
2009年03月29日.19:49:24 |
| SpamBayes Score |
4.0539157e-06 |
| Marked as misclassified |
No |
| Message-id |
<ac2200130903291249i125efba7le61b3d0a27a34641@mail.gmail.com> |
| In-reply-to |
<1238342362.29.0.506569372271.issue1757057@psf.upfronthosting.co.za> |
| Content |
> IMO IDLE should check for any exception
> (not just pickle.PicklingError) when trying to pickle an object for
> sending to the parent process. If pickle doesn't work, for whatever
> reason, IDLE can still try to work around it with str() and/or repr().
>
Do you have some specific suggestion on how to do so ? As I'm seeing
it rpc.SocketIO.putmessage would return a custom exception when a
PicklingError doesn't happen, which then
PyShell.ModifiedInterpreter.runcode could handle and decide to run the
code object locally. Sounds unpleasant. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2009年03月29日 19:49:29 | gpolo | set | recipients:
+ gpolo, taleinat |
| 2009年03月29日 19:49:27 | gpolo | link | issue1757057 messages |
| 2009年03月29日 19:49:25 | gpolo | create |
|