On Mon, Feb 11, 2013 at 9:23 AM, Barry Warsaw wrote:
> On Feb 11, 2013, at 09:23 PM, Nick Coghlan wrote:
>
> >On Mon, Feb 11, 2013 at 8:58 PM, Chris Withers
> wrote:
> >> Have any other exceptions grown new attributes in Python 3?
> >
> >Off the top of my head, ImportError grew "name" and "path"
On Feb 11, 2013, at 09:23 PM, Nick Coghlan wrote:
>On Mon, Feb 11, 2013 at 8:58 PM, Chris Withers wrote:
>> Have any other exceptions grown new attributes in Python 3?
>
>Off the top of my head, ImportError grew "name" and "path" attributes
>in 3.3, everything grew __cause__, __context__ and __tr
On Mon, Feb 11, 2013 at 8:58 PM, Chris Withers wrote:
> Have any other exceptions grown new attributes in Python 3?
Off the top of my head, ImportError grew "name" and "path" attributes
in 3.3, everything grew __cause__, __context__ and __traceback__
attributes in 3.0 and the __suppress_context__
On 11/02/2013 10:54, Nick Coghlan wrote:
On Mon, Feb 11, 2013 at 6:08 PM, Chris Withers wrote:
Hi All,
I see in Python 3, some ImportErrors have grown a '_not_found' attribute.
What's the significance of this attribute and where/how is it added?
The only way I can seem to create this attribut
On Mon, Feb 11, 2013 at 6:08 PM, Chris Withers wrote:
> Hi All,
>
> I see in Python 3, some ImportErrors have grown a '_not_found' attribute.
> What's the significance of this attribute and where/how is it added?
>
> The only way I can seem to create this attribute is:
>
> ex = ImportError
> ex._n
Hi All,
I see in Python 3, some ImportErrors have grown a '_not_found'
attribute. What's the significance of this attribute and where/how is it
added?
The only way I can seem to create this attribute is:
ex = ImportError
ex._not_found = True
cheers,
Chris
--
Simplistix - Content Managemen
