Only a week? :)
Keeping m low alleviates some concern for your sanity, but I worry about n,
then?
-Original Message-
From: Dave Fugate
Sent: Wednesday, January 06, 2010 11:43
To: Discussion of IronPython
Subject: Re: [IronPython] IronPython 2.0.3
There's one major benefit
Fugate
> Sent: Wednesday, January 06, 2010 11:43 AM
> To: Discussion of IronPython
> Subject: Re: [IronPython] IronPython 2.0.3
>
> There's one major benefit of n different IronPython versions though - testing.
> Right now, we run all CPy 2.6 tests for every IronPython (2.6) ch
, 2010 11:21 AM
To: Discussion of IronPython
Subject: Re: [IronPython] IronPython 2.0.3
Yet you end up (worst case)maintaining nm different versions of the entire
source, n CPython compats by m NetFX compats? That's not a great space to be
in, and then end-users have to hunt for the IronPython versio
Sent: Wednesday, January 06, 2010 10:23
To: Discussion of IronPython
Subject: Re: [IronPython] IronPython 2.0.3
Keith wrote:
> I was wondering if it might not be better (even possible) to merge the version
> compatibility into a switch, so people would optionally use a targetVersion
> fla
Keith wrote:
> I was wondering if it might not be better (even possible) to merge the version
> compatibility into a switch, so people would optionally use a targetVersion
> flag or some-such.
>
> Part of the difference between versions isn't simply language, it's outright
> bug corrections and co
y with the base DLR, neh?
-Original Message-
From: users-boun...@lists.ironpython.com
[mailto:users-boun...@lists.ironpython.com] On Behalf Of Dino Viehland
Sent: Wednesday, January 06, 2010 9:21 AM
To: Discussion of IronPython
Subject: Re: [IronPython] IronPython 2.0.3
Yep, 2.0.3 is
n.com
> Subject: [IronPython] IronPython 2.0.3
>
> Hi.
>
> I am seemingly locked into Python 2.5 for compatibility with
> requirements from ESRI based products. I am wanting to write some C#
> code (very new to it) and call it from Python. Should I use IronPython
> 2.0
Hi.
I am seemingly locked into Python 2.5 for compatibility with
requirements from ESRI based products. I am wanting to write some C#
code (very new to it) and call it from Python. Should I use IronPython
2.0.3?
The C# interfaces are from GPS Pathfinder Office application. Hopefully
I detaile
In compiled assemblies, the FolderBrowseDialog window control (Windows
Forms) does not show the folder tree view.
On Fri, Sep 25, 2009 at 4:52 PM, David DiCato wrote:
> As we work towards our IronPython 2.0.3 bugfix release, Dino and I would
> like to get a feel for which bugs left unresolved
Issue 19510 tripped me up today (Need to recognize
DefaultMemberAttribute for __getitem__/__setitem__).
Not sure how important it is to others, but our application uses
ironpython to handle custom data imports (typically xml documents).
There is a workaround, but it involves modification to custom
The issue of parse error for UTF-8 scripts .
Every 1024th byte is truncated.
The problem is fixed for 2.6,
but has not fixed for 2.0 .
http://ironpython.codeplex.com/Wiki/View.aspx?title=2.6%20Release%20Plan
___
Users mailing list
Users@lists.ironpython
As we work towards our IronPython 2.0.3 bugfix release, Dino and I would like
to get a feel for which bugs left unresolved in 2.0.2 are most important for us
to fix in the next release. Please let us know ASAP if there's an issue you'd
like to see fixed in IronPython 2.0.3. Thanks!
_
12 matches
Mail list logo
