From mdhillca at gmail.com  Thu Oct  4 17:44:42 2018
From: mdhillca at gmail.com (Michael Hill)
Date: Thu, 4 Oct 2018 11:44:42 -0400
Subject: [PySide] Building Pyside2 in a flatpak
Message-ID: <CAGvW9WehFa14SOZiycmAD5SE0_5UvDwmD=R8L3RBW0kY3sbPMw@mail.gmail.com>

For building a FreeCAD flatpak using Qt 5, Pyside2 seems to lose track of
some header files:

https://bugreports.qt.io/browse/PYSIDE-787

Alexandru has already commented on the bug.

Inside the build environment, the include directories map to /app/include
and /usr/include. As I understand it, that's "dependencies just built" for
the first, and "things provided by org.kde.Sdk" for the second. If I grep
for the missing declarations, they all appear to be present under
/usr/include.

In the (now successful) Qt 4 version of the flatpak, FreeCAD initially had
a similar error. Bastien fixed it with this patch:

https://github.com/flathub/flathub/pull/618/commits/4e459030db373342498993cfe1bc9ca0873a067e

If that's what's happening, can someone suggest where to try to patch
Pyside2 so that it doesn't lose track of /usr/include?

Thanks,

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

From alexandru.croitor at qt.io  Thu Oct  4 17:55:21 2018
From: alexandru.croitor at qt.io (Alexandru Croitor)
Date: Thu, 4 Oct 2018 15:55:21 +0000
Subject: [PySide] Building Pyside2 in a flatpak
In-Reply-To: <CAGvW9WehFa14SOZiycmAD5SE0_5UvDwmD=R8L3RBW0kY3sbPMw@mail.gmail.com>
References: <CAGvW9WehFa14SOZiycmAD5SE0_5UvDwmD=R8L3RBW0kY3sbPMw@mail.gmail.com>
Message-ID: <7BA3E0BF-6EA7-4644-B3EB-9B988FC2E6FF@qt.io>

Hi,

Why do you assume that "/usr/include" gets lost somehow?

In the log snippets you provided on the issue, "-I/usr/include" can clearly be found.

I assume you meant to say that "-I/app/lib" should actually be passed as well?

The include flags that are passed to libclang are queried via something like "g++ -E -x c++ - -v </dev/null".
The code is in sources/shiboken2/ApiExtractor/clangparser/compilersupport.cpp

Perhaps consider attaching a fresh full new build log to the issue.

On 4. Oct 2018, at 17:44, Michael Hill <mdhillca at gmail.com<mailto:mdhillca at gmail.com>> wrote:

For building a FreeCAD flatpak using Qt 5, Pyside2 seems to lose track of some header files:

https://bugreports.qt.io/browse/PYSIDE-787

Alexandru has already commented on the bug.

Inside the build environment, the include directories map to /app/include and /usr/include. As I understand it, that's "dependencies just built" for the first, and "things provided by org.kde.Sdk" for the second. If I grep for the missing declarations, they all appear to be present under /usr/include.

In the (now successful) Qt 4 version of the flatpak, FreeCAD initially had a similar error. Bastien fixed it with this patch:

https://github.com/flathub/flathub/pull/618/commits/4e459030db373342498993cfe1bc9ca0873a067e

If that's what's happening, can someone suggest where to try to patch Pyside2 so that it doesn't lose track of /usr/include?

Thanks,

Mike
_______________________________________________
PySide mailing list
PySide at qt-project.org<mailto: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/20181004/8b72f5e9/attachment.html>

From mdhillca at gmail.com  Thu Oct  4 18:36:19 2018
From: mdhillca at gmail.com (Michael Hill)
Date: Thu, 4 Oct 2018 12:36:19 -0400
Subject: [PySide] Building Pyside2 in a flatpak
In-Reply-To: <7BA3E0BF-6EA7-4644-B3EB-9B988FC2E6FF@qt.io>
References: <CAGvW9WehFa14SOZiycmAD5SE0_5UvDwmD=R8L3RBW0kY3sbPMw@mail.gmail.com>
	<7BA3E0BF-6EA7-4644-B3EB-9B988FC2E6FF@qt.io>
Message-ID: <CAGvW9WdVt6YOfpHRthRXN4Uf4Dci5opu9LW1kt+L_Bk-7B0e0g@mail.gmail.com>

