Phoenix and Linux repositories

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'd be my hero for providing DEBs.

They are sorely needed for bringing GNUmed (http://www.gnumed.de)
into the age of Python3/wxP4.

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

> 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, ti...@probo.com
Providenza & Boekelheide, Inc.

When doing so, please be aware that Pip does not find the Linux binaries
by default and tries to build from source instead.
See the section "Yes, we have Linux Wheels. Sort of." on the download page.

Regards,

Dietmar

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/
> to wxpython-user...@googlegroups.com.
> --
> You received this message because you are subscribed to the Google Groups
> "wxPython-users" group.

Yes, please !! :-)

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
> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcopr.fedorainfracloud.org%2Fcoprs%2Fswt2c%2FwxPython-Phoenix%2F&data=02%7C01%7C%7C173d736dd5874ccc2cf108d55742b671%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636510866391505078&sdata=9yBn2uUee%2FgHzRI7PsSIPW6mfkZFfDPxy9uyZgF2ib4%3D&reserved=0>
> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Ftopic%2Fwxpython-users%2F54wHFZ4xKFQ%2Funsubscribe&data=02%7C01%7C%7C173d736dd5874ccc2cf108d55742b671%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636510866391505078&sdata=fT9kz1jRYxEJh6LRghKnqD18l80qs%2F2BveV3NsIBSos%3D&reserved=0>.
>       to wxpython-user...@googlegroups.com
> <mailto:wxpython-users%2Bunsu...@googlegroups.com>.
> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Foptout&data=02%7C01%7C%7C173d736dd5874ccc2cf108d55742b671%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636510866391505078&sdata=EdkcvutnbMZ502bJYuKkUV6PgGJkHXYfMrOiWc8xdcc%3D&reserved=0>.
> email to wxpython-user...@googlegroups.com
> <mailto:wxpython-users%2Bunsu...@googlegroups.com>.
> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Foptout&data=02%7C01%7C%7C173d736dd5874ccc2cf108d55742b671%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636510866391505078&sdata=EdkcvutnbMZ502bJYuKkUV6PgGJkHXYfMrOiWc8xdcc%3D&reserved=0>.
> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Ftopic%2Fwxpython-users%2F54wHFZ4xKFQ%2Funsubscribe&data=02%7C01%7C%7C173d736dd5874ccc2cf108d55742b671%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636510866391505078&sdata=fT9kz1jRYxEJh6LRghKnqD18l80qs%2F2BveV3NsIBSos%3D&reserved=0>.
> wxpython-user...@googlegroups.com
> <mailto:wxpython-users%2Bunsu...@googlegroups.com>.
> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Foptout&data=02%7C01%7C%7C173d736dd5874ccc2cf108d55742b671%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636510866391505078&sdata=EdkcvutnbMZ502bJYuKkUV6PgGJkHXYfMrOiWc8xdcc%3D&reserved=0>.
> an email to wxpython-user...@googlegroups.com
> <mailto:wxpython-user...@googlegroups.com>.
> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Foptout&data=02%7C01%7C%7C173d736dd5874ccc2cf108d55742b671%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636510866391505078&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.

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

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).
I know it's much to be asked for but Debian Testing (or
Unstable) would be even closer to my "supported target
platform" :-)
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,

Yes, I figured it would be easier for people to be able to move one step
at a time. :)
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.
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

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.
AFAICT, *.pth files are a Python mechanism, independent of
wxPython/wxPhoenix.

https://docs.python.org/2/library/site.html

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.