Aha! Many thanks John.
It would appear that there is indeed something of an unwritten law in
operation regarding IronPython, going something like:
"thou shalt always ensure that the CPython Lib be included on thine
sys.path"
cheers,
gary
----- Original Message -----
From: "John Machin" <[EMAIL PROTECTED]>
To: "Discussion of IronPython" <users@lists.ironpython.com>
Sent: Friday, September 22, 2006 10:05 AM
Subject: Re: [IronPython] true division?
> On 22/09/2006 8:10 AM, Michael Foord wrote:
>> Gary Stephenson wrote:
>>> Thanks John (and Seo),
>>>
>>> When I attempt the same thing I get:
>>>
>> Of course. The correct syntax is:
>>>>> from __future__ import division
>>
>> ;-)
>
> Of course nothing.
>
> Gary's original problem has nothing to do with syntax; he used the
> correct syntax (from name1 import name2) but supplied an incorrect value
> (true_division, IIRC) for name2.
>
> In my whimsical advertisement for introspection, IronPython accepted the
> correct syntax (import name1). The difference between my whimsy outcome
> and Gary's is most likely because I've got the CPython Lib on my
> sys.path for IronPython, and he hasn't:
>
> | DOS_prompt>\ironpython\ipy
> | IronPython 1.0.60816 on .NET 2.0.50727.42
> | Copyright (c) Microsoft Corporation. All rights reserved.
> | >>> import __future__
> | >>> __future__.__file__
> | 'C:\\Python24\\Lib\\__future__.py'
> | >>>
>
> HTH,
> John
> _______________________________________________
> users mailing list
> users@lists.ironpython.com
> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>
_______________________________________________
users mailing list
users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
