From bhood2 at comcast.net  Wed Sep  2 22:51:11 2015
From: bhood2 at comcast.net (Bob Hood)
Date: Wed, 2 Sep 2015 14:51:11 -0600
Subject: [PySide] PySide 2.0.0.dev0 build issue
Message-ID: <55E7613F.6030809@comcast.net>

Hi, all!  I am attempting to build (current) PySide v2.0.0.dev0 within the 
following environment:

        Python: 2.7.9 64-bit
Visual Studio: 2013 Update 4 64-bit (VC/bin/amd64/vcvars64.bat)
       OpenSSL: 1.0.1h 64-bit
            Qt: 5.4.2 64-bit (shared)

I have cloned pyside-setup2/, and within that folder I am running the 
following command:

     python setup.py build --qmake=Q:\Qt\5.4.2\64_dll\bin\qmake.exe 
--openssl=E:\openssl_64_dll\bin --jom --jobs=4

This build ultimately encounters the error:

     ...
     [100%] Built target shibokenmodule
     Generating Shiboken documentation shiboken...
     Running process: E:\jom_1_0_16\jom.exe doc
     Error: Target doc doesn't exist.
     error: Error generating documentation shiboken

On the off chance that the problem involves using jom, I removed that (so it 
uses nmake instead) and encountered:

     Linking CXX shared module ..\QtCore.pyd
        Creating library QtCore.lib and object QtCore.exp

     qtcore_module_wrapper.cpp.obj : error LNK2019: unresolved external symbol 
"__declspec(dllimport) public: int __cdecl QString::toWCharArray(unsigned 
short *)const " (__imp_?toWCharArray at QString@@QEBAHPEAG at Z) referenced in 
function "struct _object * __cdecl QStringRef_CppToPython_QStringRef(void 
const *)" (?QStringRef_CppToPython_QStringRef@@YAPEAU_object@@PEBX at Z)

     ..\QtCore.pyd : fatal error LNK1120: 1 unresolved externals

I understand this is development, and may well be broken at the moment, but I 
wanted to make sure I wasn't doing anything wrong on my end.

Thanks for any help.


From mr.smittye at gmail.com  Thu Sep  3 05:48:36 2015
From: mr.smittye at gmail.com (E Smitty)
Date: Wed, 2 Sep 2015 20:48:36 -0700
Subject: [PySide] PySide 2.0.0.dev0 build issue
In-Reply-To: <55E7613F.6030809@comcast.net>
References: <55E7613F.6030809@comcast.net>
Message-ID: <CAFXk2UcjngRZDkv6C52eZ2DXPq5DXmxZuyUX9mgisRg_f03e2w@mail.gmail.com>

Well, did you compile Python 2.7.9 yourself? Because it is incompatible
with extensions compiled with Visual Studio 2013.

Also, did you follow these
<https://github.com/PySide/pyside2/blob/qt5/README_WIN.rst> guidelines?

On Wed, Sep 2, 2015 at 1:51 PM, Bob Hood <bhood2 at comcast.net> wrote:

> Hi, all!  I am attempting to build (current) PySide v2.0.0.dev0 within the
> following environment:
>
>         Python: 2.7.9 64-bit
> Visual Studio: 2013 Update 4 64-bit (VC/bin/amd64/vcvars64.bat)
>        OpenSSL: 1.0.1h 64-bit
>             Qt: 5.4.2 64-bit (shared)
>
> I have cloned pyside-setup2/, and within that folder I am running the
> following command:
>
>      python setup.py build --qmake=Q:\Qt\5.4.2\64_dll\bin\qmake.exe
> --openssl=E:\openssl_64_dll\bin --jom --jobs=4
>
> This build ultimately encounters the error:
>
>      ...
>      [100%] Built target shibokenmodule
>      Generating Shiboken documentation shiboken...
>      Running process: E:\jom_1_0_16\jom.exe doc
>      Error: Target doc doesn't exist.
>      error: Error generating documentation shiboken
>
> On the off chance that the problem involves using jom, I removed that (so
> it
> uses nmake instead) and encountered:
>
>      Linking CXX shared module ..\QtCore.pyd
>         Creating library QtCore.lib and object QtCore.exp
>
>      qtcore_module_wrapper.cpp.obj : error LNK2019: unresolved external
> symbol
> "__declspec(dllimport) public: int __cdecl QString::toWCharArray(unsigned
> short *)const " (__imp_?toWCharArray at QString@@QEBAHPEAG at Z) referenced in
> function "struct _object * __cdecl QStringRef_CppToPython_QStringRef(void
> const *)" (?QStringRef_CppToPython_QStringRef@@YAPEAU_object@@PEBX at Z)
>
>      ..\QtCore.pyd : fatal error LNK1120: 1 unresolved externals
>
> I understand this is development, and may well be broken at the moment,
> but I
> wanted to make sure I wasn't doing anything wrong on my end.
>
> Thanks for any help.
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20150902/3f9f5523/attachment.html>