On Thu, Oct 4, 2018 at 11:55 AM Alexandru Croitor
<alexandru.croitor at qt.io> wrote:

> Why do you assume that "/usr/include" gets lost somehow?

Just a misinterpretation of your comment on the bug. I don't know
where to start looking.

> Perhaps consider attaching a fresh full new build log to the issue.

I'll do that.

Mike


From mdhillca at gmail.com  Sun Oct  7 21:01:12 2018
From: mdhillca at gmail.com (Michael Hill)
Date: Sun, 7 Oct 2018 15:01:12 -0400
Subject: [PySide] Building Pyside2 in a flatpak
In-Reply-To: <CAGvW9WdVt6YOfpHRthRXN4Uf4Dci5opu9LW1kt+L_Bk-7B0e0g@mail.gmail.com>
References: <CAGvW9WehFa14SOZiycmAD5SE0_5UvDwmD=R8L3RBW0kY3sbPMw@mail.gmail.com>
	<7BA3E0BF-6EA7-4644-B3EB-9B988FC2E6FF@qt.io>
	<CAGvW9WdVt6YOfpHRthRXN4Uf4Dci5opu9LW1kt+L_Bk-7B0e0g@mail.gmail.com>
Message-ID: <CAGvW9WeFR8C6GM0653pGBr7H5KGZD-sp-Hgc6Jprx7ppB_M00A@mail.gmail.com>

On Thu, Oct 4, 2018 at 12:36 PM Michael Hill <mdhillca at gmail.com> wrote:
>
> On Thu, Oct 4, 2018 at 11:55 AM Alexandru Croitor
> <alexandru.croitor at qt.io> wrote:
>
> > Why do you assume that "/usr/include" gets lost somehow?
>
> Just a misinterpretation of your comment on the bug. I don't know
> where to start looking.

Would building Qt 5 inside the flatpak fix this?

Mike


From perso.olivier.barthelemy at gmail.com  Fri Oct 12 15:37:20 2018
From: perso.olivier.barthelemy at gmail.com (Olivier B.)
Date: Fri, 12 Oct 2018 15:37:20 +0200
Subject: [PySide] The structure of type objects has changed!
Message-ID: <CA+cSArjRtoYZqfQ-x=Q2NAp3qLjDPW5P148t7cP43RN0adn+sA@mail.gmail.com>

I am getting this fatal error when importing PySide2 from a debug
python on windows

Environment :
I build my own python 3.5.2, Qt 5.11.1, and PySide2 5.11.1 (of july
27th), in a release and a debug build,
with the same compiler, VS2015 on windows  and GCC 4.8 on Linux

On Linux, i can import PySide2 with my release and my debug python
On windows, i can do it with the release python, but get the following
error for the debug python

The console says
Fatal Python error: The structure of type objects has changed!
Current thread 0x0000367c (most recent call first):
  File "<frozen importlib._bootstrap>", line 222 in _call_with_frames_removed
  File "<frozen importlib._bootstrap_external>", line 906 in create_module
  File "<frozen importlib._bootstrap>", line 577 in module_from_spec
  File "<frozen importlib._bootstrap>", line 666 in _load_unlocked
  File "<frozen importlib._bootstrap>", line 958 in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 969 in _find_and_load
  File "<frozen importlib._bootstrap>", line 222 in _call_with_frames_removed
  File "<frozen importlib._bootstrap_external>", line 906 in create_module
  File "<frozen importlib._bootstrap>", line 577 in module_from_spec
  File "<frozen importlib._bootstrap>", line 666 in _load_unlocked
  File "<frozen importlib._bootstrap>", line 958 in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 969 in _find_and_load
  File "<frozen importlib._bootstrap>", line 222 in _call_with_frames_removed
  File "<frozen importlib._bootstrap>", line 1016 in _handle_fromlist
  File "C:\...\python-3.5.2\lib\site-packages\PySide2\__init__.py",
line 39 in _setupQtDirectories
  File "C:\...\python-3.5.2\lib\site-packages\PySide2\__init__.py",
