[IronPython] Re: IronPython 0.7.4 released

[Anthony Tarlano]

Great job geeting 0.7.4 out the door!!

Thanks for the heads up that it's possible to just grab the Lib
directory from Python-2.3.5 and replace the IPython/bin/Lib directory
to get the ball rolling...

One big question comes to mind now that I have all those nice stdlib
.py files.. Do you intend to adapt the python stdlib to work
seamlessly in IronPython 1.0?

If you don't think this is the plan then I will start a project to get
this work done.. Please let me know as to not re-invent the wheel.

Anthony
 





On 5/4/05, Jim Hugunin <jimhug at exchange.microsoft.com> wrote:
> Nick Jacobson wrote:
> > What are nstr and zip2?
> 
> Two little hacks that I wrote a long time ago while playing around with
> different implementation and performance ideas.  They don't belong in
> __builtins__ any more and will be removed.  In case you're curious:
> 
> nstr is an ascii string type that I was experimenting with to see how
> well two different kinds of strings would work in IronPython vs.
> everything being a Unicode System.String.  This design didn't work very
> well, but I forgot to remove this reference from __builtins__.  There's
> still a chance that this will be revisited before IronPython 1.0;
> however, I'm pretty committed to using the single CLS string type if at
> all possible.
> 
> zip2 is a version of the zip function specialized for the most common
> case of two arguments.  It should be a private implementation detail.  I
> exposed it when looking at benchmarks to see if there were any
> noticeable performance benefits to get from calling it directly.
> 
> Time to do some more house cleaning - Jim
> _______________________________________________
> users-ironpython.com mailing list
> users-ironpython.com at lists.ironpython.com
> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>