what's the phoenix equivalent of /wx/wxPython/wxPython.h?

[miles mccoo]

I have a c++ application that uses wxwidges and has a python interface. It also uses wxpython 3.0 (last released in 2014)

I'm trying the rabbit hole of moving to wxpython 4.0

From c++ code, I want to take a wxWindow*, convert it to some sort of PyObject and then call a python function passing that converted/wrapped/... thing.

In wxpython 3.0, I call 

 PyObject*   arg = wxPyMake_wxObject( parent, false );

I can then pass arg along to PyEval_CallObject (via a py tuple)

wxPyMake_wxObject is defined in wxPython.h

looking in the wxPython 4.0 whls, I don't see any header files.

What am I missing?

Thanks in advance

Miles 

[Robin Dunn]

There hasn't been much focus yet on using Phoenix in an embedding situation, but I expect that it will still work with some adjustments.  There has been lots of internal changes in Phoenix, including the wrapper tech and runtime APIs, but many of the old API functions are still present more or less. 

Currently the header file you'll need is only in the source tree, in src/wxpy_api.h. You may want to get that and see how far you can get with it.

-- 

Robin Dunn

Software Craftsman

http://wxPython.org

[miles mccoo]

Thank you, Robin, for the help. src/wxpy_api.h has what I need.

Since I got it to work, I'll say that the application is Kicad's layout editor pcbnew. I am not a Kicad developer; just an occasional contributor.

I did a writeup of the journey here: https://kicad.mmccoo.com/2017/11/23/learnings-from-moving-kicad-to-wxpython-4-0/ as well as a mail to the kicad folks.

The most response I've gotten that's most relevant to you was here:

> The short version: Kicad will probably want to wait to move to the
> Phoenix version of wxPython.
Not until they are package in Debian stable. This is my litmus test for
availability of new dependencies. I do not want kicad to be in the
business of building dependencies. We have already traveled down that
road and it was not a fun journey.

If nothing else, I recommend including src/wxpy_api.h somewhere in the releases.

It's not urgent, but some day, the kicad folks will want to migrate to Phoenix.

Miles