Hello Python Community,
We’re pleased to announce the second Beta release of IronPython 2.7,
which can be downloaded at
http://ironpython.codeplex.com/releases/view/60193. This release fixes
a number of bugs and adds the zlib and subprocess modules. This is
also the first community release of
I want to make sure I'm on the same page as everyone else when it
comes to issue workflow. What I've been doing is:
* For old bugs that aren't reproducible, just close it.
* For old bugs that are reproducible, add test case and set Release to 2.7.
* When fixing bugs, mark as Fixed, make sure the
I searched in the NuGet gallery http://nuget.org/ for IronPython
http://nuget.org/Packages/Search?packageType=PackagessearchCategory=All+CategoriessearchTerm=ironpythonand
found that the version is still 2.6.1. It might be good to find out the
process for updating this before the 2.7 release.
Is
I've been using my own testcase template to reproduce C#/.NET interop
scenarios. It may be a good idea to include a similar thing in the docs to
try and standardize the testcase code that devs receive.
Richard
On Mon, Feb 7, 2011 at 9:03 AM, Jeff Hardy jdha...@gmail.com wrote:
I want to make
I'm already the owner of that package; I just need to build an
updated. I forgot that it was still on 2.6.1.
The .nuspec file should also be added to the repo and eventually just
part of the build process.
- Jeff
On Mon, Feb 7, 2011 at 5:32 AM, Richard Nienaber rjniena...@gmail.com wrote:
I
Re binaries - 3 flavors are currently built:
1) Desktop CLR 4.0 (.NET FW 4.0, Mono 2.10)
2) Core CLR 4.0 (Silverlight 4.0, Moonlight)
3) Core CLR 3.0 (Windows Phone 7)
So yes, the binaries should be equivalent. They won't be byte-for-byte equal,
but should functionally be the
I was wondering how this is progressing. Is there any chance that this could
be incorporated into the release of 2.7? This
issuehttp://ironpython.codeplex.com/workitem/21395is sitting on 14
votes and it would be great if we could close it.
Richard
On Tue, Jan 11, 2011 at 2:41 AM, Slide
