Phoenix and Linux repositories

Mario_Lacunza · January 9, 2018, 7:20pm

Hahaha no problem!

···

El 9 ene. 2018 14:12, “Rufus Smith” rufusvsmith@gmail.com escribió:

There it was, right in front of my face!

I must have been multitasking the first time I looked there.

Sorry about that.

Thanks, Mario!

On Jan 9, 2018, at 10:56 AM, Mario Lacunza mlacunza@gmail.com wrote:

What about click in the first link in that page?

https://www.python.org/dev/peps/pep-0373/#id2

Enviado desde mi celular LG

–

You received this message because you are subscribed to the Google Groups “wxPython-users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to wxpython-users+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

El 8 ene. 2018 23:06, “Rufus Smith” rufusvsmith@gmail.com escribió:

I looked at that pythonclock.org link, but there is no indication it is an official site.

On Jan 8, 2018, at 12:25 PM, Mario Lacunza mlacunza@gmail.com wrote:

Its offcial now, Python 2 EOL is 2020: https://pythonclock.org/

–

You received this message because you are subscribed to the Google Groups “wxPython-users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to wxpython-users+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Saludos / Best regards

Mario Lacunza
Email:: mlacunza@gmail.com
Personal Website:: http://www.lacunza.biz/
Hosting:: http://mlv-host.com/
Skype: mlacunzav

Lima - Peru

2018-01-08 12:08 GMT-05:00 Tim Roberts timr@probo.com:

Donn Ingle wrote:

A January bump for the news about wxPython 4 on Linux repos. Is there

a chance?

I worry because Python 2 is going to be dead very soon…

I doubt it. Rumors of Python 2’s demise have been reported for the

entire 10 years of Python 3’s existence. I certainly don’t see any

slacking off in Python 2 development. It is a fascinating study, and it

shows just how useful and solid Python 2 was.

–

Tim Roberts, timr@probo.com

Providenza & Boekelheide, Inc.

–

You received this message because you are subscribed to the Google Groups “wxPython-users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to wxpython-users+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Gadget_Steve · January 9, 2018, 7:39pm

Based on my experiences of porting from wxPython 3 -> 4 I would say that
95% is either compatible or points out things that you were getting away
with and can't any more rather than things that are incompatible between
the two. By that I mean that once I get things working in 4 they still
work or work better in 3.

The sole exception that I have had so far is that some of the import
paths have changed - these are easily handled with a:

try:
import wx.xxxx
except ImportError:
import wx.yyyy as xxxx

This allows me to carry on maintaining my Python 2.7/wxPython 3 code and
porting towards 3.5+/4 which is a nice place to be.

Hope that helps,

Steve

···

On 09/01/2018 09:23, Donn Ingle wrote:

Scott,
That would be grand!
I am sure it will be good to start facing the teething troubles of the
process sooner than later.
(I shall have to figure out how to keep both versions apart somehow as I
start the 3 -> 4 conversion. Eek!)

Do you have any news from Robin et al. re a release date? (Should I join
the dev list instead and ask there?)

Thanks,
/d