From bhood2 at comcast.net  Thu Sep  3 16:58:47 2015
From: bhood2 at comcast.net (Bob Hood)
Date: Thu, 3 Sep 2015 08:58:47 -0600
Subject: [PySide] PySide 2.0.0.dev0 build issue
In-Reply-To: <CAFXk2UcjngRZDkv6C52eZ2DXPq5DXmxZuyUX9mgisRg_f03e2w@mail.gmail.com>
References: <55E7613F.6030809@comcast.net>
	<CAFXk2UcjngRZDkv6C52eZ2DXPq5DXmxZuyUX9mgisRg_f03e2w@mail.gmail.com>
Message-ID: <55E86027.3050303@comcast.net>

On 9/2/2015 9:48 PM, E Smitty wrote:
> Well, did you compile Python 2.7.9 yourself? Because it is incompatible with 
> extensions compiled with Visual Studio 2013.

Ah!  Thank you, that may very well be the issue.  I'll use a VS2013-built 
version and see if that addresses it.

> Also, did you follow these 
> <https://github.com/PySide/pyside2/blob/qt5/README_WIN.rst>guidelines?

Actually, I followed this (as little as there was): 
https://wiki.qt.io/Building_PySide_on_Windows

Thanks.  :)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20150903/0f5a7708/attachment.html>

From bhood2 at comcast.net  Thu Sep  3 19:52:30 2015
From: bhood2 at comcast.net (Bob Hood)
Date: Thu, 3 Sep 2015 11:52:30 -0600
Subject: [PySide] PySide 2.0.0.dev0 build issue
In-Reply-To: <CAFXk2UcjngRZDkv6C52eZ2DXPq5DXmxZuyUX9mgisRg_f03e2w@mail.gmail.com>
References: <55E7613F.6030809@comcast.net>
	<CAFXk2UcjngRZDkv6C52eZ2DXPq5DXmxZuyUX9mgisRg_f03e2w@mail.gmail.com>
Message-ID: <55E888DE.8020009@comcast.net>

On 9/2/2015 9:48 PM, E Smitty wrote:
> Well, did you compile Python 2.7.9 yourself? Because it is incompatible with 
> extensions compiled with Visual Studio 2013.

Well, that was certainly something that might have caused a problem, but it 
wasn't causing these specific issues.  Using Python 2.7.10 built using VS2013, 
I still get the error about a "doc" target when using jom:

      ...
      [100%] Built target shibokenmodule
      Generating Shiboken documentation shiboken...
      Running process: E:\jom_1_0_16\jom.exe doc
      Error: Target doc doesn't exist.
      error: Error generating documentation shiboken

and the link error when I switch back to "nmake":

      Linking CXX shared module ..\QtCore.pyd
         Creating library QtCore.lib and object QtCore.exp

      qtcore_module_wrapper.cpp.obj : error LNK2019: unresolved external symbol
"__declspec(dllimport) public: int __cdecl QString::toWCharArray(unsigned
short *)const " (__imp_?toWCharArray at QString@@QEBAHPEAG at Z) referenced in
function "struct _object * __cdecl QStringRef_CppToPython_QStringRef(void
const *)" (?QStringRef_CppToPython_QStringRef@@YAPEAU_object@@PEBX at Z)

      ..\QtCore.pyd : fatal error LNK1120: 1 unresolved externals

Does anybody know what specific version of Qt PySide 2.0.0.dev0 is only 
developed against?  This particular method (QString::toWCharArray) has exactly 
the same signature in both Qt 5.4.2 and 5.5.0, so there wasn't a change 
between those two versions.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20150903/b3a98a43/attachment.html>

