[Chandler-dev] Python 2.5?

Mikeal Rogers mikeal at osafoundation.org
Thu Nov 30 16:43:27 PST 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I think this is a good time to bring up something I've wondered about.

Why do we always pull down our own version of python?

It would be nice if we could simply have a list of python  
requirements and have Chandler use the installed python if specified.

I like the ease of simply downloading a .app and running it with  
python already there, but why is this an absolute requirement. It  
seems to also make upgrades like this a lot harder. Are there some  
changes in our version of python that make it incompatible?

- -Mikeal

On Nov 30, 2006, at 4:17 PM, Heikki Toivonen wrote:

> 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
>
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "chandler-dev" mailing list
> http://lists.osafoundation.org/mailman/listinfo/chandler-dev

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFFb3qvIy1Ff2Qzo+wRAkKEAJ9rDT5j2IWl1spyHGnz3nu2XSl+SgCfRxFc
9ie27elg3QUQ6FCay3x7CnE=
=pqlL
-----END PGP SIGNATURE-----


More information about the chandler-dev mailing list