On 9 January 2018 at 06:51, Scott Talbert <swt@techie.net > <mailto:swt@techie.net>> wrote:

    The answer is pretty much the same as before. I'm still waiting on
    an official release to move forward with official packaging.

    I can, however, make a PPA though, so I'll work on that.

    I have had a COPR (Fedora PPA-like repository) for quite some time
    with RPMs:
    https://copr.fedorainfracloud.org/coprs/swt2c/wxPython-Phoenix/
    <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcopr.fedorainfracloud.org%2Fcoprs%2Fswt2c%2FwxPython-Phoenix%2F&data=02|01||173d736dd5874ccc2cf108d55742b671|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636510866391505078&sdata=9yBn2uUee%2FgHzRI7PsSIPW6mfkZFfDPxy9uyZgF2ib4%3D&reserved=0>

    On Mon, 8 Jan 2018, Donn Ingle wrote:

        A January bump for the news about wxPython 4 on Linux repos. Is
        there a
        chance?

        I worry because Python 2 is going to be dead very soon and
        decision have to
        be made this year about continuing to use wxPython, or switching to
        something else like (urgh..) python-gobject. (I only urgh it
        because of the
        learning curve I'm facing. It might be okay, I dunno.)

        Perhaps some kind of beta release on Launchpad as a PPA (I don't
        know what
        the rpm version of that is)?

        Hoping for the best,
        /d

        On 9 November 2017 at 16:08, Scott Talbert <swt@techie.net > <mailto:swt@techie.net>> wrote:
          On Thu, 9 Nov 2017, /d wrote:

          Hi,
          I searched around a bit, but I think this is a
          newish question:

          Is Phoenix ready to be on the formal .deb/.rpm repos
          for Linux? What's the
          ETA, etc?

          I could move my little app up to Python 3 if it
          were. I am a little worried
          that Python 2.7 is soon to be dropped and I'll be
          somewhat stuck.

          I'll totally understand if it's not on the horizon.
          Thankful that you all
          keep hacking on it. Good luck!
          Thanks,
          Donn
          (Fonty Python.)

          I am planning to package Phoenix for Fedora (and probably
        Debian
          too) but I am waiting for the first official non-beta
        release.
          This seems like it may be soon as Robin has moved to "rc"
          designations for the beta releases.

          Scott

          --
          You received this message because you are subscribed to a
        topic
          in the Google Groups "wxPython-users" group.
          To unsubscribe from this topic, visit
        https://groups.google.com/d/topic/wxpython-users/54wHFZ4xKFQ/unsubscribe
        <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Ftopic%2Fwxpython-users%2F54wHFZ4xKFQ%2Funsubscribe&data=02|01||173d736dd5874ccc2cf108d55742b671|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636510866391505078&sdata=fT9kz1jRYxEJh6LRghKnqD18l80qs%2F2BveV3NsIBSos%3D&reserved=0>\.
          To unsubscribe from this group and all its topics, send
        an email
          to wxpython-users+unsubscribe@googlegroups.com
        <mailto:wxpython-users%2Bunsubscribe@googlegroups.com>.
          For more options, visit
        https://groups.google.com/d/optout
        <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Foptout&data=02|01||173d736dd5874ccc2cf108d55742b671|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636510866391505078&sdata=EdkcvutnbMZ502bJYuKkUV6PgGJkHXYfMrOiWc8xdcc%3D&reserved=0>\.

        --
        You received this message because you are subscribed to the
        Google Groups
        "wxPython-users" group.
        To unsubscribe from this group and stop receiving emails from
        it, send an
        email to wxpython-users+unsubscribe@googlegroups.com
        <mailto:wxpython-users%2Bunsubscribe@googlegroups.com>.
        For more options, visit https://groups.google.com/d/optout
        <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Foptout&data=02|01||173d736dd5874ccc2cf108d55742b671|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636510866391505078&sdata=EdkcvutnbMZ502bJYuKkUV6PgGJkHXYfMrOiWc8xdcc%3D&reserved=0>\.

    --
    You received this message because you are subscribed to a topic in
    the Google Groups "wxPython-users" group.
    To unsubscribe from this topic, visit
    https://groups.google.com/d/topic/wxpython-users/54wHFZ4xKFQ/unsubscribe
    <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Ftopic%2Fwxpython-users%2F54wHFZ4xKFQ%2Funsubscribe&data=02|01||173d736dd5874ccc2cf108d55742b671|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636510866391505078&sdata=fT9kz1jRYxEJh6LRghKnqD18l80qs%2F2BveV3NsIBSos%3D&reserved=0>\.
    To unsubscribe from this group and all its topics, send an email to
    wxpython-users+unsubscribe@googlegroups.com
    <mailto:wxpython-users%2Bunsubscribe@googlegroups.com>.
    For more options, visit https://groups.google.com/d/optout
    <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Foptout&data=02|01||173d736dd5874ccc2cf108d55742b671|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636510866391505078&sdata=EdkcvutnbMZ502bJYuKkUV6PgGJkHXYfMrOiWc8xdcc%3D&reserved=0>\.

--
You received this message because you are subscribed to the Google
Groups "wxPython-users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to wxpython-users+unsubscribe@googlegroups.com
<mailto:wxpython-users+unsubscribe@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout
<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Foptout&data=02|01||173d736dd5874ccc2cf108d55742b671|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636510866391505078&sdata=EdkcvutnbMZ502bJYuKkUV6PgGJkHXYfMrOiWc8xdcc%3D&reserved=0>\.

--
Steve (Gadget) Barnes
Any opinions in this message are my personal opinions and do not reflect
those of my employer.

_d11 · January 9, 2018, 7:40pm

Okay. Your work is much appreciated and I shall be patient.

I will attempt a virtualenv + pip thing, to get a gradual upgrade process going.

/d

···

On 9 January 2018 at 21:00, Robin Dunn robin@alldunn.com wrote:

On Tuesday, January 9, 2018 at 1:23:58 AM UTC-8, /d wrote:

Scott,

That would be grand!

I am sure it will be good to start facing the teething troubles of the process sooner than later.

(I shall have to figure out how to keep both versions apart somehow as I start the 3 → 4 conversion. Eek!)

Do you have any news from Robin et al. re a release date? (Should I join the dev list instead and ask there?)

I’ve learned the hard way to not give dates and usually just say that it will be released when it’s ready. It does feel like it’s getting close however. The project is really too big and understaffed to shoot for a perfect release, but when it feels like it’s good enough for most people then that’s when I start considering making a release.

–

Robin Dunn

Software Craftsman

http://wxPython.org

–

You received this message because you are subscribed to a topic in the Google Groups “wxPython-users” group.

To unsubscribe from this topic, visit https://groups.google.com/d/topic/wxpython-users/54wHFZ4xKFQ/unsubscribe.

To unsubscribe from this group and all its topics, send an email to wxpython-users+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Matt_Newville · January 9, 2018, 9:06pm

Hi Robin,

···

On Tue, Jan 9, 2018 at 1:00 PM, Robin Dunn robin@alldunn.com wrote:

On Tuesday, January 9, 2018 at 1:23:58 AM UTC-8, /d wrote:

Scott,

That would be grand!

I am sure it will be good to start facing the teething troubles of the process sooner than later.

(I shall have to figure out how to keep both versions apart somehow as I start the 3 → 4 conversion. Eek!)

Do you have any news from Robin et al. re a release date? (Should I join the dev list instead and ask there?)

I’ve learned the hard way to not give dates and usually just say that it will be released when it’s ready. It does feel like it’s getting close however. The project is really too big and understaffed to shoot for a perfect release, but when it feels like it’s good enough for most people then that’s when I start considering making a release.

I am sympathetic to “it’s done when it’s done” approach. And I am most grateful for the continued dedication to wxPython and the incredible effort that went into the rewrite of wxPython 4.

I also agree that no one would expect wxPython 4.0.0 to be absolutely perfect or a replacement for every feature of wxPython 3. Are there significant missing or broken features preventing a release? I don’t know of any. I do not use every corner of wxPython, but I use a good amount of it and rely on it for daily work. For my needs, wxPython 4 has been extremely stable and shows no significant bugs or missing features.

It seems that external packaging systems would be much more likely to provide wxPython4 packages for Python 3 and Python 2 if it were officially “released”. The lack of a release may be furthering the misconception that wxPython 4 is not yet really working or that wxPython cannot be used with Python 3.

That is, I would encourage a release of wxPython 4 sooner rather than later and to take the victory lap for the enormous effort that went into Phoenix / wxPython 4.

Is there anything that we can do to make that easier?

Cheers,

–Matt Newville

Robin · January 10, 2018, 1:38am

I’ll be finishing up the last big thing that’s been on my mind soonish, then I’ll take a trip through the open issues and see if there’s something I’ve forgotten or something that is critical to be fixed. So, like I said, it’s feeling like the release is close.

···

On Tuesday, January 9, 2018 at 1:07:29 PM UTC-8, Matt Newville wrote:

I am sympathetic to “it’s done when it’s done” approach. And I am most grateful for the continued dedication to wxPython and the incredible effort that went into the rewrite of wxPython 4.

I also agree that no one would expect wxPython 4.0.0 to be absolutely perfect or a replacement for every feature of wxPython 3. Are there significant missing or broken features preventing a release? I don’t know of any. I do not use every corner of wxPython, but I use a good amount of it and rely on it for daily work. For my needs, wxPython 4 has been extremely stable and shows no significant bugs or missing features.

–

Robin Dunn

Software Craftsman

Matt_Newville · January 10, 2018, 3:42am

Great. Thanks very much!

--Matt Newville

···

On Tue, Jan 9, 2018 at 7:38 PM, Robin Dunn <robin@alldunn.com> wrote:

On Tuesday, January 9, 2018 at 1:07:29 PM UTC-8, Matt Newville wrote:

I am sympathetic to "it's done when it's done" approach. And I am most
grateful for the continued dedication to wxPython and the incredible effort
that went into the rewrite of wxPython 4.

I also agree that no one would expect wxPython 4.0.0 to be absolutely
perfect or a replacement for every feature of wxPython 3. Are there
significant missing or broken features preventing a release? I don't know
of any. I do not use every corner of wxPython, but I use a good amount of
it and rely on it for daily work. For my needs, wxPython 4 has been
extremely stable and shows no significant bugs or missing features.

I'll be finishing up the last big thing that's been on my mind soonish,
then I'll take a trip through the open issues and see if there's something
I've forgotten or something that is critical to be fixed. So, like I said,
it's feeling like the release is close.

_d11 · January 11, 2018, 8:17am

Steve,

That’s an interesting approach.

I have been using the docs for 4 a lot while hacking in 3, and to me they seem identical, so… yeah!

The only tricky thing would be having 3 and 4 somehow side-by-side installed into a Linux fs.

I think I’ll try the virtualenv voodoo first; see how it goes.

Thanks for the insight,

/d

···

On 9 January 2018 at 21:39, Steve Barnes gadgetsteve@live.co.uk wrote:

Based on my experiences of porting from wxPython 3 → 4 I would say that

95% is either compatible or points out things that you were getting away

with and can’t any more rather than things that are incompatible between

the two. By that I mean that once I get things working in 4 they still

work or work better in 3.

The sole exception that I have had so far is that some of the import

paths have changed - these are easily handled with a:

try:
 import wx.xxxx
except ImportError:
 import wx.yyyy as xxxx
This allows me to carry on maintaining my Python 2.7/wxPython 3 code and

porting towards 3.5+/4 which is a nice place to be.

Hope that helps,

Steve

swt2c · January 15, 2018, 4:48am

Okay, so I've got a PPA ready with current snapshots:

Right now it only has packages for Xenial. Let me know if there is demand for builds in other releases.

The package names follow the existing Debian naming:
python-wxgtk4.0 (for the Python 2 package)
python-wxgtk-media4.0 (for the Python 2 media module)
python3-wxgtk4.0 (for the Python 3 package)
python3-wxgtk-media4.0 (for the Python 3 media module)

Note that for the python 2 versions, the files install to a location that is not in the standard python path (so as to not conflict with the official classic packages), so to use the python 2 version, you'll have to change your PYTHONPATH to find it.

Let me know if you notice any problems.

Scott

···

On Tue, 9 Jan 2018, Karsten Hilbert wrote:

On Mon, Jan 08, 2018 at 11:51:47PM -0500, Scott Talbert wrote:

The answer is pretty much the same as before. I'm still waiting on an
official release to move forward with official packaging.

I can, however, make a PPA though, so I'll work on that.

Yes, please !!

Karsten_Hilbert · January 15, 2018, 9:32am

>
> > The answer is pretty much the same as before. I'm still waiting on an
> > official release to move forward with official packaging.
> >
> > I can, however, make a PPA though, so I'll work on that.

Okay, so I've got a PPA ready with current snapshots:
wxPython 4 (Phoenix) : Scott Talbert

MANY thanks ! This is even better than I hoped -- it'll
allow me to use Phoenix while staying with py2 for the time
being (which is not the goal but tremendously helps in
separating concerns while porting to both py3 and wxp4).

Right now it only has packages for Xenial. Let me know if there is demand
for builds in other releases.

I know it's much to be asked for but Debian Testing (or
Unstable) would be even closer to my "supported target
platform"