From tismer at stackless.com  Fri Sep  4 06:38:16 2015
From: tismer at stackless.com (Christian Tismer)
Date: Fri, 4 Sep 2015 06:38:16 +0200
Subject: [PySide] PySide 2.0.0.dev0 build issue
In-Reply-To: <55E888DE.8020009@comcast.net>
References: <55E7613F.6030809@comcast.net>
	<CAFXk2UcjngRZDkv6C52eZ2DXPq5DXmxZuyUX9mgisRg_f03e2w@mail.gmail.com>
	<55E888DE.8020009@comcast.net>
Message-ID: <55E92038.8060703@stackless.com>

Hi,

but you know that this is not ready for use, yet?
Don't use install, use

    python setup.py develop --ignore-git --qmake=...

The problems that you have are known, and right now I have the following
work-arounds:

1. Yom problem:

This only happens on Windows, and I don't know the reason, yet.
but this works (hackish):

Do a build without yom, but kill the job as soon as shiboken is built.
Then, create a file in the pyside-build dir named "shiboken-off", right
beneath
the subfolder "shiboken".

Then start the same build command with yom. This time, setup.py will skip
the faulty shiboken part.

2. Link problem:

This is a known problem that was also existent on Pyside 1.2.2/Qt4.8.
For some reason, the Pyside devs decided in 2010 to add the option
"/Zc:wchar_t-". On windows, that means that you have to build your own Qt5,
which takes many hours.

For the moment, you can switch to the branch "qt5-win-fix" and build
again.

In any case, there are still some serious problems that are a showstopper
for any use, because internal protocols are not completely adjusted.
For instance, the implementation of dynamicmetaobject.cpp ist completely
broken,
and this crashes any instantiation of a widget.

I am currently in the debugging phase and can use a lot of help.

Cheers - Chris


On 03.09.15 19:52, Bob Hood wrote:
> On 9/2/2015 9:48 PM, E Smitty wrote:
>> Well, did you compile Python 2.7.9 yourself? Because it is
>> incompatible with extensions compiled with Visual Studio 2013.
>
> Well, that was certainly something that might have caused a problem,
> but it wasn't causing these specific issues.  Using Python 2.7.10
> built using VS2013, I still get the error about a "doc" target when
> using jom:
>
>      ...
>      [100%] Built target shibokenmodule
>      Generating Shiboken documentation shiboken...
>      Running process: E:\jom_1_0_16\jom.exe doc
>      Error: Target doc doesn't exist.
>      error: Error generating documentation shiboken
>
> and the link error when I switch back to "nmake":
>
>      Linking CXX shared module ..\QtCore.pyd
>         Creating library QtCore.lib and object QtCore.exp
>
>      qtcore_module_wrapper.cpp.obj : error LNK2019: unresolved
> external symbol
> "__declspec(dllimport) public: int __cdecl QString::toWCharArray(unsigned
> short *)const " (__imp_?toWCharArray at QString@@QEBAHPEAG at Z) referenced in
> function "struct _object * __cdecl QStringRef_CppToPython_QStringRef(void
> const *)" (?QStringRef_CppToPython_QStringRef@@YAPEAU_object@@PEBX at Z)
>
>      ..\QtCore.pyd : fatal error LNK1120: 1 unresolved externals
>
> Does anybody know what specific version of Qt PySide 2.0.0.dev0 is
> only developed against?  This particular method
> (QString::toWCharArray) has exactly the same signature in both Qt
> 5.4.2 and 5.5.0, so there wasn't a change between those two versions.
>
>
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside


-- 
Christian Tismer             :^)   tismer at stackless.com
Software Consulting          :     http://www.stackless.com/
Karl-Liebknecht-Str. 121     :     https://github.com/PySide
14482 Potsdam                :     GPG key -> 0xFB7BEE0E
phone +49 173 24 18 776  fax +49 (30) 700143-0023

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20150904/4214cca4/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 522 bytes
Desc: OpenPGP digital signature
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20150904/4214cca4/attachment.sig>

From tismer at stackless.com  Fri Sep  4 07:20:27 2015
From: tismer at stackless.com (Christian Tismer)
Date: Fri, 4 Sep 2015 07:20:27 +0200
Subject: [PySide] PySide 2.0.0.dev0 build issue
In-Reply-To: <55E92038.8060703@stackless.com>
References: <55E7613F.6030809@comcast.net>
	<CAFXk2UcjngRZDkv6C52eZ2DXPq5DXmxZuyUX9mgisRg_f03e2w@mail.gmail.com>
	<55E888DE.8020009@comcast.net> <55E92038.8060703@stackless.com>
