Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report for Bug 41140 on
GitHub or Developer Community if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Following up on
The current bundled ironpython is a snapshot off master from nearly 5 years ago,
577 commits behind current master and 614 behind
ipy-2.7-maint (and 130 from the last common ancestor with ipy-2.7-maint)
as of now. It is also a bit surprising it claims to be 3.0 but did not
come from git://github.com/IronLanguages/ironpython3.git .
It appears that most current activity seems to be on
git://github.com/IronLanguages/main.git:ipy-2.7-maint - would it make
sense to switch to a more recent git://github.com/IronLanguages/main.git:ipy-2.7-maint
or one of its release tags instead?
I would suggest upgrading to 2.7.5 release, or the next (2.7.6) if it is coming out any time soon.
Also, note that more recent version of ironpython comes with tuned version of the python standard library modules. So it might be a shock during recursive copying of the install.
I briefly attempted to build a more recent version of IronPython but the Mono build was broken in several places. I'll come around to it again, but if anyone knows of a recent version that builds I'll switch to it right away.
I don't remember having problem building git://github.com/IronLanguages/main.git ipy-2.7-maint branch a couple of weeks ago with 188.8.131.52 . The ipy-2.7-maint branch is also the HEAD of git://github.com/IronLanguages/main.git (rather than master), and although it only says 2.7.6-a0... , seem to be where all the recent activities are.
@Alexis Christoforides : you are right! HEAD does not build with the default target. I did not notice because I was primarily interested in supporting older runtime, and therefore built it with:
xbuild Solutions/IronPython.sln /p:Configuration="v2Release"
This works for both the ipy-2.7.5: tag and current head (2b528dccee9e973b94ac00a0dbc14b0ebb030c6d:). with - I have a bare clone -:
git archive --prefix=2b528dccee9e973b94ac00a0dbc14b0ebb030c6d/ 2b528dccee9e973b94ac00a0dbc14b0ebb030c6d: | ( cd /tmp && tar -xpvf - )
$ mono --version
Mono JIT compiler version 4.2.2 (Stable 184.108.40.206/996df3c Sun Feb 14 19:54:12 GMT 2016)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
LLVM: supported, not enabled.
Filed issue upstream - https://github.com/IronLanguages/main/issues/1297 .
xbuild Solutions/IronPython.sln /p:Configuration="Release"
probably only needs a small fix to get it to work; but /p:Configuration="v2Release" works now.
We should probably remove ironpython from our packages since its available as a nuget: