Skip Menu |

This queue is for tickets about the Python-Serialize-Pickle-InlinePython CPAN distribution.

Report information
The Basics
Id: 74955
Status: open
Priority: 0/
Queue: Python-Serialize-Pickle-InlinePython

People
Owner: Nobody in particular
Requestors: nine [...] detonation.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Propagate IOError exception up to Perl
Just wanted to let you know that with more recent Inline::Python versions, one can safely catch a Python exception in Perl with eval. So there should be no need anymore for returning 'IOErrorIOErrorIOErrorIOError' as a special marker :)
Subject: Re: [rt.cpan.org #74955] Propagate IOError exception up to Perl
Date: Tue, 14 Feb 2012 06:55:28 +0900
To: bug-Python-Serialize-Pickle-InlinePython [...] rt.cpan.org
From: Tokuhiro Matsuno <tokuhirom [...] gmail.com>
patches welcome. On Tue, Feb 14, 2012 at 3:32 AM, Stefan Seifert via RT <bug-Python-Serialize-Pickle-InlinePython@rt.cpan.org> wrote: Show quoted text
> Mon Feb 13 13:32:21 2012: Request 74955 was acted upon. > Transaction: Ticket created by NINE >       Queue: Python-Serialize-Pickle-InlinePython >     Subject: Propagate IOError exception up to Perl >   Broken in: (no value) >    Severity: (no value) >       Owner: Nobody >  Requestors: nine@detonation.org >      Status: new >  Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=74955 > > > > Just wanted to let you know that with more recent Inline::Python versions, one can safely > catch a Python exception in Perl with eval. So there should be no need anymore for > returning 'IOErrorIOErrorIOErrorIOError' as a special marker :)