Message-ID: <901E34AC-B294-4C85-ADD5-8D3C68CEEE76@stackless.com>

Please replace "beneath" by "besides". Where you find the shiboken folder, create some file "shiboken-skip".

Sent from my iPad

> On 04 Sep 2015, at 06:38, Christian Tismer <tismer at stackless.com> wrote:
> 
> Hi,
> 
> but you know that this is not ready for use, yet?
> Don't use install, use
> 
>     python setup.py develop --ignore-git --qmake=...
> 
> The problems that you have are known, and right now I have the following
> work-arounds:
> 
> 1. Yom problem:
> 
> This only happens on Windows, and I don't know the reason, yet.
> but this works (hackish):
> 
> Do a build without yom, but kill the job as soon as shiboken is built.
> Then, create a file in the pyside-build dir named "shiboken-off", right beneath
> the subfolder "shiboken".
> 
> Then start the same build command with yom. This time, setup.py will skip
> the faulty shiboken part.
> 
> 2. Link problem:
> 
> This is a known problem that was also existent on Pyside 1.2.2/Qt4.8.
> For some reason, the Pyside devs decided in 2010 to add the option
> "/Zc:wchar_t-". On windows, that means that you have to build your own Qt5,
> which takes many hours.
> 
> For the moment, you can switch to the branch "qt5-win-fix" and build
> again.
> 
> In any case, there are still some serious problems that are a showstopper
> for any use, because internal protocols are not completely adjusted.
> For instance, the implementation of dynamicmetaobject.cpp ist completely broken,
> and this crashes any instantiation of a widget.
> 
> I am currently in the debugging phase and can use a lot of help.
> 
> Cheers - Chris
> 
> 
>> On 03.09.15 19:52, Bob Hood wrote:
>>> On 9/2/2015 9:48 PM, E Smitty wrote:
>>> Well, did you compile Python 2.7.9 yourself? Because it is incompatible with extensions compiled with Visual Studio 2013.
>> 
>> Well, that was certainly something that might have caused a problem, but it wasn't causing these specific issues.  Using Python 2.7.10 built using VS2013, I still get the error about a "doc" target when using jom:
>> 
>>      ...
>>      [100%] Built target shibokenmodule
>>      Generating Shiboken documentation shiboken...
>>      Running process: E:\jom_1_0_16\jom.exe doc
>>      Error: Target doc doesn't exist.
>>      error: Error generating documentation shiboken
>> 
>> and the link error when I switch back to "nmake":
>> 
>>      Linking CXX shared module ..\QtCore.pyd
>>         Creating library QtCore.lib and object QtCore.exp
>> 
>>      qtcore_module_wrapper.cpp.obj : error LNK2019: unresolved external symbol
>> "__declspec(dllimport) public: int __cdecl QString::toWCharArray(unsigned
>> short *)const " (__imp_?toWCharArray at QString@@QEBAHPEAG at Z) referenced in
>> function "struct _object * __cdecl QStringRef_CppToPython_QStringRef(void
>> const *)" (?QStringRef_CppToPython_QStringRef@@YAPEAU_object@@PEBX at Z)
>> 
>>      ..\QtCore.pyd : fatal error LNK1120: 1 unresolved externals
>> 
>> Does anybody know what specific version of Qt PySide 2.0.0.dev0 is only developed against?  This particular method (QString::toWCharArray) has exactly the same signature in both Qt 5.4.2 and 5.5.0, so there wasn't a change between those two versions.
>> 
>> 
>> 
>> _______________________________________________
>> PySide mailing list
>> PySide at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/pyside
> 
> 
> -- 
> Christian Tismer             :^)   tismer at stackless.com
> Software Consulting          :     http://www.stackless.com/
> Karl-Liebknecht-Str. 121     :     https://github.com/PySide
> 14482 Potsdam                :     GPG key -> 0xFB7BEE0E
> phone +49 173 24 18 776  fax +49 (30) 700143-0023
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20150904/c65a67c4/attachment.html>

From bhood2 at comcast.net  Fri Sep  4 18:30:00 2015
From: bhood2 at comcast.net (Bob Hood)
Date: Fri, 4 Sep 2015 10:30:00 -0600
Subject: [PySide] PySide 2.0.0.dev0 build issue
In-Reply-To: <55E92038.8060703@stackless.com>
References: <55E7613F.6030809@comcast.net>
	<CAFXk2UcjngRZDkv6C52eZ2DXPq5DXmxZuyUX9mgisRg_f03e2w@mail.gmail.com>
	<55E888DE.8020009@comcast.net> <55E92038.8060703@stackless.com>