line 47 in <module>
  File "<frozen importlib._bootstrap>", line 222 in _call_with_frames_removed
  File "<frozen importlib._bootstrap_external>", line 665 in exec_module
  File "<frozen importlib._bootstrap>", line 673 in _load_unlocked
  File "<frozen importlib._bootstrap>", line 958 in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 969 in _find_and_load
  File "<stdin>", line 1 in <module>

The call stack when it happens, triggered by the import of QNetwork
from __init.py__:39
  python35_d.dll!Py_FatalError(const char * msg) Line 1399 C
  shiboken2_d.cp35-win_amd64.dll!check_PepTypeObject_valid() Line 441 C++
  shiboken2_d.cp35-win_amd64.dll!Pep384_Init() Line 837 C++
  shiboken2_d.cp35-win_amd64.dll!Shiboken::init() Line 554 C++
  shiboken2_d.cp35-win_amd64.dll!Shiboken::Module::create(const char *
moduleName, void * moduleData) Line 81 C++
  QtCore_d.cp35-win_amd64.pyd!PyInit_QtCore() Line 4110 C++
  python35_d.dll!_PyImport_LoadDynamicModuleWithSpec(_object * spec,
_iobuf * fp) Line 150 C
  python35_d.dll!_imp_create_dynamic_impl(PyModuleDef * module,
_object * spec, _object * file) Line 2027 C
  python35_d.dll!_imp_create_dynamic(PyModuleDef * module, _object *
args) Line 282 C
  python35_d.dll!PyCFunction_Call(_object * func, _object * args,
_object * kwds) Line 109 C
  python35_d.dll!ext_do_call(_object * func, _object * * * pp_stack,
int flags, int na, int nk) Line 5032 C
  python35_d.dll!PyEval_EvalFrameEx(_frame * f, int throwflag) Line 3278 C
  python35_d.dll!_PyEval_EvalCodeWithName(_object * _co, _object *
globals, _object * locals, _object * * args, int argcount, _object * *
kws, int kwcount, _object * * defs, int defcount, _object * kwdefs,
_object * closure, _object * name, _object * qualname) Line 4018 C
  python35_d.dll!fast_function(_object * func, _object * * * pp_stack,
int n, int na, int nk) Line 4818 C
  python35_d.dll!call_function(_object * * * pp_stack, int oparg) Line 4730 C
  python35_d.dll!PyEval_EvalFrameEx(_frame * f, int throwflag) Line 3238 C
  python35_d.dll!fast_function(_object * func, _object * * * pp_stack,
int n, int na, int nk) Line 4804 C
  python35_d.dll!call_function(_object * * * pp_stack, int oparg) Line 4730 C
  python35_d.dll!PyEval_EvalFrameEx(_frame * f, int throwflag) Line 3238 C
  python35_d.dll!fast_function(_object * func, _object * * * pp_stack,
int n, int na, int nk) Line 4804 C
  python35_d.dll!call_function(_object * * * pp_stack, int oparg) Line 4730 C
  python35_d.dll!PyEval_EvalFrameEx(_frame * f, int throwflag) Line 3238 C
  python35_d.dll!fast_function(_object * func, _object * * * pp_stack,
int n, int na, int nk) Line 4804 C
  python35_d.dll!call_function(_object * * * pp_stack, int oparg) Line 4730 C
  python35_d.dll!PyEval_EvalFrameEx(_frame * f, int throwflag) Line 3238 C
  python35_d.dll!fast_function(_object * func, _object * * * pp_stack,
int n, int na, int nk) Line 4804 C
  python35_d.dll!call_function(_object * * * pp_stack, int oparg) Line 4730 C
  python35_d.dll!PyEval_EvalFrameEx(_frame * f, int throwflag) Line 3238 C
  python35_d.dll!_PyEval_EvalCodeWithName(_object * _co, _object *
globals, _object * locals, _object * * args, int argcount, _object * *
kws, int kwcount, _object * * defs, int defcount, _object * kwdefs,
_object * closure, _object * name, _object * qualname) Line 4018 C
  python35_d.dll!PyEval_EvalCodeEx(_object * _co, _object * globals,
_object * locals, _object * * args, int argcount, _object * * kws, int
kwcount, _object * * defs, int defcount, _object * kwdefs, _object *
closure) Line 4043 C
  python35_d.dll!function_call(_object * func, _object * arg, _object
* kw) Line 627 C
  python35_d.dll!PyObject_Call(_object * func, _object * arg, _object
* kw) Line 2165 C
  python35_d.dll!_PyObject_CallMethodIdObjArgs(_object * callable,
_Py_Identifier * name, ...) Line 2423 C
  python35_d.dll!PyImport_ImportModuleLevelObject(_object * name,
_object * given_globals, _object * locals, _object * given_fromlist,
int level) Line 1595 C
  python35_d.dll!builtin___import__(_object * self, _object * args,
_object * kwds) Line 215 C
  python35_d.dll!PyCFunction_Call(_object * func, _object * args,
_object * kwds) Line 98 C
  python35_d.dll!PyObject_Call(_object * func, _object * arg, _object
* kw) Line 2165 C
  python35_d.dll!call_function_tail(_object * callable, _object *
args) Line 2191 C
  python35_d.dll!PyObject_CallFunction(_object * callable, const char
* format, ...) Line 2218 C
  python35_d.dll!PyImport_Import(_object * module_name) Line 1800 C
  python35_d.dll!PyImport_ImportModule(const char * name) Line 1263 C
  shiboken2_d.cp35-win_amd64.dll!Shiboken::Module::import(const char *
moduleName) Line 67 C++
> QtNetwork_d.cp35-win_amd64.pyd!PyInit_QtNetwork() Line 1125 C++
  python35_d.dll!_PyImport_LoadDynamicModuleWithSpec(_object * spec,
_iobuf * fp) Line 150 C

