Be careful of what you read in svn ;) That's where the release notes etc. that *will be* 1.0 are being worked on, but there hasn't been a 1.0 yet (that pesky day-job has been busy lately). FWIW - I'll clean up the warning, but otherwise the 1.0 branch should be stable. There are a number of things cooking in the 2.x branch that will need to be back-merged before 1.x (things like __overloads__, IP 'clr' module compatibility, etc.), and I plan to do that as a single effort rather than torture myself with a bunch of mini-merges ;) -Brian
-----Original Message----- From: pythondotnet-bounces@python.org [mailto:pythondotnet-bounces@python.org] On Behalf Of Bruce Dodson Sent: Friday, June 16, 2006 4:07 PM To: pythondotnet@python.org Subject: [Python.NET] Python.NET 1.0 Final
In the change log in SVN I see that there was a 1.0 final release, with the new import semantics back-ported, but still using .NET 1.1 in contrast to the more recent work Brian has been doing.
However, I don't see the updates to the documentation in the 1.0 branch, and also I get an "unreachable code" warning when I try to compile it, so I'm not confident that it is the old branch is complete and tested. Is there a pre-built, tested 1.0 release version available somewhere?
Thanks, Bruce
ps. Unreachable code is after the first return in arrayobject.cs, line 44:
return CLRObject.GetInstHandle(result, tp); string message = "cannot instantiate array wrapper"; return Exceptions.RaiseTypeError(message);
Could be due to a merge that went awry?
_________________________________________________ Python.NET mailing list - PythonDotNet@python.org http://mail.python.org/mailman/listinfo/pythondotnet