I’ve used wxPython in a small way on and off over the last few years. Not having used it for a while, and having changed computers some time ago, I recently had cause to reinstall the Docs/Demo on a couple of systems, one 32-bit Win7, the other 64-bit Win7. The installation worked fine in both cases with one exception. On the 64-bit system, no entries were created in the Windows Start Menu. I’m using Python 2.7.5 on the 32-bit system, 2.7.3 on the 64-bit system and wxPython2.8-win32-unicode-2.8.12.1-py27 and the same version of the docs. A search of the forum didn’t give me any hits for this issue.
Go to your program files where the app was installed, create a shortcut to demo.py or whatever you want in your startmenu and place that shortcut in you startmenu dir. It should show up then. You might have to log off log in to get them to show up.
If not, then report back with specifics.
···
On Monday, November 18, 2013 4:29:12 AM UTC-6, raichea wrote:
I’ve used wxPython in a small way on and off over the last few years. Not having used it for a while, and having changed computers some time ago, I recently had cause to reinstall the Docs/Demo on a couple of systems, one 32-bit Win7, the other 64-bit Win7. The installation worked fine in both cases with one exception. On the 64-bit system, no entries were created in the Windows Start Menu. I’m using Python 2.7.5 on the 32-bit system, 2.7.3 on the 64-bit system and wxPython2.8-win32-unicode-2.8.12.1-py27 and the same version of the docs. A search of the forum didn’t give me any hits for this issue.
I did that when reinstalling a second time didn’t fix the problem. I can access the demo and docs OK from these manually-created shortcuts, so not a problem for me, as such. Just wanted to flag that there seems to be an issue installing on 64-bit systems. There is a docs/demo entry in Control Panel/Remove Programs, so it does just seem to be creation of shortcuts that’s going wrong.
I've used wxPython in a small way on and off over the last few years.
Not having used it for a while, and having changed computers some time
ago, I recently had cause to reinstall the Docs/Demo on a couple of
systems, one 32-bit Win7, the other 64-bit Win7. The installation
worked fine in both cases with one exception. On the 64-bit system, no
entries were created in the Windows Start Menu. I'm using Python 2.7.5
on the 32-bit system, 2.7.3 on the 64-bit system and
wxPython2.8-win32-unicode-2.8.12.1-py27 and the same version of the
docs. A search of the forum didn't give me any hits for this issue.
I am on 64bit Windows 7 with Python 2.7.5 32bit and wxPython and if I use search in the start menu I see both demos 2.8 and 2.9.
BTW, you might want to go with 2.9.5 as there are lots of new things and just in case that the .9. is an issue for you you might want to read ReleaseSeries - wxPyWiki
Just to verify… What wx.version() are you using Exactly? Post the output of print(wx.version()) if unsure.
2.8.9 or 2.8.12 or other…?
···
On Tuesday, November 19, 2013 2:19:23 AM UTC-6, raichea wrote:
I did that when reinstalling a second time didn’t fix the problem. I can access the demo and docs OK from these manually-created shortcuts, so not a problem for me, as such. Just wanted to flag that there seems to be an issue installing on 64-bit systems. There is a docs/demo entry in Control Panel/Remove Programs, so it does just seem to be creation of shortcuts that’s going wrong.
Thanks Werner… I’ve no objection to upgrading, but didn’t feel the need to… I doubt it’s a Python version bug, though… and I’ve got the latest wxPython.
2.8.12 is a very old (2011) wxPython version;-) , the latest is 2.9.5, I know it is labelled as dev release that is the reason to point you to ReleaseSeries - wxPyWiki
I use the 2.9.x series for a long time now and there are quite a few others who do too, you might want to give it a try, if you do check the 'CHANGES.html'
Werner
···
On 20/11/2013 00:15, raichea wrote:
Thanks Werner... I've no objection to upgrading, but didn't feel the
need to... I doubt it's a Python version bug, though... and I've got
the latest wxPython.
My only concern to use the 2.9 series is: its not comming by default or could be easily installed from repos in all (?) of the major Linux distributions, in Ubuntu for example need compilation.
That avoid me to create a software using that version, because the normal user cant compile it. Very easy to said is: “requirements are: wxPython 2.8.x…” users only need to install it from repos and can start using my software.
Anyways Ubuntu plans move to Python 3 next year, any ideas when the 2.9 branch could be “stable”?
Thanks Werner… I’ve no objection to upgrading, but didn’t feel the
need to… I doubt it’s a Python version bug, though… and I’ve got
the latest wxPython.
2.8.12 is a very old (2011) wxPython version;-) , the latest is 2.9.5, I know it is labelled as dev release that is the reason to point you to http://wiki.wxpython.org/ReleaseSeries
I use the 2.9.x series for a long time now and there are quite a few others who do too, you might want to give it a try, if you do check the ‘CHANGES.html’
Werner
–
You received this message because you are subscribed to the Google Groups “wxPython-users” group.
My only concern to use the 2.9 series is: its not comming by default or could be easily installed from repos in all (?) of the major Linux distributions, in Ubuntu for example need compilation.
Good point, I don't think Robin maintains what is in the Linux repos, any way of pinging the people to get 2.9.x maybe not as default but at least as an option.
That avoid me to create a software using that version, because the normal user cant compile it. Very easy to said is: "requirements are: wxPython 2.8.x.." users only need to install it from repos and can start using my software.
I am still only distributing on Windows and there I use py2exe to make sure that user uses/gets the correct dependencies.
Anyways Ubuntu plans move to Python 3 next year, any ideas when the 2.9 branch could be "stable"?
Robin might know;-) , for a while now the snapshots for Phoenix uses wxWidget 3.0 and has Py3.x snapshots - also help is needed (e.g. ensuring that the wx.lib stuff is working on both py2x and py3x) to get this to a point where it is usable.
Who knows, maybe someone added it to the xmas list:-) .