It does not seem to work with distribute (it exits with a
StackOverflowException). I'll dig into it a little more.
slide
On Wed, Mar 7, 2012 at 3:59 PM, Jeff Hardy wrote:
> On Wed, Mar 7, 2012 at 2:54 PM, Slide wrote:
> > Just as an FYI, I committed some fixes today that should allow
> setupto
Hello,
We are considering IronPython for a new automation infrastructure
project; it will not be used to write automated tests though.
I wasn't aware that MS bailed on the Irons (back at 2010) until a few
days ago, this will probably hurt my arguments, let alone other chatter
on the web saying th
Hi ironpython,
Here's your Daily Digest of new issues for project "IronPython".
In today's digest:ISSUES
1. [Status update] IronPython 1.1: test_urllibnet.py failing
2. [Status update] (CPy) test_import.py fails with StackOverflow exception
3. [Status update] PythonErrorSink moves to IPy
4. [New
Hi All,
I am using Ironpython (2.7) to call a python script from my C# console
application. The code executes fine. But when I try to terminate the console by
clicking 'X' , I get the below error message:
---
Intel(r) Visual Fortran run-time error
-
If you remove IronPython from the app and do the same thing, do you still
get the error? I've never seen that error before.
On Mar 13, 2012 6:21 PM, "surangika ranathunga"
wrote:
> Hi All,
> I am using Ironpython (2.7) to call a python script from my C# console
> application. The code executes f
Jeff or Dino (or anyone else who might knows),
Is there any specific reason we aren't using the __future__.py directly
from the stdlib? I ran into an issue today with doctest when it was
extracting future flags, nested_scopes was not defined in the __future__.py
that is located at Languages/IronPy
