Owen Williams wrote:
On Wed, 2006-09-27 at 14:54 -0500, Ian Bicking wrote:
Owen Williams wrote:
On Wed, 2006-09-27 at 14:26 -0500, Ian Bicking wrote:
I'm thinking that the Sugar jhbuild should probably use
virtual-python.py: http://peak.telecommunity.com/dist/virtual-python.py
Alternately (and particularly if OLPC goes to Python 2.5), Python should
be built as part of the build process. virtual-python basically
symlinks Python so it doesn't pick anything up from the global
installation. It's like building a custom Python, but faster since it
doesn't actually build anything.
I had asked for this feature, so Marco pushed python into jhbuild. It
was a start, but it didn't have the dbus bindings. If we use a custom
python, someone will need to make sure that all of the bindings olpc
supports are actually installed by jhbuild.
When you say he pushed python into jhbuild, do you mean the $PYTHONPATH
stuff?
He put Python 2.4.3 into jhbuild, ie the whole thing I think.
Is it hiding from me, or did I not build it somehow? I'd expect
build/bin/python to exist, plus build/lib/python2.4 should be full of
stdlib modules. If it's not there but planned to be there, then forget
about virtual-python, a custom build will cover this issue for me.
--
Ian Bicking | [EMAIL PROTECTED] | http://blog.ianbicking.org
_______________________________________________
Sugar mailing list
[email protected]
http://mailman.laptop.org/mailman/listinfo/sugar