Message-ID: <55E9C708.5020105@comcast.net>

On 9/3/2015 10:38 PM, Christian Tismer wrote:
> Hi,
>
> but you know that this is not ready for use, yet?

Yes, I believe that is the conclusion I've come to.  ;)

> Don't use install, use
>
>     python setup.py develop --ignore-git --qmake=...

I tried that instead (used "develop" instead of "build") and still encountered 
the same link errors.  I can't use "--git-ignore" because the sub-projects 
will not be populated and there's nothing to build.

The command lines I've attempted in the pyside-setup2/ folder are:

  * python setup.py build --qmake=Q:\Qt\5.4.2\64_dll\bin\qmake.exe
    --openssl=E:\openssl_64_dll\bin --jom --jobs=4
  * python setup.py build --qmake=Q:\Qt\5.4.2\64_dll\bin\qmake.exe
    --openssl=E:\openssl_64_dll\bin
  * python setup.py build
    --qmake=C:\Qt\Qt5.4.2\5.4\msvc2013_64_opengl\bin\qmake.exe
    --openssl=E:\openssl_64_dll\bin
  * python setup.py build --qmake=C:\Qt\Qt5.5.0\5.5\msvc2013_64\bin\qmake.exe
    --openssl=E:\openssl_64_dll\bin
  * python setup.py develop --qmake=Q:\Qt\5.4.2\64_dll\bin\qmake.exe
    --openssl=E:\openssl_64_dll\bin


The Qt in the Q:\Qt\5.4.2\ folder referenced above is our own build of that 
version.  Those in the C:\Qt\ folder are the pre-built binaries provided for 
download.  In all cases, I get a link error of some kind (the 5.4.2 version 
has one link error, the 5.5.0 version generates a different link error).

> The problems that you have are known, and right now I have the following
> work-arounds:
>
> 1. Yom problem:

Do you actually mean "jom" here?

> 2. Link problem:
>
> This is a known problem that was also existent on Pyside 1.2.2/Qt4.8.
> For some reason, the Pyside devs decided in 2010 to add the option
> "/Zc:wchar_t-". On windows, that means that you have to build your own Qt5,
> which takes many hours.

I am in charge of doing this for my team, so it's not an issue for me.  I've 
got an environment set up for building Qt that's largely automated.  In fact, 
as I stated earlier, one of the Qt versions against which I am attempting to 
build was actually built by me.  Are you saying that removing that compiler 
switch (if I can figure out how) addresses the link error?

> For the moment, you can switch to the branch "qt5-win-fix" and build
> again.

Ah, ok.  I've already reported my failures and opinions of the state of PySide 
v2 to the team, but I will try this branch and see if I can get any further.

Thank you very much for the response, Chris.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20150904/c332e90f/attachment.html>

From goswin-v-b at web.de  Tue Sep  8 10:59:01 2015
From: goswin-v-b at web.de (Goswin von Brederlow)
Date: Tue, 8 Sep 2015 10:59:01 +0200
Subject: [PySide] Segfault when clicking next in QWizard
In-Reply-To: <20150812113210.GA25429@frosties>
References: <20150812113210.GA25429@frosties>
Message-ID: <20150908085900.GD2970@frosties>