Note that for the python 2 versions, the files install to a location that is
not in the standard python path (so as to not conflict with the official
classic packages), so to use the python 2 version, you'll have to change
your PYTHONPATH to find it.

Debian uses wx.pth to prefer wxp versions over another at the
system level (unless the user explicitely uses wxversion,
which is gone for good in wxp4):

  root@hermes:~/bin# ls -la /usr/lib/python2.7/dist-packages/wx.pth
  lrwxrwxrwx 1 root root 22 Dez 17 04:33 /usr/lib/python2.7/dist-packages/wx.pth -> ../../wx/python/wx.pth
  root@hermes:~/bin# cat /usr/lib/python2.7/dist-packages/wx.pth
  wx-3.0-gtk2
  root@hermes:~/bin#

wx.pth, in turn, is controlled by update-alternatives:

  wx.pth - auto mode
    link best version is /usr/lib/wx/python/wx3.0.pth
    link currently points to /usr/lib/wx/python/wx3.0.pth
    link wx.pth is /usr/lib/wx/python/wx.pth
  /usr/lib/wx/python/wx3.0.pth - priority 30

in /etc/alternatives:

lrwxrwxrwx 1 root root 28 Dez 22 11:09 /etc/alternatives/wx.pth -> /usr/lib/wx/python/wx3.0.pth

