The IronPython ones should be working, and nothing I did should change
IronRuby's installer builds. However, the old build script may
reference IronPython installers that no longer exist.
- Jeff
On Tue, Jan 3, 2012 at 8:14 PM, Tomas Matousek
wrote:
> Yes, the installer is broken. Jeff is working
I did a git pull today of IronLanguages\main, and noticed a giant stack of
changes on December 30, 31 and Jan 1 - which look like they're related to
Win8 and Mango, amongst other things.
I'm trying to build the IronRuby installer - the process also builds the
IronPython installer along with it.
Yes, the installer is broken. Jeff is working on some better installer building
scripts. I'm not sure what the status is atm.
Tomas
From: [email protected]
[mailto:[email protected]] On Behalf Of Orion Edwards
Sent: Tuesday, January 03, 2012 8:07 PM
To: ironr
When the development was all done inside of Microsoft we had a gated check-in
system called SNAP. TestRunner was a just a simple way to dump all of the
metadata about the tests from that system and have an easy way to run them all.
It wasn't necessarily meant to be a long-term solution.
I kno
Is there a specific reason that IronPython is using TestRunner as opposed
to just extending something like xUnit or NUnit?
___
Ironpython-users mailing list
[email protected]
http://mail.python.org/mailman/listinfo/ironpython-users
Hi ironpython,
Here's your Daily Digest of new issues for project "IronPython".
In today's digest:ISSUES
1. [New issue] Regression: __reduce_ex__ and __reduce__ fails for None
2. [New issue] Type error from string input to class inheriting int
3. [New issue] Support PyCapsule type module extens
