[IronPython] true division?

2006-09-21 Thread Gary Stephenson
Is there a way to get true division in ipy without using the -Qnew command line option? On a per-module or per-instance basis? "from __future__ import true_division" returns "SyntaxError: future feature is not defined: true_division" I see in the Issue Tracker for work item 2206 it says f

Re: [IronPython] true division?

2006-09-21 Thread Sanghyeon Seo
2006/9/21, Gary Stephenson <[EMAIL PROTECTED]>: > Is there a way to get true division in ipy without using the -Qnew command > line option? On a per-module or per-instance basis? > > "from __future__ import true_division" > returns "SyntaxError: future feature is not defined: true_division" Of co

Re: [IronPython] true division?

2006-09-21 Thread John Machin
On 21/09/2006 7:27 PM, Sanghyeon Seo wrote: > 2006/9/21, Gary Stephenson <[EMAIL PROTECTED]>: >> Is there a way to get true division in ipy without using the -Qnew command >> line option? On a per-module or per-instance basis? >> >> "from __future__ import true_division" >> returns "SyntaxError: f

[IronPython] Implicit line joining error of ipy.exe interactive session.

2006-09-21 Thread HEMMI, Shigeru
Hello, In interactive ipy.exe session, implicit line joining causes an error if a datum structure has both list and dictionary at the same time. IronPython 1.0.60816 on .NET 2.0.50727.42 Copyright (c) Microsoft Corporation. All rights reserved. >>> x = [{"a":0, "b":1},[2,3,4,5]] >>> x = [{"a":0,

[IronPython] int.__int__ doesn't exist in IP

2006-09-21 Thread Jan Szumiec
Hello, Me and Michael just noticed that there is a inconsistency between CP and IP, namely in CP the int object has an __int__ attribute, whereas in IP it does not. Is this behavior by design, or is it a bug? Thanks, Jan Szumiec Resolver Systems ___

[IronPython] IronPython contributions

2006-09-21 Thread David Fraser
Hi Martin Thanks for the links. The most relevant message I found on the list stating Microsoft's position was http://lists.ironpython.com/pipermail/users-ironpython.com/2005-March/000326.html in which Jim Hugunin states: > That said, we're not going to be accepting any external code > contributio

Re: [IronPython] int.__int__ doesn't exist in IP

2006-09-21 Thread Dino Viehland
Definitely a bug - thanks for reporting this, I've opened CodePlex bug #3529 to track the issue (http://www.codeplex.com/WorkItem/View.aspx?ProjectName=IronPython&WorkItemId=3529). From: [EMAIL PROTECTED] On Behalf Of Jan Szumiec Sent: Thursday, September

Re: [IronPython] Implicit line joining error of ipy.exe interactive session.

2006-09-21 Thread Dino Viehland
Thanks for the bug report. I've opened CodePlex bug #3530 to track this (http://www.codeplex.com/WorkItem/View.aspx?ProjectName=IronPython&WorkItemId=3530) From: [EMAIL PROTECTED] On Behalf Of HEMMI, Shigeru Sent: Thursday, September 21, 2006 3:06 AM To:

[IronPython] Problems with PythonSyntaxErrorException

2006-09-21 Thread Mike McGavin
Hello. We've been attempting to use IronPython as a scripting engine for an application we've been writing. So far it's mostly been working out, but when trying to report errors about any incoming script, I've noticed that the PyhonSyntaxErrorException.LineText property seems to be inconsistent w

Re: [IronPython] true division?

2006-09-21 Thread Gary Stephenson
Thanks John (and Seo), When I attempt the same thing I get: IronPython 1.0.60816 on .NET 2.0.50727.42 Copyright (c) Microsoft Corporation. All rights reserved. >>> import __future__ Traceback (most recent call last): File , line 0, in ##3 File , line 0, in __import__##7 ImportError: No modul

Re: [IronPython] true division?

2006-09-21 Thread Michael Foord
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 ;-) Fuzzyman http://www.voidspace.org.uk > IronPython 1.0.60816 on .NET 2.0.50727.42 > Copyright (c) Microsoft Corporation. All ri

Re: [IronPython] true division?

2006-09-21 Thread Gary Stephenson
What does the wink mean? Is it not a fair question as to why a simple statement seems to work for John (and presumably both Seo and yourself) and yet fails for me? Both syntaxes ("import __future__" and "from __future__ import division") return the same ImportError. Why? Have I offended some

Re: [IronPython] true division?

2006-09-21 Thread John Machin
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 synt

Re: [IronPython] true division?

2006-09-21 Thread Gary Stephenson
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"

Re: [IronPython] true division?

2006-09-21 Thread John Machin
On 22/09/2006 10:15 AM, Gary Stephenson wrote: > 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" >

Re: [IronPython] true division?

2006-09-21 Thread Gary Stephenson
Hi John > The difference in this case is that IronPython has special-cased the > "from __future__ import whatever" caper -- there is no module called > __future__ in IronPython. Note the different error messages below: > > | >>> from __future__ import somerubbish > | Traceback (most recent call la

[IronPython] compiling exe

2006-09-21 Thread asu
How to make exe a file? ipy -X:SaveAssemblies wfdemo.py wfdemo.exe not work. Exception: Just-In-Time Debugging "An exception System.IO.FileNotFoundException..." Anton Orekhov ___ users mailing list users@lists.ironpython.com http://lists.ironpython.com