Hi all,
Subject says it all really. Did someone try already?
Thanks, Frank
My boss said he tried the 64-bit build of our program on Lion this morning and it appeared to run fine (it was compiled on Snow Leopard). We’re using Python 2.7.2, wxPython 2.9.1 (Cocoa version) for this; I haven’t checked whether the 32-bit build using 2.8.12 (and compiled on Tiger) also works.
-Nat
···
On Thu, Jul 21, 2011 at 1:27 PM, Frank Niessink frank@niessink.com wrote:
Subject says it all really. Did someone try already?
Is it possible to use wxPython2.9-osx-2.9.1.1-cocoa-py2.7.dmg from the site? I’m wondering because winpdb isn’t able to find wxPython on my Lion installation. It gives me this error:
wxPython was not found.
wxPython 2.6 or higher is required to run the winpdb GUI.
(I haven’t used either wxPython or winpdb previously so please don’t shoot me.)
Are you using the Python provided by Apple or the one from python.org? I did some hackery to be able to get one wxPython install to work with both Apple's Py26 and Python.org's Py26 on 10.5 and 10.6, but I would not be surprised if Apple changed something in how they do their install and import paths which causes my hackery to break. Try installing and using Python.org's Python 2.7 instead. If you've already done that then I'm not sure what the problem could be and will need more information to be able to make my shots in the dark more accurate. (I don't have a 10.7 machine yet.)
···
On 7/23/11 12:36 PM, jmagnusson wrote:
Is it possible to use wxPython2.9-osx-2.9.1.1-cocoa-py2.7.dmg from the
site? I'm wondering because winpdb isn't able to find wxPython on my
Lion installation. It gives me this error:wxPython was not found.
wxPython 2.6 or higher is required to run the winpdb GUI.
(I haven't used either wxPython or winpdb previously so please don't
shoot me.)
--
Robin Dunn
Software Craftsman
I installed Lion and Python 2.7 plus wxPython 2.8.12.0 work fine.
Thanks, Frank
···
2011/7/21 Nat Echols <nathaniel.echols@gmail.com>:
On Thu, Jul 21, 2011 at 1:27 PM, Frank Niessink <frank@niessink.com> wrote:
Subject says it all really. Did someone try already?
My boss said he tried the 64-bit build of our program on Lion this morning
and it appeared to run fine (it was compiled on Snow Leopard). We're using
Python 2.7.2, wxPython 2.9.1 (Cocoa version) for this; I haven't checked
whether the 32-bit build using 2.8.12 (and compiled on Tiger) also works.
I get the following warning when a wx.TextCtrl is drawn:
CFURLCreateWithString was passed this invalid URL string: '/System/
Library/CoreServices/CommonCocoaPanels.bundle' (a file system path
instead of an URL string). The URL created will not work with most
file URL functions. CFURLCreateWithFileSystemPath or
CFURLCreateWithFileSystemPathRelativeToBase should be used instead.
The control draws but the warning is printed.
Craig
I see that too while running the unittests for Task Coach. Funny thing
is that I see it only once, though we have over 4400 unittests. I'm
pretty sure we have more than one unittest that draws a TextCtrl 
Maybe some initialization issue?
Cheers, Frank
···
2011/7/24 Craig <cahoward@earthlink.net>:
I get the following warning when a wx.TextCtrl is drawn:
CFURLCreateWithString was passed this invalid URL string: '/System/
Library/CoreServices/CommonCocoaPanels.bundle' (a file system path
instead of an URL string). The URL created will not work with most
file URL functions. CFURLCreateWithFileSystemPath or
CFURLCreateWithFileSystemPathRelativeToBase should be used instead.The control draws but the warning is printed.
Me too; just once, and it happens very, very early.
···
On Jul 24, 2:42 pm, Frank Niessink <fr...@niessink.com> wrote:
2011/7/24 Craig <cahow...@earthlink.net>:
> I get the following warning when a wx.TextCtrl is drawn:
> CFURLCreateWithString was passed this invalid URL string: '/System/
> Library/CoreServices/CommonCocoaPanels.bundle' (a file system path
> instead of an URL string). The URL created will not work with most
> file URL functions. CFURLCreateWithFileSystemPath or
> CFURLCreateWithFileSystemPathRelativeToBase should be used instead.> The control draws but the warning is printed.
I see that too while running the unittests for Task Coach. Funny thing
is that I see it only once, though we have over 4400 unittests. I'm
pretty sure we have more than one unittest that draws a TextCtrl
Maybe some initialization issue?Cheers, Frank