Will announce beyond this group in a day or two.
Long life wxPython !!!
···
Le 16/04/2017 à 04:32, Robin Dunn a écrit :
Will announce beyond this group in a day or two.
--
Robin Dunn
Software Craftsman
http://wxPython.org
--
You received this message because you are subscribed to the Google Groups "wxPython-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wxPython-dev+unsubscribe@googlegroups.com <mailto:wxPython-dev+unsubscribe@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.
Thanks especially Robin for the main work and maintenance of wxPython!
But also all others that support this version with bugfixes or patches!
Thanks for this, Robin!
To keep using latest snapshots, should we use the old magic handshake:
pip download \
–pre \
–trusted-host wxpython.org \
–find-links http://wxpython.org/Phoenix/snapshot-builds/ \
wxPython_Phoenix
or grab the latest pypi wheel for the 4.0 installer?
pip download wxPython
···
On Sat, Apr 15, 2017 at 7:32 PM, Robin Dunn robin@alldunn.com wrote:
–
Robin DunnSoftware Craftsman
https://pypi.python.org/pypi/wxPython/4.0.0a1
Will announce beyond this group in a day or two.
–
You received this message because you are subscribed to the Google Groups “wxPython-dev” group.
To unsubscribe from this group and stop receiving emails from it, send an email to wxPython-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Eric Fahlgren wrote:
Thanks
for this, Robin!
To keep using latest snapshots, should we use the old magic handshake:
pip download \
–pre \
–trusted-host wxpython.org
\
–find-links http://wxpython.org/Phoenix/snapshot-builds/
\
wxPython_Phoenix
or grab the latest pypi wheel for the 4.0 installer?
pip download wxPython
Only releases will be going to PyPI. Snapshots will still be uploaded to
wxPython.org on days when changes are committed to the master branch. However the name on the snapshots will be changing to “wxPython” now that Phoenix is official, also it’s no longer necessary to use the --trusted-host flag since https is supported on the server. So something
like this should work to get the snapshots going forward:
pip install --pre --find-links wxPython
Hi,
Im running Ubuntu can I have installed both versions of wxPython? :
Python 2.x-> wxPython
Python 3.x-> Phoenix
···
2017-04-16 20:49 GMT-05:00 Robin Dunn robin@alldunn.com:
Eric Fahlgren wrote:
Thanks
for this, Robin!
To keep using latest snapshots, should we use the old magic handshake:
pip download \
–pre \
–trusted-host wxpython.org
\
–find-links http://wxpython.org/Phoenix/snapshot-builds/
\
wxPython_Phoenix
or grab the latest pypi wheel for the 4.0 installer?
pip download wxPython
Only releases will be going to PyPI. Snapshots will still be uploaded to
wxPython.org on days when changes are committed to the master branch. However the name on the snapshots will be changing to “wxPython” now that Phoenix is official, also it’s no longer necessary to use the --trusted-host flag since https is supported on the server. So something
like this should work to get the snapshots going forward:pip install --pre --find-links http://wxpython.org/Phoenix/snapshot-builds/ wxPython
–
Robin DunnSoftware Craftsman
–
You received this message because you are subscribed to the Google Groups “wxPython-dev” group.
To unsubscribe from this group and stop receiving emails from it, send an email to wxPython-dev+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
Hi Robin,
First, congratulations on this milestone. I’m happy to report that NonVisual Desktop Access (www.nvaccess.org) has been ported to wxPython 4:
https://github.com/nvaccess/nvda/issues/7077
One question: will you be hosting a .pdb for Phoenix builds somewhere? If so, let us know where, otherwise NV Access plans to build wxPython so we can have debug symbols. Thanks.
Cheers,
Joseph
···
From: wxpython-dev@googlegroups.com [mailto:wxpython-dev@googlegroups.com] On Behalf Of Robin Dunn
Sent: Sunday, April 16, 2017 6:49 PM
To: wxPython-dev@googlegroups.com
Subject: Re: [wxPython-dev] TaDAAA!!!
Eric Fahlgren wrote:
Thanks for this, Robin!
To keep using latest snapshots, should we use the old magic handshake:
pip download \
–pre \
–trusted-host wxpython.org \
–find-links http://wxpython.org/Phoenix/snapshot-builds/ \
wxPython_Phoenix
or grab the latest pypi wheel for the 4.0 installer?
pip download wxPython
Only releases will be going to PyPI. Snapshots will still be uploaded to wxPython.org on days when changes are committed to the master branch. However the name on the snapshots will be changing to “wxPython” now that Phoenix is official, also it’s no longer necessary to use the --trusted-host flag since https is supported on the server. So something like this should work to get the snapshots going forward:
pip install --pre --find-links http://wxpython.org/Phoenix/snapshot-builds/ wxPython
–
Robin Dunn
Software Craftsman
http://wxPython.org
–
You received this message because you are subscribed to the Google Groups “wxPython-dev” group.
To unsubscribe from this group and stop receiving emails from it, send an email to wxPython-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
thank you Robin!
Just one note: if I “pip install wxPython” I get the tar.gz instead of the wheel package. Shouldn’t pip get the whl when it exists?
(virtualenv on python2.7,win7)
Yes, I do that on my (windows) development machine. The trick is to delete (or rename) the installation info that 3.0 puts in site-packages before you install 4.0, or pip will remove the 3.0 installation.
cd python/lib/site-packages
pip install …3.0…
rm wxPython-3.0.2.0.dist-info
pip install …4.0…
mkdir wxPhoenix
mv wx wxPhoenix
Now we have two parallel installations in site-packages:
lib/site-packages/
wx-3.0-msw (“msw” because this is windows, your’s will be different on Ubuntu)
wx
wxPhoenix
wx
I then hack up site-packages/wx.pth so it looks like this:
import site ; sp = site.getsitepackages()[-1]
import os ; cwd = os.getcwd()
import sys ; sys.path.append(sp+os.sep+ (“wxPhoenix” if “wxUpdate” in cwd else “wx-3.0-msw”))
So in my “wxUpdate” workspace, it automatically switches to wxPhoenix and “import wx” gets 4.0 instead of 3.0.
···
On Sun, Apr 16, 2017 at 8:13 PM, Mario Lacunza mlacunza@gmail.com wrote:
Hi,
Im running Ubuntu can I have installed both versions of wxPython? :
Python 2.x-> wxPython
Python 3.x-> Phoenix
–
You received this message because you are subscribed to the Google Groups “wxPython-dev” group.
To unsubscribe from this group and stop receiving emails from it, send an email to wxPython-dev+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
2017-04-16 20:49 GMT-05:00 Robin Dunn robin@alldunn.com:
Eric Fahlgren wrote:
Thanks
for this, Robin!
To keep using latest snapshots, should we use the old magic handshake:
pip download \
–pre \
–trusted-host wxpython.org
\
–find-links http://wxpython.org/Phoenix/snapshot-builds/
\
wxPython_Phoenix
or grab the latest pypi wheel for the 4.0 installer?
pip download wxPython
Only releases will be going to PyPI. Snapshots will still be uploaded to
wxPython.org on days when changes are committed to the master branch. However the name on the snapshots will be changing to “wxPython” now that Phoenix is official, also it’s no longer necessary to use the --trusted-host flag since https is supported on the server. So something
like this should work to get the snapshots going forward:pip install --pre --find-links http://wxpython.org/Phoenix/snapshot-builds/ wxPython
–
Robin DunnSoftware Craftsman
–
You received this message because you are subscribed to the Google Groups “wxPython-dev” group.
To unsubscribe from this group and stop receiving emails from it, send an email to wxPython-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Marco Prosperi wrote:
thank you Robin!
Just one note: if I "pip install wxPython" I get the tar.gz instead of
the wheel package. Shouldn't pip get the whl when it exists?(virtualenv on python2.7,win7)
Is your Python a stock Python from Python.org or some other build? If
it's a custom build then it's possible that something has been changed
such that pip doesn't think that the binary wheels on PiPI are
compatible with your Python.
···
--
Robin Dunn
Software Craftsman
Eric Fahlgren wrote:
Yes,
I do that on my (windows) development machine. The trick is to delete (or rename) the installation info that 3.0 puts in site-packages before you install 4.0, or pip will remove the 3.0 installation.
cd python/lib/site-packages
pip install …3.0…
rm wxPython-3.0.2.0.dist-info
pip install …4.0…
mkdir wxPhoenix
mv wx wxPhoenix
Now we have two parallel installations in site-packages:
lib/site-packages/
wx-3.0-msw (“msw” because this is windows, your’s will be different on Ubuntu)
wx
wxPhoenix
wx
I then hack up site-packages/wx.pth so it looks like this:
import site ; sp = site.getsitepackages()[-1]
import os ; cwd = os.getcwd()
import sys ; sys.path.append(sp+os.sep+ (“wxPhoenix” if “wxUpdate” in cwd else “wx-3.0-msw”))
So in my “wxUpdate” workspace, it automatically switches to wxPhoenix and “import wx” gets 4.0 instead of 3.0.
Much easier IMO is to use virtual environments for any project that will
be using Phoenix. Then pip takes care of everything for you and you do not have to perform surgery on your main Python installs.
Hi
Robin,
First,
congratulations on this milestone. I’m happy to report that NonVisual Desktop Access (www.nvaccess.org )
has been ported to wxPython 4:
https://github.com/nvaccess/nvda/issues/7077
One question: will you be hosting a .pdb for Phoenix builds somewhere? If so, let us know where, otherwise NV Access plans to build wxPython so we can have debug symbols. Thanks.
Mario Lacunza wrote:
Hi,
Im running Ubuntu can I have installed both versions of wxPython? :
Python 2.x-> wxPython
Python 3.x-> Phoenix
I haven't checked yet if there are any overlapping files with stock
system packages vs the Phoenix wheels, but if you use virtual
environments for your projects it won't matter. You can even have a
different wxPython (Classic, official Phoenix, Phoenix snapshots, etc.)
in each virtual environment if you needed it.
···
--
Robin Dunn
Software Craftsman
Robin Dunn wrote:
Much easier IMO is to use virtual environments for any project that will
be using Phoenix. Then pip takes care of everything for you and you do not have to perform surgery on your main Python installs.
BTW, I made a little utility for my own use to make it easy to switch between multiple full python installs and/or python virtual environments. There are a few other ways to do things like this too, but
this one works well for me. On Windows it requires a bash shell (only tested on cygwin but others may work too.)
Each of my machines has an average of a dozen or so Python environments (either full or virtual) and this tool makes it quick and easy to switch
which environment will be used from the current command line. Another benefit of relying on virtual environments is that my stock Python’s don’t need to have anything installed in them except for whatever is needed for creating virtual environments. This helps keep them uncluttered and eliminates dependency mismatches when one project needs version A of something and another project needs version B.
Thanks for the answers! and congratulations for this long expected release!
···
2017-04-17 11:52 GMT-05:00 Robin Dunn robin@alldunn.com:
Mario Lacunza wrote:
Hi,
Im running Ubuntu can I have installed both versions of wxPython? :
Python 2.x-> wxPython
Python 3.x-> Phoenix
I haven’t checked yet if there are any overlapping files with stock
system packages vs the Phoenix wheels, but if you use virtual
environments for your projects it won’t matter. You can even have a
different wxPython (Classic, official Phoenix, Phoenix snapshots, etc.)
in each virtual environment if you needed it.
–
Robin Dunn
Software Craftsman
–
You received this message because you are subscribed to the Google Groups “wxPython-dev” group.
To unsubscribe from this group and stop receiving emails from it, send an email to wxPython-dev+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
it’s from a python.org installer. It happens only if I install in a virtual environment on my machine. No problem if I pip install from the main environment: in this case *.whl is collected
···
On Monday, April 17, 2017 at 6:51:45 PM UTC+2, Robin Dunn wrote:
Marco Prosperi wrote:
thank you Robin!
Just one note: if I “pip install wxPython” I get the tar.gz instead of
the wheel package. Shouldn’t pip get the whl when it exists?
(virtualenv on python2.7,win7)
Is your Python a stock Python from Python.org or some other build? If
it’s a custom build then it’s possible that something has been changed
such that pip doesn’t think that the binary wheels on PiPI are
compatible with your Python.
–
Robin DunnSoftware Craftsman
Marco Prosperi wrote:
it’s from a python.org installer. It happens only if I install in a virtual environment on my machine. No problem if I pip
install from the main environment: in this case *.whl is collected
It worked for me, so I’m not sure what to suggest other than making sure
your virtualenv package is up to date and trying with a new, empty virtual environment.
virtualenv .myPyEnv/temp27
wrangler temp27
(temp27) > python -c “import sys; print(sys.version)”
2.7.12 (v2.7.12:d33e0cf91556, Jun 27 2016, 15:19:22) [MSC v.1500 32 bit (Intel)]
(temp27) > pip install wxPython
Collecting wxPython
Using cached wxPython-4.0.0a1-cp27-cp27m-win32.whl
Requirement already satisfied: six in c:\users\robind\home.mypyenv\temp27\lib\site-packages (from wxPython)
Installing collected packages: wxPython
Successfully installed wxPython-4.0.0a1
Robin Dunn wrote:
Marco Prosperi wrote:
it’s from a python.org installer. It happens only if I install in a virtual environment on my machine. No problem if I pip
install from the main environment: in this case *.whl is collected
It worked for me, so I’m not sure what to suggest other than making sure
your virtualenv package is up to date and trying with a new, empty virtual environment.virtualenv .myPyEnv/temp27
wrangler temp27
(temp27) > python -c “import sys; print(sys.version)”
2.7.12 (v2.7.12:d33e0cf91556, Jun 27 2016, 15:19:22) [MSC v.1500 32 bit (Intel)]
(temp27) > pip install wxPython
Collecting wxPython
Using cached wxPython-4.0.0a1-cp27-cp27m-win32.whl
Requirement already satisfied: six in c:\users\robind\home.mypyenv\temp27\lib\site-packages (from wxPython)
Installing collected packages: wxPython
Successfully installed wxPython-4.0.0a1
I just noticed that the example above pulled from the local cache so just to be sure I recreated the venv and tried again with --no-chache-dir and pip still fetched and installed the wheel in the virtual environment.
(temp27) > pip --no-cache-dir install wxPython
Collecting wxPython
Downloading wxPython-4.0.0a1-cp27-cp27m-win32.whl (11.9MB)
100% |################################| 11.9MB 10.2MB/s
Requirement already satisfied: six in c:\users\robind\home.mypyenv\temp27\lib\site-packages (from wxPython)
Installing collected packages: wxPython
Successfully installed wxPython-4.0.0a1