Package Details: python2-wxpython-phoenix 4.0.1-2

Git Clone URL: (read-only)
Package Base: python-wxpython-phoenix
Description: wxPython 4.x. This is a split package providing both Python 2 and Python 3 versions of wxPython 4.x (aka wxPython Phoenix)
Upstream URL:
Licenses: custom:wxWindows
Conflicts: python-wxpython, sk1, wammu, wxpython-phoenix-bin, wxpython-phoenix-git
Provides: python-wxpython, wxpython-phoenix
Replaces: wxpython-phoenix
Submitter: tobac
Maintainer: tobac
Last Packager: tobac
Votes: 3
Popularity: 0.009587
First Submitted: 2018-01-24 13:20
Last Updated: 2018-04-07 18:15

Required by (11)

Sources (1)

Latest Comments

1 2 3 Next › Last »

tobac commented on 2018-06-06 04:37

@e7p Thanks for letting me know. I didn't have any problems in my test runs, but it's entirely possible I didn't test properly. I'll look into it.

e7p commented on 2018-06-04 21:10

@tobac I assume that the 'provides' addition of 'python-wxpython' breaks installation of both python2 and python3 versions at the same time. At least I got "python-wxpython-phoenix and python2-wxpython-phoenix are in conflict" when trying to install both parts of this package when this 'provides' is in the PKGBUILD.

On the other hand I needed the 'provides' 'wxpython' clause. Still I'm not very certain which version of wxpython I really need for my wxwidgets version.

tobac commented on 2018-05-08 09:27

Would you mind manually (i.e. by pressing M when yaourt presents upgradable packages) removing "python2-wxpython-phoenix" from the to-be-updated packages list and leaving "python-wxpython-phoenix"?

(Just for testing purposes; if a normal upgrade actually causes problems, this needs to be fixed within the package.)

nickoe commented on 2018-05-08 09:24

I am simply updating with yaourt -Syu --aur

tobac commented on 2018-05-08 09:09

@nickoe: Are you instructing yaourt to install "python-wxpythoen-phoenix" or "python2-wxpython-phoenix"? I'm suspecting the latter and if that's the case could you try "python-wxpython-phoenix" instead?

nickoe commented on 2018-05-07 15:49

I wonder why there is not a python3 with wxpython3.

I get this error while building Installing img2xpm script to /tmp/yaourt-tmp-nickoe/aur-python2-wxpython-phoenix/pkg/python-wxpython-phoenix/usr/bin chmod: cannot access '/tmp/yaourt-tmp-nickoe/aur-python2-wxpython-phoenix/pkg/python-wxpython-phoenix/usr/lib/python3.6/site-packages/wxPython-4.0.1-py3.6.egg-info/*': No such file or directory ==> ERROR: A failure occurred in package_python-wxpython-phoenix().

that is this package version 4.0.1-2

tobac commented on 2018-04-12 17:43

With the official 'python-wxpython' package shipping the Python 3 version of wxPython Phoenix, it probably makes sense to drop my 'python-wxpython-phoenix' and continue to maintain 'python2-wxpython-phoenix'. Any objections?

tobac commented on 2018-04-07 18:15

@ase1590: Done. I also added 'python-wxpython' into the 'provides' array, which makes the 'conflicts' entry probably somewhat redundant, but in my understanding doesn't hurt either. I chose this solution as 'fsleyes', one of my packages depending on 'python-wxpython-phoenix', won't start with the official 'python-wxpython'.

ase1590 commented on 2018-04-07 16:54

this needs to conflict with 'python-wxpython' now, as Wxpython 4.0 phoenix is now in the community repo.

tobac commented on 2018-03-22 13:23

Split packages can be confusing, yes. There is, in fact, just one PKGBUILD which will give you two packages: python-wxpython-phoenix and python2-wxpython-phoenix. The difference between the two packages is simply their name: the AUR (and the Arch Linux software management system, i.e. pacman) registers this split package as two packages even though their basis (i.e. the PKGBUILD file) is the same.

After building the package with makepkg, you're free to install just one of the resulting *pkg.tar.xz files.