On Wed, Aug 12, 2015 at 01:32:10PM +0200, Goswin von Brederlow wrote:
> Hi,
> 
> I have a problem with a QWizard in pyside that I can't track down. Every
> so often I get a segfault when clicking next or finished ion the wizard:
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x0000000000000090 in ?? ()
> (gdb) bt
> #0  0x0000000000000090 in ?? ()
> #1  0x00007ffff41dfec3 in ?? ()
>    from /usr/lib/python3/dist-packages/PySide/QtGui.cpython-34m-x86_64-linux-gnu.so
> #2  0x00007ffff347483b in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
> #3  0x00007ffff56d087a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) ()
>    from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
> #4  0x00007ffff35dd172 in QAbstractButton::clicked(bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
> #5  0x00007ffff3340a63 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
> #6  0x00007ffff3341bd3 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
> #7  0x00007ffff3341cbc in QAbstractButton::mouseReleaseEvent(QMouseEvent*) ()
>    from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
> #8  0x00007ffff2fde51a in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
> #9  0x00007ffff2f8ee2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
>    from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
> #10 0x00007ffff2f955dd in QApplication::notify(QObject*, QEvent*) ()
>    from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
> #11 0x00007ffff3c6076e in ?? ()
>    from /usr/lib/python3/dist-packages/PySide/QtGui.cpython-34m-x86_64-linux-gnu.so
> #12 0x00007ffff56bc4dd in QCoreApplication::notifyInternal(QObject*, QEvent*) ()
>    from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
> #13 0x00007ffff2f94d93 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
> #14 0x00007ffff30099eb in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
> 
> I've somewhat reduce the problem to a test case with just the wizard
> and uploaded it to github:
> 
>     https://github.com/Q-Leap-Networks/pyside-segfault
> 
> The segfaults seem to be random. Sometimes they happen, sometimes
> everything works. Sometimes the first run through works but when I run
> the wizard a second or third time it suddenly segfaults. Sometimes
> it's on one of the next buttons and sometimes on finish.
> 
> Any help or suggestions how to track this segfault down would be
> appreciated.
> 
> MfG
> 	Goswin

To answere myself:

The problem was that the created pages were not stored in the python
class. Therefore the python side of the pages gets freed by the GC and
the callbacks go nowhere.

MfG
	Goswin


From uknowpm at gmail.com  Thu Sep  3 08:27:11 2015
From: uknowpm at gmail.com (min pang)
Date: Thu, 3 Sep 2015 14:27:11 +0800
Subject: [PySide] Problem with install PySide (repository
 'https://git.gitorious.org/pyside/pyside.git/' not found)
Message-ID: <CAM-4jdQQGAfV9Z8wXnb7q9DX40TkDGCBYZdAO8fd=hNj3KM=fg@mail.gmail.com>

Hi,

I would like to install PySide but I encountered the error in the step
"python setup.py bdist_wheel --version=1.2.2".

The error message says
"Clone of 'https://git.gitorious.org/pyside/pyside.git' into submodule path
'sources/pyside' failed
Traceback (most recent call last):
    File "setup.py", line 207, in <module>
    raise DistutilsSetupError("Failed to initialize the git submodules")
distutils.errors.DistutilsSetupError: Failed to initialize the git
submodules

I think it's the problem of the website as it says "repository '
https://git.gitorious.org/pyside/pyside.git/' not found". So do I need to
keep waiting until the website is fixed or is there any other measure I can
take to circumvent this issue?

Thank you,
Min
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20150903/be0aade2/attachment.html>

From jumaroch.belpecajo at gmail.com  Wed Sep 23 17:36:36 2015
From: jumaroch.belpecajo at gmail.com (Jumaroch Belpecajo)
Date: Wed, 23 Sep 2015 17:36:36 +0200
Subject: [PySide] Ann: porting PySide to Qt5
In-Reply-To: <55A23E27.5020009@stackless.com>
References: <559EDD5F.5070403@stackless.com>
	<2baad33a.1d5.14e813e4997.Coremail.redstone-cold@163.com>
	<55A23E27.5020009@stackless.com>
Message-ID: <CACes4vmkyOPviRbr6ZixLmStfVdvU_-ad1-UOn0tZ3YCB1+hgg@mail.gmail.com>

Hi Christian,



Last year, I started a porting of PySide to Qt5.

I only worked on the QtCore module, but I succedded in having 99% of all
classes and methods sucessfully wrapped.

I made a quick python test with a custom class derived from QObject with
signal/slot connections, and everything was working well.

I didn't have time to continue with the QtGui porting since it's a huge
task due the QtWidgets modules split.



If you are interested, I can generate the patches and send them to you,
especially the ones related to "tricky" qt metaobject stuff :)

FYI, I used an old version of PySide (1.0.9), but hopefully there is not
much difference with the current version (even if in this version,
api-extractor was not yet merged with the shiboken module).



IIRC, the main difficulties were:

- replace Zc:wchar_t- with Zc:wchar_t to use the native type instead of
ushort typedef (Qt5 is now compiled with wchar_t by default)