AFAICT, "update-alternatives --install" adds a new option:

update-alternatives(1) dpkg suite update-alternatives(1)

  NAME
         update-alternatives - maintain symbolic links
         determining default commands

SYNOPSIS
update-alternatives [option...] command

  COMMANDS
         --install link name path priority [--slave link
         name path]...
                Add a group of alternatives to the system.
                link is the generic name for the master
                link, name is the name of its symlink in the
                alternatives directory, and path is the
                alternative being introduced for the master
                link. The arguments after --slave are the
                generic name, symlink name in the
                alternatives directory and the alternative
                path for a slave link. Zero or more --slave
                options, each followed by three arguments,
                may be specified. Note that the master
                alternative must exist or the call will
                fail. However if a slave alternative doesn't
                exist, the corresponding slave alternative
                link will simply not be installed (a warning
                will still be displayed). If some real file
                is installed where an alternative link has
                to be installed, it is kept unless --force
                is used.

                If the alternative name specified exists
                already in the alternatives system's
                records, the information supplied will be
                added as a new set of alternatives for the
                group. Otherwise, a new group, set to
                automatic mode, will be added with this
                information. If the group is in automatic
                mode, and the newly added alternatives'
                priority is higher than any other installed
                alternatives for this group, the symlinks
                will be updated to point to the newly added
                alternatives.

