Hello all,
Olav Vitters [2012-11-05 10:05 +0100]:
In the last release team meeting we've accepted the Python 3 porting
goal for GNOME 3.8.
https://live.gnome.org/GnomeGoals/Python3Porting
Meaning: During development phase of GNOME 3.8 (3.7.x) we will depend on
Python 3.
*applauds*
I
Hi,
My name is Jorge and I'm a gnome user from Barcelona. Thank you for
your amazing work!
I'm not sure if this is the right list to send this message so excuse
me in case this is not.
I recently began to read a book [1] about PhoneGap (Apache Cordova)
framework [2]. If you don't know it, it's
On Mon, Nov 05, 2012 at 10:28:35AM +0100, Martin Pitt wrote:
Should I just change the default to python3, so that jhbuild will
from now on build for py3 unless you explicitly configure for python2?
That would go along with that goal, but would break modules which
expect pygobject for py2.
The
On Mon, Nov 5, 2012 at 4:56 AM, Olav Vitters o...@vitters.nl wrote:
I prefer a jhbuild hack as it seems easier. Any distribution likely
already dealt with this.
For Fedora, we have a python3-gobject package.
I think what the goal page is missing is some advice on how to
concretely do the
On Mon, Nov 05, 2012 at 06:45:04AM -0500, Matthias Clasen wrote:
On Mon, Nov 5, 2012 at 4:56 AM, Olav Vitters o...@vitters.nl wrote:
I prefer a jhbuild hack as it seems easier. Any distribution likely
already dealt with this.
For Fedora, we have a python3-gobject package.
I think
On Mon, 2012-11-05 at 10:28 +0100, Martin Pitt wrote:
but if we now want to port GNOME to py3, I guess this should be
rearranged.
Should I just change the default to python3, so that jhbuild will
from now on build for py3 unless you explicitly configure for python2?
That would go along
See also:
https://bugzilla.gnome.org/show_bug.cgi?id=658237
And the original train wreck:
https://bugzilla.gnome.org/show_bug.cgi?id=650763
If we don't have a concrete plan for how stuff like the shebang lines
work, the mess is just going to get worse. And ideally, we share
infrastructure
Matthias Clasen [2012-11-05 6:45 -0500]:
For Fedora, we have a python3-gobject package.
Same for Debian/Ubuntu, our pygobject source package builds both
python-gi (for py 2) and python3-gi, and they are co-installable.
I think what the goal page is missing is some advice on how to
concretely
Olav Vitters [2012-11-05 13:19 +0100]:
There is also a script to change v2 to v3. Then I assume run it and
done.
More precisely there is the tool 2to3 which is shipped with py3. It
gets the syntactic changes out of the way, and also copes with renamed
imports and some straightforward
Colin Walters [2012-11-05 11:12 -0500]:
--with-python-major=2/3/auto
As I mentioned before, this is easier to work with for build systems and
more reliable than environment variables.
Ack. However, I'd change this to
--with-python=command
and default to python3 if available; if not
On Mon, 2012-11-05 at 17:33 +0100, Martin Pitt wrote:
So for the fake pygobject-py2 jhbuild project we'd specify
--with-python=python2.
Does that sound acceptable?
Makes sense, yeah. So you're suggesting this gets propagated into the
shebang lines too? If so...that does allow us to kind
Colin Walters wrote:
The whole thing is just so horrible...Python upstream should have just
accepted they made a different (but closely related) programming
language and said python is always python2, and python3 is 3, or
they should have made a python2 symlink upstream for the old branch, so
On Mon, 2012-11-05 at 11:45 -0500, Colin Walters wrote:
Probably the least bad thing to do is for jhbuild, just pass
--with-python=python3 for pygobject, and --with-python=python2 for
pygobject-py2. Then we test in jhbuild if /usr/bin/python is Python 2,
*and* there's no /usr/bin/python2
On Mon, Nov 05, 2012 at 08:04:50AM -0500, Colin Walters wrote:
Longer answer: The Python3 porting should really be focused along
runtime/devel lines first. What I mean by this is that ideally for a
If someone could add some priority to the modules I'd appreciate. The
Python3 porting is one of
Martin Pitt [2012-11-05 17:33 +0100]:
Ack. However, I'd change this to
--with-python=command
and default to python3 if available; if not fall back to python.
Clarification: Due to the unhelpfully undefined behaviour of python
in PEP-394, we can't rely on that, so we'd fall back to
15 matches
Mail list logo
