Chris:
Thanks for the detailed information. That was pretty much what I was
looking for. It makes everything make sense.
I had tried downloading the mono source and rebuilding -- what an
error! I've spent most of my morning removing the new, broken mono
and replacing the stock version. Ugh!
Once that was done, I went hunting for the newest version of
IronPython which ran on the dotNET 2.0 platform. It is IronPython
2.6.2, a maintenance release with several bug fixes, especially
compared with the Beta2. I copied the binary onto my machine and
tried it. It seems to work quite well, other than the fact that it
turns the black print on my console to grey when it starts, which is a
little weird. I will stick with that version for the time being.
I suggest that the packaging folks consider an upgrade to it soon.
It's a good version of Python, just not good enough for testing
bleeding edge stuff.
Meanwhile, I am downloading an OpenSUSE live USB so that I can test
new IronPython modules on occasion. I will switch back to Ubuntu when
the smoke clears.
--
Vernon
On Sun, Mar 20, 2011 at 3:39 AM, Christopher James Halse Rogers
r...@ubuntu.com wrote:
The Ubuntu mono team is pretty much a subset of the Debain CLI team, and [...]
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
