Bob Ippolito wrote:
>
> On May 17, 2005, at 10:42 PM, Curt Hagenlocher wrote:
>
> >> Is this bug known?
> >> That is, if a module fails to import, a second attempt to import
does
> >> not throw an exception. I think this is because
> >> Importer.LoadFromSource puts the module into sys.modules bef
http://zephyrfalcon.org/weblog2/arch_e10_00590.html
http://www.voidspace.org.uk/python/articles/upgrading_python.html#id25
Some people claim that 1.5.2 is the One True Python. I only started using it at
2.2, so my brain may be a little warped in that regard...
> Bob Ippolito writes:
>
> > On
Bob Ippolito writes:
> On May 18, 2005, at 12:23 AM, Curt Hagenlocher wrote:
>> Figures. I'm still using 1.5.2 :)
>
> And you have a version of Windows new enough to run .NET 2.0?
> Amazing :)
Hey, 1.5.2 works just fine on Windows 2003!
--
Curt Hagenlocher
[EMAIL PROTECTED]
___
On May 18, 2005, at 12:23 AM, Curt Hagenlocher wrote:
On May 17, 2005, at 10:42 PM, Curt Hagenlocher wrote:
I believe that this behavior is consistent with that of CPython.
Consistent with CPython < 2.4. The behavior has changed.
Figures. I'm still using 1.5.2 :)
And you have a version of Window
> On May 17, 2005, at 10:42 PM, Curt Hagenlocher wrote:
>
> > I believe that this behavior is consistent with that of CPython.
>
> Consistent with CPython < 2.4. The behavior has changed.
Figures. I'm still using 1.5.2 :)
--
Curt Hagenlocher
[EMAIL PROTECTED]
_
On 5/17/05, Curt Hagenlocher <[EMAIL PROTECTED]> wrote:
> > Is this bug known?
> > That is, if a module fails to import, a second attempt to import does
> > not throw an exception. I think this is because
> > Importer.LoadFromSource puts the module into sys.modules before
> > calling the import fun
On May 17, 2005, at 10:42 PM, Curt Hagenlocher wrote:
Is this bug known?
That is, if a module fails to import, a second attempt to import does
not throw an exception. I think this is because
Importer.LoadFromSource puts the module into sys.modules before
calling the import function, but does not re
> Is this bug known?
> That is, if a module fails to import, a second attempt to import does
> not throw an exception. I think this is because
> Importer.LoadFromSource puts the module into sys.modules before
> calling the import function, but does not remove it if the import
> function fails.
I b
Is this bug known?
In file foo.py:
import bar
At the IronPython console:
>>> import foo
[[ Giant exception stack trace ]]
>>> import foo
>>>
That is, if a module fails to import, a second attempt to import does
not throw an exception. I think this is because
Importer.LoadFr
