only wxPython Phoenix will run on Python 3, but not that it is still
in development.
Oh, I understand now why the examples weren't complete and that it might
take time to release.
Thanks for the link, I'm gonna install V.3.n.n-dev
Just one more question: I see on this link that pip & setuptools should
be at least in versions 6.0.8 & 12.0.5; as debian has the annoying habit
to use its own versioning, is it ok with stable? (or at least, jessie,
the next stable to come?)
…
objectlistview you should be able to install with pip/pip3 too, the
others you need to check their sites.
Thanks, but I'm now turning myself toward a wx.Grid that should
better suit my needs.
Jean-Yves
···
On Thu, 05 Mar 2015 09:54:36 +0100 Werner <wernerfbd@gmx.ch> wrote:
On Thu, Mar 05, 2015 at 02:51:35PM +0100, Bzzzz wrote:
Just one more question: I see on this link that pip & setuptools should
be at least in versions 6.0.8 & 12.0.5; as debian has the annoying habit
to use its own versioning
I mean the version that appears into dselect or synaptic (that is:
5.5.1-1 ≠ 12.2-1 & 1.5.6-5).
From what you wrote, I see setuptools is ok (≥ 12.0.5), but not pip
(≥ 6.0.8) (?)
BTW, which command did you use to get those results?
JY
···
On Thu, 5 Mar 2015 15:02:36 +0100 Karsten Hilbert <Karsten.Hilbert@gmx.net> wrote:
Following your link and Karsten information, I purged python-pip &
python-setuptools, then used get-pip.py to manually install both
from the latest version.
Unfortunately, it failed with cryptic messages:
Command
'"/usr/bin/python" /tmp/pip-build-9eJjQO/wxPython-Phoenix/bin/waf-1.7.15-p1
--wx_config=/tmp/pip-build-9eJjQO/wxPython-Phoenix/build/wxbld/wx-config
--python="/usr/bin/python" --out=build/waf/2.7 configure build '
failed with exit code 1. Finished command: build_py (8m24.239s)
Finished command: build (16m0.579s)
WARNING: Building this way assumes that all generated files have been
generated already. If that is not the case then use build.py
directly
to generate the source and perform the build stage. You can use
--skip-build with the bdist_* or install commands to avoid this
message and the wxWidgets and Phoenix build steps in the future.
/usr/bin/python -u build.py build
Command '/usr/bin/python -u build.py build' failed with exit code 1.
···
On Thu, 05 Mar 2015 09:54:36 +0100 Werner <wernerfbd@gmx.ch> wrote:
In /tmp I just have: pip_build_root that contains a placeholder; so I'm
a bit lost at this point. (I did not purged wx2.8 pkgs, may be it is
the problem (?))
If you did then some Linux guru will have to help.
Arrgghhh! (I feel like murdering a cute kitten with a rusty chainsaw;)
Hmm, first, I made a mistake, using pip & setuptools from pkgs, they were
a lot more verbose; is there a way to make the tarball pip report many
more and keep the wx3.n-dev tarball files into /tmp/pipxxx to try to
analyse what is wrong?
JY
···
On Thu, 05 Mar 2015 17:19:29 +0100 Werner <wernerfbd@gmx.ch> wrote:
Did you install the requirements listed on the above page?
Yep, I followed this howto literally.
If you did then some Linux guru will have to help.
Arrgghhh! (I feel like murdering a cute kitten with a rusty chainsaw;)
Hmm, first, I made a mistake, using pip& setuptools from pkgs, they were
a lot more verbose; is there a way to make the tarball pip report many
more and keep the wx3.n-dev tarball files into /tmp/pipxxx to try to
analyse what is wrong?
I always recommend that when working with Phoenix that people use virtualenv or pyvenv to make a clean and empty Python environment. Then you can install things like the latest pip and setuptools without worry that you may upset the system installed Python. Then you just need to activate that environment and make sure that the Python and other tools you run are coming from the venv's bin folder.
As for the build problems, I would have expected that there would be more output than that, but maybe pip is capturing or suppressing it. Either way it would be good to try building it yourself so you can take smaller steps and maybe get more clues about where the problem may be. If you download the source tarball then you can either use standard setup.py commands, or you can use the build.py tool to break up the build process even more. If you use git to fetch the source then you'll need to use build.py and have it also run the steps that generate the code. There are some how-to details in the README file and also some recent conversations on wxPython-dev.
Keep in mind that the build tools will also build wxWidgets by default, as this is the best way to ensure that the correct version is being used. That may change once there are official releases, but for now your wxPython-Phoenix build will have its own private copy of the wxWidgets libs. This is also a possible point of failure if you do not have required -dev packages installed, so watch the output when it runs wxWidgets' configure script to see if it is turning features off that you don't expect it to.
···
On Thu, 05 Mar 2015 17:19:29 +0100 > Werner<wernerfbd@gmx.ch> wrote:
