[PySide] BuildScripts for Python 3 (Was: from PySide import * in Python2/3)

Thomas Perl th.perl at gmail.com
Wed Feb 29 09:04:37 CET 2012


2012/2/29 anatoly techtonik <techtonik at gmail.com>:
> On Tue, Feb 21, 2012 at 7:49 PM, Thomas Perl <th.perl at gmail.com> wrote:
>> This includes support for building PySide for Python 3. You have to
>> edit the environment.sh file and uncomment one line. PySide for Python
>> 3 will be installed in a different directory, so that you can easily
>> switch between it and PySide for Python 2 - simply edit the
>> environment.sh and then "source" it in your shell.
> Is it possible to provide Python 2 and Python 3 bindings
> simultaneously? 2 and 3 peacefully coexist in Linux, so why isn't it
> possible to use both? Editing environment.sh every time is bothersome.

Right now, I think the approach used is okay - most users might still
want to use Python 2 for various reasons. We can think about changing
this later on. It will also require more testing, the current approach
is more fail-safe (no conflicting environment variables).

>> Please also note that pyside-tools and mobility are not yet able to
>> utilize/find Python 3 from the CMake scripts, I've filed two bugs:
>> http://bugs.pyside.org/show_bug.cgi?id=1148
>> http://bugs.pyside.org/show_bug.cgi?id=1149
> Unfortunately, PySide doesn't compile anymore even with Python 2.
> CMake Error at cmake/Modules/FindQtMobility.cmake:52 (message):
>  Couldn't find any version of QtMobility.
> That's a bad default to require QtMobility installed. Ideally, build
> scripts should detect its presence, but for a quick fix I'd move all
> QtMobility stuff into separate README chapter and instead of requiring
> everybody to type "./build_and_install apiextractor generatorrunner
> shiboken pyside", provided an instructions just for those who needs
> QtMobility to type "./build_and_install qtmobility"

Indeed, that's probably a better default. Changed now.


More information about the PySide mailing list