which might be worthwhile in postinst.

But I guess you knew that

(Not sure this helps with the PYTHONPATH, though.)

Regards,
Karsten

···

On Sun, Jan 14, 2018 at 11:48:37PM -0500, Scott Talbert wrote:

> On Mon, Jan 08, 2018 at 11:51:47PM -0500, Scott Talbert wrote:

--
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346

_d11 · January 15, 2018, 11:24am

Thank you Scott. I will try it as soon as I can!

/d

···

On 15 January 2018 at 06:48, Scott Talbert swt@techie.net wrote:

On Mon, Jan 08, 2018 at 11:51:47PM -0500, Scott Talbert wrote:

The answer is pretty much the same as before. I’m still waiting on an

official release to move forward with official packaging.

I can, however, make a PPA though, so I’ll work on that.

Yes, please !!
On Tue, 9 Jan 2018, Karsten Hilbert wrote:

Okay, so I’ve got a PPA ready with current snapshots:

https://launchpad.net/~swt-techie/+archive/ubuntu/wxpython4

Right now it only has packages for Xenial. Let me know if there is demand for builds in other releases.

The package names follow the existing Debian naming:

python-wxgtk4.0 (for the Python 2 package)

python-wxgtk-media4.0 (for the Python 2 media module)

python3-wxgtk4.0 (for the Python 3 package)

python3-wxgtk-media4.0 (for the Python 3 media module)

Note that for the python 2 versions, the files install to a location that is not in the standard python path (so as to not conflict with the official classic packages), so to use the python 2 version, you’ll have to change your PYTHONPATH to find it.

Let me know if you notice any problems.

Scott

–

You received this message because you are subscribed to a topic in the Google Groups “wxPython-users” group.

To unsubscribe from this topic, visit https://groups.google.com/d/topic/wxpython-users/54wHFZ4xKFQ/unsubscribe.

To unsubscribe from this group and all its topics, send an email to wxpython-users+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

swt2c · January 15, 2018, 1:46pm

The answer is pretty much the same as before. I'm still waiting on an
official release to move forward with official packaging.

I can, however, make a PPA though, so I'll work on that.

Okay, so I've got a PPA ready with current snapshots:
wxPython 4 (Phoenix) : Scott Talbert

MANY thanks ! This is even better than I hoped -- it'll
allow me to use Phoenix while staying with py2 for the time
being (which is not the goal but tremendously helps in
separating concerns while porting to both py3 and wxp4).

Yes, I figured it would be easier for people to be able to move one step at a time.

Right now it only has packages for Xenial. Let me know if there is demand
for builds in other releases.

I know it's much to be asked for but Debian Testing (or
Unstable) would be even closer to my "supported target
platform"

Sure, I can do builds for Unstable too. Last time I checked, though, there's not any sort of PPA for Debian, so the best I can think of would be to just post the debs somewhere. Would that work?

Also, the version of sip that's in Unstable is currently broken, so I'll need to figure out what to do with that.

Note that for the python 2 versions, the files install to a location that is
not in the standard python path (so as to not conflict with the official
classic packages), so to use the python 2 version, you'll have to change
your PYTHONPATH to find it.

