kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #15004
Re: [PATCH] Python scripting crashed with multiple wxPython versions
-
To:
kicad-developers@xxxxxxxxxxxxxxxxxxx
-
From:
Wayne Stambaugh <stambaughw@xxxxxxxxxxx>
-
Date:
Tue, 07 Oct 2014 09:05:14 -0400
-
In-reply-to:
<CAA-CTZ-J1NokhPLkrv1p73YzPzHEm2D72TN=+W9DWJmyDLH=bQ@mail.gmail.com>
-
User-agent:
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
On 9/29/2014 2:28 AM, Francesco Del Degan wrote:
> Hi,
> I found that if you have multiple versions of wxPython (2.8 and 3.0)
> installed and
> enabled WX_PYTOHN_SCRIPTING macro, the wxPyCoreAPI_IMPORT call will
> select the default one (in my case 2.8), and it will SEGV.
>
> This because it does an import of wx._core_ and in my case is 2.8.
> (Ubuntu 14.04)
>
> The patch calls wxversion.select() method to select 3.0 version before
> wxCoreAPI_IMPORT call.
>
> Cheers,
> Francesco
>
Hi Francesco,
Thank you for making me aware of this problem. This is patch solves
your immediate problem but just creates another one. What really needs
to happen is the wxPython version string used to build KiCad should be
determined by CMake during the build configuration to set the the
appropriate wx version selection. I will add this to my todo list.
For future reference, please ensure your code conforms to the kicad
coding policy before submitting patches.
Regards,
Wayne
References