Do not use .message attributes in exceptions, deprecated in 2.6
Bug #407836 reported by
Fernando Perez
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
IPython |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Running the test suite under 2.6 shows:
/home/fperez/
The code reads:
class CompositeError(
def __init__(self, message, elist):
self.elist = elist
I don't want to change that for 0.10 because I'm pretty sure I'll break something. But for 0.11, we should clean this up.
To post a comment you must log in.
I will look at this for 0.11.
On Sat, Aug 1, 2009 at 4:09 PM, Fernando Perez <email address hidden> wrote:
> Public bug reported: usr/lib/ python2. 6/site- packages/ IPython/ kernel/ error.py: 127: message has been deprecated as of Python KernelError) : __init_ _(self, *(message, elist)) /bugs.launchpad .net/bugs/ 407836 usr/lib/ python2. 6/site- packages/ IPython/ kernel/ error.py: 127: message has been deprecated as of Python KernelError) : __init_ _(self, *(message, elist))
>
> Running the test suite under 2.6 shows:
>
> /home/fperez/
> DeprecationWarning: BaseException.
> 2.6
>
> The code reads:
>
> class CompositeError(
> def __init__(self, message, elist):
> Exception.
> self.message = message
> self.elist = elist
>
> I don't want to change that for 0.10 because I'm pretty sure I'll break
> something. But for 0.11, we should clean this up.
>
> ** Affects: ipython
> Importance: Medium
> Status: Confirmed
>
> --
> Do not use .message attributes in exceptions, deprecated in 2.6
> https:/
> You received this bug notification because you are a member of IPython
> Developers, which is subscribed to IPython.
>
> Status in IPython - Enhanced Interactive Python: Confirmed
>
> Bug description:
> Running the test suite under 2.6 shows:
>
> /home/fperez/
> DeprecationWarning: BaseException.
> 2.6
>
> The code reads:
>
> class CompositeError(
> def __init__(self, message, elist):
> Exception.
> self.message = message
> self.elist = elist
>
> I don't want to change that for 0.10 because I'm pretty sure I'll break
> something. But for 0.11, we should clean this up.
>
--
Brian E. Granger, Ph.D.
Assistant Professor of Physics
Cal Poly State University, San Luis Obispo
<email address hidden>
<email address hidden>