Re: [gtk-osx-users] Python3

[John Ralls <jralls ceridwen us>]

On Jan 25, 2014, at 8:42 AM, Volker Braun <vbraun name gmail com> wrote:

> There are various Python3 packages, but I can't see how to build gtk3
> + python3. Is this  possible at all? It starts to fail when building
> pycairo-python3:
>
>
> $ ./.local/bin/jhbuild build pycairo-python3
> *** Checking out pixman *** [1/3]
> *** Skipping pixman (package and dependencies not updated) *** [1/3]
> *** Checking out cairo *** [2/3]
> *** Skipping cairo (package and dependencies not updated) *** [2/3]
> *** Checking out pycairo-python3 *** [3/3]
> *** Configuring pycairo-python3 *** [3/3]
> ./waf configure --prefix /Users/vbraun/gtk/inst
>  ./options()
> Setting top to                           :
> /Users/vbraun/gtk/source/pycairo-1.10.0
> Setting out to                           :
> /Users/vbraun/gtk/source/pycairo-1.10.0/build_directory
>  ./configure()
> Checking for 'gcc' (c compiler)          : ok
> Checking for program python              : python
> python executable 'python' different from sys.executable
> '/Users/vbraun/gtk/inst/bin/python'
> Checking for python version              : (2, 7, 3, 'final', 0)
> The python version is too old, expecting (3, 1, 0)
> (complete log in
> /Users/vbraun/gtk/source/pycairo-1.10.0/build_directory/config.log)
> *** Error during phase configure of pycairo-python3: ########## Error
> running ./waf configure --prefix /Users/vbraun/gtk/inst *** [3/3]
>
>  [1] Rerun phase configure
>  [2] Ignore error and continue to build
>  [3] Give up on module
>  [4] Start shell
>  [5] Reload configuration
>  [6] Go to phase "wipe directory and start over"
> choice: 4
> exit shell to continue with build
>
>
> Since jhbuild is python2 only, I can't just run everything with
> python3. And it seems that the .jhbuildrc sets up the Python
> environment depending on what jhbuild is running under. If I switch in
> the shell to python3 then pycairo-python3 works, but  thats not
> exactly a desirable approach for all packages:
>
>
> $ echo $PYTHON
> /Users/vbraun/gtk/inst/bin/python
> $ echo $PYTHONPATH
> /Users/vbraun/gtk/inst/lib/python2.7:/Users/vbraun/gtk/inst/lib/python2.7/site-packages/gtk-2.0:/Users/vbraun/gtk/inst/lib/python2.7/site-packages
> $ export PYTHON=/Users/vbraun/gtk/inst/bin/python3
> $ export 
> PYTHONPATH=/Users/vbraun/gtk/inst/lib/python3.3:/Users/vbraun/gtk/inst/lib/python3.3/site-packages/gtk-2.0:/Users/vbraun/gtk/inst/lib/python3.3/site-packages
> $ python3 ./waf configure --prefix /Users/vbraun/gtk/inst
>  ./options()
> Setting top to                           :
> /Users/vbraun/gtk/source/pycairo-1.10.0
> Setting out to                           :
> /Users/vbraun/gtk/source/pycairo-1.10.0/build_directory
>  ./configure()
> Checking for 'gcc' (c compiler)          : ok
> Checking for program python              : /Users/vbraun/gtk/inst/bin/python3
> Checking for python version              : (3, 3, 2, 'final', 0)
> Checking for library python3.3 in LIBPATH_PYEMBED : not found
> Checking for library python3.3 in LIBDIR          : not found
> Checking for library python3.3 in python_LIBPL    : not found
> Checking for library python3.3 in $prefix/libs    : not found
> Checking for library python3.3m in LIBPATH_PYEMBED : yes
> Checking for program python3.3-config              :
> /Users/vbraun/gtk/inst/bin/python3.3-config
> Checking for header Python.h                       : yes
> Checking for program pkg-config                    :
> /Users/vbraun/gtk/inst/bin/pkg-config
> Checking for 'cairo' >= 1.10.0                     : yes
> Configuration:
> PREFIX                                   : /Users/vbraun/gtk/inst
> LIBDIR                                   : /Users/vbraun/gtk/inst/lib
> 'configure' finished successfully (0.477s)

Yeah, I haven't managed to figure that out either. Jhbuild isn't the problem: It's using the Apple supplied 
python. GObject-Introspection is the problem, because it's also Py2-only, so one needs Py2 to make the Girs 
and Typelibs and then switch to Py3 for running every instance of setup.py so that modules go into 
lib/python-3.2 instead of lib/python-2.7. Not too hard to do by hand, but I'm not sure that it can be done 
with jhbuild.

Regards,
John Ralls