Just one other comment on top of what Curt said. You might more properly think of Main as IronPython 3k. Main includes a ton of renames and other breaking made in Microsoft.Scripting.Core/System.Core that will end up in .NET 4.0. We're still working on what we want to do for 2.1 (and input is always welcome of course) but our current thinking is that it will be API compatible w/ 2.0.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Foord Sent: Friday, October 31, 2008 5:24 AM To: Discussion of IronPython Subject: [IronPython] 2.1 Branch in Codeplex Sources Hello guys, I saw a while ago a note about some of the Codeplex source pushes containing code for the 2.1 branch rather than 2.0. Is it possible to tell which is which when we download a changeset? I've just downloaded 42708 (we're trying to keep the Resolver One port using the latest sources to minimise unexpected changes) and it contains 'IronPython_Main' and 'IronPython_2_0'. The assembly info for main shows: AssemblyVersion("2.0.0.5000")] Is this still the 2.0 branch or should I be using 'IronPython_2_0'? How about some checkin messages to go along with the source code drops? "Latest sources migrated to CodePlex TFS" is not terribly informative... Michael -- Michael Foord Senior Software Engineer, Resolver Systems Ltd. [EMAIL PROTECTED] +44 (0) 20 7253 6372 Try out Resolver One! <http://www.resolversystems.com/get-it/> 17a Clerkenwell Road, London EC1M 5RD, UK VAT No.: GB 893 5643 79 Registered in England and Wales as company number 5467329. Registered address: 843 Finchley Road, London NW11 8NA, UK _______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com _______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