- need explicit cast in qstring_convertsions:
QString::fromUtf16(reinterpret_cast<const ushort*>(unicode)

- headergenerator: need to order customized converter, due to dependencies:
QString before QVariant before QStringRef, ...

- replace deprecated macro qdoc with Q_QDOC (otherwise, the metaObject
method is not seen)



Cheers,

Romain

2015-07-12 12:15 GMT+02:00 Christian Tismer <tismer at stackless.com>:

> Thank you for the hint!
>
> Exactly this is what I saved for later, because I needed to gain more
> experience by the porting, before going into this.
>
> cheers - Chris
>
>
> On 12.07.15 09:50, redstone-cold wrote:
>
> I hope you guys be careful about the signal - slot  mechanism in Qt5
>
> http://www.riverbankcomputing.com/pipermail/pyqt/2014-January/033575.html
>
>
>
> 在2015年07月10 04时45分, "Christian Tismer"<tismer at stackless.com>
> <tismer at stackless.com>写道:
>
>
> Hi all,
>
> to let you be informed:
>
> PySide will live on.
> --------------------
>
> There is someone intensively working on porting PySide to Qt5,
> with some help from Autodesk.
>
> I started end of May and am still very busy to get the most
> important modules to compile. Now I think it is time to open
> things up to the community and discuss some things, do reviews,
> and most importantly: stop working alone for too long.
>
> This stuff is still under heavy development, and I'm inviting
> experienced PySide developers to join me on the pyside-dev
> list. I will post more details there.
>
> All the best - Chris
>
> --
> Christian Tismer             :^)   tismer at stackless.com
> Software Consulting          :     http://www.stackless.com/
> Karl-Liebknecht-Str. 121     :     http://www.pydica.net/
> 14482 Potsdam                :     GPG key -> 0xFB7BEE0E
> phone +49 173 24 18 776  fax +49 (30) 700143-0023
>
>
>
>
>
> --
> Christian Tismer             :^)   tismer at stackless.com
> Software Consulting          :     http://www.stackless.com/
> Karl-Liebknecht-Str. 121     :     http://www.pydica.net/
> 14482 Potsdam                :     GPG key -> 0xFB7BEE0E
> phone +49 173 24 18 776  fax +49 (30) 700143-0023
>
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20150923/b77842c4/attachment.html>

From tismer at stackless.com  Wed Sep 23 18:09:36 2015
From: tismer at stackless.com (Christian Tismer)
Date: Wed, 23 Sep 2015 18:09:36 +0200
Subject: [PySide] Ann: porting PySide to Qt5
In-Reply-To: <CACes4vmkyOPviRbr6ZixLmStfVdvU_-ad1-UOn0tZ3YCB1+hgg@mail.gmail.com>
References: <559EDD5F.5070403@stackless.com>	<2baad33a.1d5.14e813e4997.Coremail.redstone-cold@163.com>	<55A23E27.5020009@stackless.com>
	<CACes4vmkyOPviRbr6ZixLmStfVdvU_-ad1-UOn0tZ3YCB1+hgg@mail.gmail.com>
Message-ID: <5602CEC0.2080100@stackless.com>

Hi Jumaroch,

this is interesting, maybe you have solved things that I have not yet.

PySide2 builds completely, and a few things work on Qt5.4.
Qt5.5 right now has a problem with QSysInfo.

I am interested in your support for signals, because I did not do
that, yet. But before, there is the bigger problem of
the implementation of dynamicmetaobject.
That needs a re-write, and I did not understand exactly how.

The revision that PySide uses is still #3, which is no longer supported
by Qt5, they now require #7.

Was that the case when you worked on QtCore?

I would be very much interested in your patches, if it solves more than
in your list below, which I all have already.

Here is my status log of the project.

> Status:
> 
> +  Full build of PySide 2.0 for Qt5.4
> +  Migration to Qt5.5 done
> +  Windows 7/10 support is done
> +- regression tests 50 % working
> -  rewrite libpyside.dynamicmetaobject.cpp for revision 7 (current is 3)
> -  signal support is missing
> -  plugin support is missing
> 
> This primitive example crashes, because of the above libpyside flaw.:
> from PySide import QtWidgets
> app = QtWidgets.QApplication(())
> w = QtWidgets.QLabel('hello')
> w.show() # crashes because of too old metaobject revision
> 
> 
> The 50% regression does not say much, because most errors depend on the missing features or old revisions. Once there things are resolved, we really can look into the remaining errors.


Thanks very much -- Chris