Debian uses wx.pth to prefer wxp versions over another at the
system level (unless the user explicitely uses wxversion,
which is gone for good in wxp4):

  root@hermes:~/bin# ls -la /usr/lib/python2.7/dist-packages/wx.pth
  lrwxrwxrwx 1 root root 22 Dez 17 04:33 /usr/lib/python2.7/dist-packages/wx.pth -> ../../wx/python/wx.pth
  root@hermes:~/bin# cat /usr/lib/python2.7/dist-packages/wx.pth
  wx-3.0-gtk2
  root@hermes:~/bin#

wx.pth, in turn, is controlled by update-alternatives:

  wx.pth - auto mode
    link best version is /usr/lib/wx/python/wx3.0.pth
    link currently points to /usr/lib/wx/python/wx3.0.pth
    link wx.pth is /usr/lib/wx/python/wx.pth
  /usr/lib/wx/python/wx3.0.pth - priority 30

in /etc/alternatives:

  lrwxrwxrwx 1 root root 28 Dez 22 11:09 /etc/alternatives/wx.pth -> /usr/lib/wx/python/wx3.0.pth

But I guess you knew that

(Not sure this helps with the PYTHONPATH, though.)

Actually, I had forgotten about wx.pth, but that appears to be part of Classic's version selection mechanism, rather than being something specific to Debian. It appears that it is gone in Phoenix too.

Scott

···

On Mon, 15 Jan 2018, Karsten Hilbert wrote:

Karsten_Hilbert · January 15, 2018, 2:28pm

> I know it's much to be asked for but Debian Testing (or
> Unstable) would be even closer to my "supported target
> platform"

Sure, I can do builds for Unstable too. Last time I checked, though,
there's not any sort of PPA for Debian, so the best I can think of would be
to just post the debs somewhere. Would that work?

I have installed the Xenial packages by adding the Ubuntu PPA
line into my sources.lst and it seems to work just fine so
far, so no rush with that, I suppose.

> > Note that for the python 2 versions, the files install to a location that is
> > not in the standard python path (so as to not conflict with the official
> > classic packages), so to use the python 2 version, you'll have to change
> > your PYTHONPATH to find it.
>
> Debian uses wx.pth to prefer wxp versions over another at the
> system level (unless the user explicitely uses wxversion,
> which is gone for good in wxp4):
>
> root@hermes:~/bin# ls -la /usr/lib/python2.7/dist-packages/wx.pth
> lrwxrwxrwx 1 root root 22 Dez 17 04:33 /usr/lib/python2.7/dist-packages/wx.pth -> ../../wx/python/wx.pth
> root@hermes:~/bin# cat /usr/lib/python2.7/dist-packages/wx.pth
> wx-3.0-gtk2
> root@hermes:~/bin#
>
> wx.pth, in turn, is controlled by update-alternatives:
>
> wx.pth - auto mode
> link best version is /usr/lib/wx/python/wx3.0.pth
> link currently points to /usr/lib/wx/python/wx3.0.pth
> link wx.pth is /usr/lib/wx/python/wx.pth
> /usr/lib/wx/python/wx3.0.pth - priority 30
>
> in /etc/alternatives:
>
> lrwxrwxrwx 1 root root 28 Dez 22 11:09 /etc/alternatives/wx.pth -> /usr/lib/wx/python/wx3.0.pth
>
> But I guess you knew that
>
> (Not sure this helps with the PYTHONPATH, though.)

Actually, I had forgotten about wx.pth, but that appears to be part of
Classic's version selection mechanism, rather than being something specific
to Debian. It appears that it is gone in Phoenix too.

AFAICT, *.pth files are a Python mechanism, independent of
wxPython/wxPhoenix.

28.14. site — Site-specific configuration hook — Python 2.7.18 documentation

Adding an alternative filling wx.pth with the path to the
Phoenix package "should" work just fine.

I have manually added a

/usr/lib/python2.7/dist-packages/wxp4custom

link pointing to the /usr/lib/python2.7/dist-packages/wxP*
that get's created when your deb is installed.

In my Python scripts I can then go:

import sys
sys.path.insert(0, '/usr/lib/python2.7/dist-packages/wxp4custom')

et voila, "import wx" gives me wxPhoenix.

Karsten

···

On Mon, Jan 15, 2018 at 08:46:55AM -0500, Scott Talbert wrote:
--
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346