Python 2.5 came out a little while ago. It is a fairly significant
release, adding some nice new features in the language. AFAIK at least
one feature would enable us to fix a repository bug. 2.5 is also
significantly faster than 2.4. Finally, 2.5 contains some security fixes
that have never been ported to 2.4.

I also believe that 2.5 included build changes which will make it
possible to build it with the free Microsoft Visual C++ 2005 Express
edition. Besides being free, I believe it produces slightly faster and
better code than our current compiler.

All good reasons for us to upgrade to 2.5 at the first opportunity.

However, there are also downsides. My main gripe, as usual, is that it
would once again push further the time when we could use the platform
Python to run Chandler (at least on Linux).

More information about Python 2.5 is here:
http://www.python.org/download/releases/2.5/

So, there are some options available for us:

1) Upgrade and require 2.5
2) Upgrade to 2.5 but let Chandler still run with 2.4
   - this would require some version dependent imports for files that
wanted to use certain 2.5 features
3) Don't upgrade

Personally I am slightly in favor of 2) because of the possibility of
using the system Python on Linux. My second choice is 1).

If we decide to upgrade, I think we should aim to do it in alpha5.

Also, I think we should switch to Microsoft Visual C++ 2005 Express
edition as the compiler on Windows.

The 2.5 upgrade bug is here:
https://bugzilla.osafoundation.org/show_bug.cgi?id=6704

Please add any bugs that are blocking that or depend on that to Bugzilla.

Thoughts?

-- 
  Heikki Toivonen


Attachment: signature.asc
Description: OpenPGP digital signature

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev

Reply via email to