On 23/09/15 17:36, Jumaroch Belpecajo wrote:
> Hi Christian,
> 
>  
> 
> Last year, I started a porting of PySide to Qt5.
> 
> I only worked on the QtCore module, but I succedded in having 99% of all
> classes and methods sucessfully wrapped.
> 
> I made a quick python test with a custom class derived from QObject with
> signal/slot connections, and everything was working well.
> 
> I didn't have time to continue with the QtGui porting since it's a huge
> task due the QtWidgets modules split.
> 
>  
> 
> If you are interested, I can generate the patches and send them to you,
> especially the ones related to "tricky" qt metaobject stuff :)
> 
> FYI, I used an old version of PySide (1.0.9), but hopefully there is not
> much difference with the current version (even if in this version,
> api-extractor was not yet merged with the shiboken module).
> 
>  
> 
> IIRC, the main difficulties were:
> 
> - replace Zc:wchar_t- with Zc:wchar_t to use the native type instead of
> ushort typedef (Qt5 is now compiled with wchar_t by default)
> 
> - need explicit cast in qstring_convertsions:
> QString::fromUtf16(reinterpret_cast<const ushort*>(unicode)
> 
> - headergenerator: need to order customized converter, due to
> dependencies: QString before QVariant before QStringRef, ...
> 
> - replace deprecated macro qdoc with Q_QDOC (otherwise, the metaObject
> method is not seen)
> 
>  
> 
> Cheers,
> 
> Romain
> 
> 
> 2015-07-12 12:15 GMT+02:00 Christian Tismer <tismer at stackless.com
> <mailto:tismer at stackless.com>>:
> 
>     Thank you for the hint!
> 
>     Exactly this is what I saved for later, because I needed to gain more
>     experience by the porting, before going into this.
> 
>     cheers - Chris
> 
> 
>     On 12.07.15 09:50, redstone-cold wrote:
>>     I hope you guys be careful about the signal - slot  mechanism in Qt5
>>
>>     http://www.riverbankcomputing.com/pipermail/pyqt/2014-January/033575.html
>>
>>
>>
>>     在2015年07月10 04时45分, "Christian Tismer"<tismer at stackless.com>
>>     <mailto:tismer at stackless.com>写道:
>>
>>
>>         Hi all,
>>
>>         to let you be informed:
>>
>>         PySide will live on.
>>         --------------------
>>
>>         There is someone intensively working on porting PySide to Qt5,
>>         with some help from Autodesk.
>>
>>         I started end of May and am still very busy to get the most
>>         important modules to compile. Now I think it is time to open
>>         things up to the community and discuss some things, do reviews,
>>         and most importantly: stop working alone for too long.
>>
>>         This stuff is still under heavy development, and I'm inviting
>>         experienced PySide developers to join me on the pyside-dev
>>         list. I will post more details there.
>>
>>         All the best - Chris
>>
>>         -- 
>>         Christian Tismer             :^)   tismer at stackless.com
>>         <mailto:tismer at stackless.com>
>>         Software Consulting          :     http://www.stackless.com/
>>         Karl-Liebknecht-Str. 121     :     http://www.pydica.net/
>>         14482 Potsdam                :     GPG key -> 0xFB7BEE0E
>>         phone +49 173 24 18 776 <tel:%2B49%20173%2024%2018%20776>  fax
>>         +49 (30) 700143-0023 <tel:%2B49%20%2830%29%20700143-0023>
>>
>>
>>
> 
> 
>     -- 
>     Christian Tismer             :^)   tismer at stackless.com <mailto:tismer at stackless.com>
>     Software Consulting          :     http://www.stackless.com/
>     Karl-Liebknecht-Str. 121     :     http://www.pydica.net/
>     14482 Potsdam                :     GPG key -> 0xFB7BEE0E
>     phone +49 173 24 18 776 <tel:%2B49%20173%2024%2018%20776>  fax +49 (30) 700143-0023 <tel:%2B49%20%2830%29%20700143-0023>
> 
> 
>     _______________________________________________
>     PySide mailing list
>     PySide at qt-project.org <mailto:PySide at qt-project.org>
>     http://lists.qt-project.org/mailman/listinfo/pyside
> 
> 


-- 
Christian Tismer             :^)   tismer at stackless.com
Software Consulting          :     http://www.stackless.com/
Karl-Liebknecht-Str. 121     :     https://github.com/PySide
14482 Potsdam                :     GPG key -> 0xFB7BEE0E
phone +49 173 24 18 776  fax +49 (30) 700143-0023

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 522 bytes
Desc: OpenPGP digital signature
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20150923/9e5079f7/attachment.sig>