What kind of cause could make check_PepTypeObjectValid() to fail?
The proper Qt dlls and PySide pyd files seem loaded from my point of view.


From alexandru.croitor at qt.io  Fri Oct 12 16:24:12 2018
From: alexandru.croitor at qt.io (Alexandru Croitor)
Date: Fri, 12 Oct 2018 14:24:12 +0000
Subject: [PySide] The structure of type objects has changed!
In-Reply-To: <CA+cSArjRtoYZqfQ-x=Q2NAp3qLjDPW5P148t7cP43RN0adn+sA@mail.gmail.com>
References: <CA+cSArjRtoYZqfQ-x=Q2NAp3qLjDPW5P148t7cP43RN0adn+sA@mail.gmail.com>
Message-ID: <CF933EC9-D417-4C7B-89BC-D104AAAA0BD1@qt.io>

Hi,

It's a bug in the PySide2 code when building with debug interpreter on Windows.

I encountered the same, and had a local dirty fix.

You want to modify sources/shiboken2/libshiboken/pep384impl.cpp
and comment out the if ( .... probe_tp_name - check->tp_name != 0) line.

Consider opening a bug report, so we don't forget about it.




> On 12. Oct 2018, at 15:37, Olivier B. <perso.olivier.barthelemy at gmail.com> wrote:
> 
> I am getting this fatal error when importing PySide2 from a debug
> python on windows
> 
> Environment :
> I build my own python 3.5.2, Qt 5.11.1, and PySide2 5.11.1 (of july
> 27th), in a release and a debug build,
> with the same compiler, VS2015 on windows  and GCC 4.8 on Linux
> 
> On Linux, i can import PySide2 with my release and my debug python
> On windows, i can do it with the release python, but get the following
> error for the debug python
> 
> The console says
> Fatal Python error: The structure of type objects has changed!
> Current thread 0x0000367c (most recent call first):
>  File "<frozen importlib._bootstrap>", line 222 in _call_with_frames_removed
>  File "<frozen importlib._bootstrap_external>", line 906 in create_module
>  File "<frozen importlib._bootstrap>", line 577 in module_from_spec
>  File "<frozen importlib._bootstrap>", line 666 in _load_unlocked
>  File "<frozen importlib._bootstrap>", line 958 in _find_and_load_unlocked
>  File "<frozen importlib._bootstrap>", line 969 in _find_and_load
>  File "<frozen importlib._bootstrap>", line 222 in _call_with_frames_removed
>  File "<frozen importlib._bootstrap_external>", line 906 in create_module
>  File "<frozen importlib._bootstrap>", line 577 in module_from_spec
>  File "<frozen importlib._bootstrap>", line 666 in _load_unlocked
>  File "<frozen importlib._bootstrap>", line 958 in _find_and_load_unlocked
>  File "<frozen importlib._bootstrap>", line 969 in _find_and_load
>  File "<frozen importlib._bootstrap>", line 222 in _call_with_frames_removed
>  File "<frozen importlib._bootstrap>", line 1016 in _handle_fromlist
>  File "C:\...\python-3.5.2\lib\site-packages\PySide2\__init__.py",
> line 39 in _setupQtDirectories
>  File "C:\...\python-3.5.2\lib\site-packages\PySide2\__init__.py",
> line 47 in <module>
>  File "<frozen importlib._bootstrap>", line 222 in _call_with_frames_removed
>  File "<frozen importlib._bootstrap_external>", line 665 in exec_module
>  File "<frozen importlib._bootstrap>", line 673 in _load_unlocked
>  File "<frozen importlib._bootstrap>", line 958 in _find_and_load_unlocked
>  File "<frozen importlib._bootstrap>", line 969 in _find_and_load
>  File "<stdin>", line 1 in <module>
> 
> The call stack when it happens, triggered by the import of QNetwork
> from __init.py__:39
>  python35_d.dll!Py_FatalError(const char * msg) Line 1399 C
>  shiboken2_d.cp35-win_amd64.dll!check_PepTypeObject_valid() Line 441 C++
>  shiboken2_d.cp35-win_amd64.dll!Pep384_Init() Line 837 C++
>  shiboken2_d.cp35-win_amd64.dll!Shiboken::init() Line 554 C++
>  shiboken2_d.cp35-win_amd64.dll!Shiboken::Module::create(const char *
> moduleName, void * moduleData) Line 81 C++
>  QtCore_d.cp35-win_amd64.pyd!PyInit_QtCore() Line 4110 C++
>  python35_d.dll!_PyImport_LoadDynamicModuleWithSpec(_object * spec,
> _iobuf * fp) Line 150 C
>  python35_d.dll!_imp_create_dynamic_impl(PyModuleDef * module,
> _object * spec, _object * file) Line 2027 C
>  python35_d.dll!_imp_create_dynamic(PyModuleDef * module, _object *
> args) Line 282 C
>  python35_d.dll!PyCFunction_Call(_object * func, _object * args,
> _object * kwds) Line 109 C
>  python35_d.dll!ext_do_call(_object * func, _object * * * pp_stack,
> int flags, int na, int nk) Line 5032 C
>  python35_d.dll!PyEval_EvalFrameEx(_frame * f, int throwflag) Line 3278 C
>  python35_d.dll!_PyEval_EvalCodeWithName(_object * _co, _object *
> globals, _object * locals, _object * * args, int argcount, _object * *
> kws, int kwcount, _object * * defs, int defcount, _object * kwdefs,
> _object * closure, _object * name, _object * qualname) Line 4018 C
>  python35_d.dll!fast_function(_object * func, _object * * * pp_stack,
> int n, int na, int nk) Line 4818 C
>  python35_d.dll!call_function(_object * * * pp_stack, int oparg) Line 4730 C
>  python35_d.dll!PyEval_EvalFrameEx(_frame * f, int throwflag) Line 3238 C
>  python35_d.dll!fast_function(_object * func, _object * * * pp_stack,
> int n, int na, int nk) Line 4804 C
>  python35_d.dll!call_function(_object * * * pp_stack, int oparg) Line 4730 C
>  python35_d.dll!PyEval_EvalFrameEx(_frame * f, int throwflag) Line 3238 C
>  python35_d.dll!fast_function(_object * func, _object * * * pp_stack,
> int n, int na, int nk) Line 4804 C
>  python35_d.dll!call_function(_object * * * pp_stack, int oparg) Line 4730 C
>  python35_d.dll!PyEval_EvalFrameEx(_frame * f, int throwflag) Line 3238 C
>  python35_d.dll!fast_function(_object * func, _object * * * pp_stack,
> int n, int na, int nk) Line 4804 C
>  python35_d.dll!call_function(_object * * * pp_stack, int oparg) Line 4730 C
>  python35_d.dll!PyEval_EvalFrameEx(_frame * f, int throwflag) Line 3238 C
>  python35_d.dll!fast_function(_object * func, _object * * * pp_stack,
> int n, int na, int nk) Line 4804 C
>  python35_d.dll!call_function(_object * * * pp_stack, int oparg) Line 4730 C
>  python35_d.dll!PyEval_EvalFrameEx(_frame * f, int throwflag) Line 3238 C
>  python35_d.dll!_PyEval_EvalCodeWithName(_object * _co, _object *
> globals, _object * locals, _object * * args, int argcount, _object * *
> kws, int kwcount, _object * * defs, int defcount, _object * kwdefs,
> _object * closure, _object * name, _object * qualname) Line 4018 C
>  python35_d.dll!PyEval_EvalCodeEx(_object * _co, _object * globals,
> _object * locals, _object * * args, int argcount, _object * * kws, int
> kwcount, _object * * defs, int defcount, _object * kwdefs, _object *
> closure) Line 4043 C
>  python35_d.dll!function_call(_object * func, _object * arg, _object
> * kw) Line 627 C
>  python35_d.dll!PyObject_Call(_object * func, _object * arg, _object
> * kw) Line 2165 C
>  python35_d.dll!_PyObject_CallMethodIdObjArgs(_object * callable,
> _Py_Identifier * name, ...) Line 2423 C
>  python35_d.dll!PyImport_ImportModuleLevelObject(_object * name,
> _object * given_globals, _object * locals, _object * given_fromlist,
> int level) Line 1595 C
>  python35_d.dll!builtin___import__(_object * self, _object * args,
> _object * kwds) Line 215 C
>  python35_d.dll!PyCFunction_Call(_object * func, _object * args,
> _object * kwds) Line 98 C
>  python35_d.dll!PyObject_Call(_object * func, _object * arg, _object
> * kw) Line 2165 C
>  python35_d.dll!call_function_tail(_object * callable, _object *
> args) Line 2191 C
>  python35_d.dll!PyObject_CallFunction(_object * callable, const char
> * format, ...) Line 2218 C
>  python35_d.dll!PyImport_Import(_object * module_name) Line 1800 C
>  python35_d.dll!PyImport_ImportModule(const char * name) Line 1263 C
>  shiboken2_d.cp35-win_amd64.dll!Shiboken::Module::import(const char *
> moduleName) Line 67 C++
>> QtNetwork_d.cp35-win_amd64.pyd!PyInit_QtNetwork() Line 1125 C++
>  python35_d.dll!_PyImport_LoadDynamicModuleWithSpec(_object * spec,
> _iobuf * fp) Line 150 C
> 
> What kind of cause could make check_PepTypeObjectValid() to fail?
> The proper Qt dlls and PySide pyd files seem loaded from my point of view.
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside



From perso.olivier.barthelemy at gmail.com  Mon Oct 15 13:28:54 2018
From: perso.olivier.barthelemy at gmail.com (Olivier B.)
Date: Mon, 15 Oct 2018 13:28:54 +0200
Subject: [PySide] The structure of type objects has changed!
In-Reply-To: <CF933EC9-D417-4C7B-89BC-D104AAAA0BD1@qt.io>
References: <CA+cSArjRtoYZqfQ-x=Q2NAp3qLjDPW5P148t7cP43RN0adn+sA@mail.gmail.com>
	<CF933EC9-D417-4C7B-89BC-D104AAAA0BD1@qt.io>
Message-ID: <CA+cSAri0=G+rYQkzodqeMmQURiTu4p38c-bKiZCCkc1gpSi8Pg@mail.gmail.com>

Commenting out this test indeed passes the test thanks!. I'll submit a
bug,but i seem unable to login for now
Le ven. 12 oct. 2018 à 16:24, Alexandru Croitor
<alexandru.croitor at qt.io> a écrit :
>
> Hi,
>
> It's a bug in the PySide2 code when building with debug interpreter on Windows.
>
> I encountered the same, and had a local dirty fix.
>
> You want to modify sources/shiboken2/libshiboken/pep384impl.cpp
> and comment out the if ( .... probe_tp_name - check->tp_name != 0) line.
>
> Consider opening a bug report, so we don't forget about it.
>
>
>
>
> > On 12. Oct 2018, at 15:37, Olivier B. <perso.olivier.barthelemy at gmail.com> wrote:
> >
> > I am getting this fatal error when importing PySide2 from a debug
> > python on windows
> >
> > Environment :
> > I build my own python 3.5.2, Qt 5.11.1, and PySide2 5.11.1 (of july
> > 27th), in a release and a debug build,
> > with the same compiler, VS2015 on windows  and GCC 4.8 on Linux
> >
> > On Linux, i can import PySide2 with my release and my debug python
> > On windows, i can do it with the release python, but get the following
> > error for the debug python
> >
> > The console says
> > Fatal Python error: The structure of type objects has changed!
> > Current thread 0x0000367c (most recent call first):
> >  File "<frozen importlib._bootstrap>", line 222 in _call_with_frames_removed
> >  File "<frozen importlib._bootstrap_external>", line 906 in create_module
> >  File "<frozen importlib._bootstrap>", line 577 in module_from_spec
> >  File "<frozen importlib._bootstrap>", line 666 in _load_unlocked
> >  File "<frozen importlib._bootstrap>", line 958 in _find_and_load_unlocked
> >  File "<frozen importlib._bootstrap>", line 969 in _find_and_load
> >  File "<frozen importlib._bootstrap>", line 222 in _call_with_frames_removed
> >  File "<frozen importlib._bootstrap_external>", line 906 in create_module
> >  File "<frozen importlib._bootstrap>", line 577 in module_from_spec
> >  File "<frozen importlib._bootstrap>", line 666 in _load_unlocked
> >  File "<frozen importlib._bootstrap>", line 958 in _find_and_load_unlocked
> >  File "<frozen importlib._bootstrap>", line 969 in _find_and_load
> >  File "<frozen importlib._bootstrap>", line 222 in _call_with_frames_removed
> >  File "<frozen importlib._bootstrap>", line 1016 in _handle_fromlist
> >  File "C:\...\python-3.5.2\lib\site-packages\PySide2\__init__.py",
> > line 39 in _setupQtDirectories
> >  File "C:\...\python-3.5.2\lib\site-packages\PySide2\__init__.py",
> > line 47 in <module>
> >  File "<frozen importlib._bootstrap>", line 222 in _call_with_frames_removed
> >  File "<frozen importlib._bootstrap_external>", line 665 in exec_module
> >  File "<frozen importlib._bootstrap>", line 673 in _load_unlocked
> >  File "<frozen importlib._bootstrap>", line 958 in _find_and_load_unlocked
> >  File "<frozen importlib._bootstrap>", line 969 in _find_and_load
> >  File "<stdin>", line 1 in <module>
> >
> > The call stack when it happens, triggered by the import of QNetwork
> > from __init.py__:39
> >  python35_d.dll!Py_FatalError(const char * msg) Line 1399 C
> >  shiboken2_d.cp35-win_amd64.dll!check_PepTypeObject_valid() Line 441 C++
> >  shiboken2_d.cp35-win_amd64.dll!Pep384_Init() Line 837 C++
> >  shiboken2_d.cp35-win_amd64.dll!Shiboken::init() Line 554 C++
> >  shiboken2_d.cp35-win_amd64.dll!Shiboken::Module::create(const char *
> > moduleName, void * moduleData) Line 81 C++
> >  QtCore_d.cp35-win_amd64.pyd!PyInit_QtCore() Line 4110 C++
> >  python35_d.dll!_PyImport_LoadDynamicModuleWithSpec(_object * spec,
> > _iobuf * fp) Line 150 C
> >  python35_d.dll!_imp_create_dynamic_impl(PyModuleDef * module,
> > _object * spec, _object * file) Line 2027 C
> >  python35_d.dll!_imp_create_dynamic(PyModuleDef * module, _object *
> > args) Line 282 C
> >  python35_d.dll!PyCFunction_Call(_object * func, _object * args,
> > _object * kwds) Line 109 C
> >  python35_d.dll!ext_do_call(_object * func, _object * * * pp_stack,
> > int flags, int na, int nk) Line 5032 C
> >  python35_d.dll!PyEval_EvalFrameEx(_frame * f, int throwflag) Line 3278 C
> >  python35_d.dll!_PyEval_EvalCodeWithName(_object * _co, _object *
> > globals, _object * locals, _object * * args, int argcount, _object * *
> > kws, int kwcount, _object * * defs, int defcount, _object * kwdefs,
> > _object * closure, _object * name, _object * qualname) Line 4018 C
> >  python35_d.dll!fast_function(_object * func, _object * * * pp_stack,
> > int n, int na, int nk) Line 4818 C
> >  python35_d.dll!call_function(_object * * * pp_stack, int oparg) Line 4730 C
> >  python35_d.dll!PyEval_EvalFrameEx(_frame * f, int throwflag) Line 3238 C
> >  python35_d.dll!fast_function(_object * func, _object * * * pp_stack,
> > int n, int na, int nk) Line 4804 C
> >  python35_d.dll!call_function(_object * * * pp_stack, int oparg) Line 4730 C
> >  python35_d.dll!PyEval_EvalFrameEx(_frame * f, int throwflag) Line 3238 C
> >  python35_d.dll!fast_function(_object * func, _object * * * pp_stack,
> > int n, int na, int nk) Line 4804 C
> >  python35_d.dll!call_function(_object * * * pp_stack, int oparg) Line 4730 C
> >  python35_d.dll!PyEval_EvalFrameEx(_frame * f, int throwflag) Line 3238 C
> >  python35_d.dll!fast_function(_object * func, _object * * * pp_stack,
> > int n, int na, int nk) Line 4804 C
> >  python35_d.dll!call_function(_object * * * pp_stack, int oparg) Line 4730 C
> >  python35_d.dll!PyEval_EvalFrameEx(_frame * f, int throwflag) Line 3238 C
> >  python35_d.dll!fast_function(_object * func, _object * * * pp_stack,
> > int n, int na, int nk) Line 4804 C
> >  python35_d.dll!call_function(_object * * * pp_stack, int oparg) Line 4730 C
> >  python35_d.dll!PyEval_EvalFrameEx(_frame * f, int throwflag) Line 3238 C
> >  python35_d.dll!_PyEval_EvalCodeWithName(_object * _co, _object *
> > globals, _object * locals, _object * * args, int argcount, _object * *
> > kws, int kwcount, _object * * defs, int defcount, _object * kwdefs,
> > _object * closure, _object * name, _object * qualname) Line 4018 C
> >  python35_d.dll!PyEval_EvalCodeEx(_object * _co, _object * globals,
> > _object * locals, _object * * args, int argcount, _object * * kws, int
> > kwcount, _object * * defs, int defcount, _object * kwdefs, _object *
> > closure) Line 4043 C
> >  python35_d.dll!function_call(_object * func, _object * arg, _object
> > * kw) Line 627 C
> >  python35_d.dll!PyObject_Call(_object * func, _object * arg, _object
> > * kw) Line 2165 C
> >  python35_d.dll!_PyObject_CallMethodIdObjArgs(_object * callable,
> > _Py_Identifier * name, ...) Line 2423 C
> >  python35_d.dll!PyImport_ImportModuleLevelObject(_object * name,
> > _object * given_globals, _object * locals, _object * given_fromlist,
> > int level) Line 1595 C
> >  python35_d.dll!builtin___import__(_object * self, _object * args,
> > _object * kwds) Line 215 C
> >  python35_d.dll!PyCFunction_Call(_object * func, _object * args,
> > _object * kwds) Line 98 C
> >  python35_d.dll!PyObject_Call(_object * func, _object * arg, _object
> > * kw) Line 2165 C
> >  python35_d.dll!call_function_tail(_object * callable, _object *
> > args) Line 2191 C
> >  python35_d.dll!PyObject_CallFunction(_object * callable, const char
> > * format, ...) Line 2218 C
> >  python35_d.dll!PyImport_Import(_object * module_name) Line 1800 C
> >  python35_d.dll!PyImport_ImportModule(const char * name) Line 1263 C
> >  shiboken2_d.cp35-win_amd64.dll!Shiboken::Module::import(const char *
> > moduleName) Line 67 C++
> >> QtNetwork_d.cp35-win_amd64.pyd!PyInit_QtNetwork() Line 1125 C++
> >  python35_d.dll!_PyImport_LoadDynamicModuleWithSpec(_object * spec,
> > _iobuf * fp) Line 150 C
> >
> > What kind of cause could make check_PepTypeObjectValid() to fail?
> > The proper Qt dlls and PySide pyd files seem loaded from my point of view.
> > _______________________________________________
> > PySide mailing list
> > PySide at qt-project.org
> > http://lists.qt-project.org/mailman/listinfo/pyside
>