🌐 Mailman 3 October 2010 - Pythonmac-SIG - python.org

Mac app store
by Kevin Walzer Oct. 21, 2010

Oct. 21, 2010

Well, I guess it should be no surprise that Apple's bringing the App Store to the Mac. The question is, what does it mean for Python developers? I saw a link to the app store guidelines here: http://pastie.org/1236378 If these are accurate, then I suppose Python apps that are wrapped via py2app wouldn't automatically be excluded. Java apps, however, are specifically excluded. (There are howls of protest on Apple's Java-dev list.) Of course, Apple isn't making the app store the only game in town, which is good. But as a developer of commercial desktop Mac apps in Python, I'm taking a careful look. --Kevin -- Kevin Walzer Code by Kevin http://www.codebykevin.com

1 0

New binary installers for Python 2.7 packages (retry)
by Russell E. Owen Oct. 20, 2010

Oct. 20, 2010

I have build several binary installers for the python.org 32-bit Python 2.7 (compatible with 10.3.9 and later): numpy 1.5.0 (see note 1) matplotlib 1.0.0 (but wx support is iffy; see note 2) PIL 1.1.7 pygame 1.9.1 They are available here: <http://www.astro.washington.edu/users/rowen/python/> Please test them and let me know if they work for you. So far I have tried them on 10.4 Intel (where I built them) and 10.5 Intel. I also ran code built from them on 10.3.9 PPC. Notes: 1) the numpy 1.5.0 binary installer that is served by the numpy folks does NOT work with 32-bit python 2.7. That is why I made a new installer. 2) I doubt matplotlib works with wxAgg because I used the wxPython binary installer for 2.7, and I fear it may only be compatible with 64-bit python. I only tested TkAgg. While we are going through the uncomfortable transition between 32-bit and 64-bit python (e.g. while we still support Mac OS X 10.4) it would really help if folks who make binary installers were explicit about which version of Python they are for (32-bit or 64-bit). -- Russell P.S. sorry if this is a duplicate. I didn't see my first attempt.

3 2

New binary installers for numpy, PIL and matplotlib for 32-bit python 2.7
by Russell E. Owen Oct. 19, 2010

Oct. 19, 2010

I have build three binary installers for the python.org 32-bit Python 2.7 (compatible with 10.3.9 and later): numpy 1.5.0 (see note 1) matplotlib 1.0.0 (see note 2) PIL 1.1.7 They are available here: <http://www.astro.washington.edu/users/rowen/python/> Please test them and let me know if they work for you. So far I have tried them on 10.4 Intel (where I built them) and 10.5 Intel. Notes: 1) the numpy 1.5.0 binary installer that is served by the numpy folks does NOT work with 32-bit python 2.7. That is why I made a new installer. 2) I doubt matplotlib works with wxAgg because I used the wxPython binary installer for 2.7, and I fear it may only be compatible with 64-bit python. I only tested TkAgg. If matplotlib does not work with wxAgg then does anyone know how hard it is to build wxPython from source? I've never tried it. While we are going through the uncomfortable transition between 32-bit and 64-bit python (e.g. while we still support Mac OS X 10.4) it would really help if folks who make binary installers were explicit about which version of Python they are for (32-bit or 64-bit). -- Russell

1 0

Advice on building binary installers for Python 2.7?
by Russell E. Owen Oct. 18, 2010

Oct. 18, 2010

I'd like to build binary installers for PIL and matplotlib for python.org Mac Python 2.7 but I confess I'm not sure how to go about it. As I understand it there are two flavors of Mac Python 2.7: a 32-bit build that is compatible with Mac OS X 10.3.9 and later and a 64-bit build that requires Mac OS X 10.5 or later. A complicating factor is that I have not figured out how to build matplotlib or PIL installers for Python 2.6 on 10.5 or 10.6 that were usable on 10.3.9 or 10.4. I built the libraries they depend on as static universal binaries but even so, it did not work. I ended up building everything on a Mac OS X 10.4 machine (which I have on long-term loan for that sole purpose). I think the following is true, but I'd be most grateful for corrections: - I'll need to make two installers per package, one for the 32-bit python, one for the 64-bit python. - 32-bit python 2.7 should be trivial: treat it exactly like Python 2.6. Build the installers on a Mac OS X 10.4 machine using the existing static libraries I already built and all should be well. - 64-bit python 2.7 is what I'm worried about. For building the dependent libraries do I have to use a particular gcc (e.g. 4.2 instead of 4.0)? What flags should I use? I'm guessing it would be safer to build on Mac OS X 10.5 than 10.6 (especially since the 10.6 XCode has some known issues -- components that were built incorrectly that cause warnings when one tries to build libraries). Any pointers to documentation or advice would be most appreciated. -- Russell P.S. The numpy folks apparently were able to make a single binary installer that works everywhere with both versions of Python 2.7. I'm not sure how they managed that, but perhaps numpy doesn't require bringing in any static libraries (if it uses the built in numeric libraries).

2 1

Fwd: [Twisted-Python] _twistd_unix.py / daemonize() / OSX / USING_FORK_WITHOUT_EXEC_IS_NOT_SUPPORTED_BY_FILE_MANAGER
by Erik van Blokland Oct. 13, 2010

Oct. 13, 2010

Begin forwarded message: > From: James Y Knight <foom(a)fuhm.net> > Date: October 13, 2010 7:20:20 PM GMT+02:00 > To: Twisted general discussion <twisted-python(a)twistedmatrix.com> > Subject: Re: [Twisted-Python] _twistd_unix.py / daemonize() / OSX / USING_FORK_WITHOUT_EXEC_IS_NOT_SUPPORTED_BY_FILE_MANAGER > Reply-To: Twisted general discussion <twisted-python(a)twistedmatrix.com> > > > On Oct 13, 2010, at 12:05 PM, Erik van Blokland wrote: > >> >> On Oct 13, 2010, at 5:52 PM, Phil Mayers wrote: >> >>> Other info indicates this is Apple trying to be clever and "protect" >>> applications from some signal handling issues surrounding fork() with >>> libraries which aren't safe in that situation; presumably these are >>> MacOS-specific libraries? >>> >>> If this really is true, then MacOS X is no longer posix-compliant in >>> those circumstances, and Twisted is going to need some work :o( >>> >>> Can you share more details about the application; the context in which >>> it is started, and which system libraries it's likely to load? >> >> Here's a compact version. The script uses OSX' Quartz to create and manipulate images. Twisted is used to wrap it as a webserver, images are served. More pointers on how to start and use it in the script itself. > > You need to avoid using or importing any OSX APIs until after the daemonization has occurred. Unfortunately, twisted executes the entire script file before daemonizing. [that's unfortunate for other reasons besides this, too] > > Here's a corrected version of your script which works properly. It defers importing Quartz until the reactor is running, by moving it into a function called by reactor.callWhenRunning(). > > _______________________________________________ > Twisted-Python mailing list > Twisted-Python(a)twistedmatrix.com > http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

1 0

Weird Carbon: gestalt: wxPython issue/bug
by Christopher Barker Oct. 13, 2010

Oct. 13, 2010

Hi folks, Peter Hanson, on the wxPython list, seems to have identified a bug in the gestalt module, that may be a Carbon issue. It's a bit of an unusual case: it freezes up wxPython, when wx is called from other than the main thread. Robin Dunn suspects that it's a Carbon issue -- gestalt is calling Carbon, and doing so in the main thread, so you are then trying to call Carbon from more than one thread, which may be the cause of the problem. I've confirmed that if you call gestalt from the same thread as wxPython, there is no failure. A link to Robin Dunn's assessment: http://permalink.gmane.org/gmane.comp.python.wxpython/76590 As Carbon is deprecated anyway, I guess it's time for gestalt ( or platform.mac_ver ) to be re-written I've tested on OS-X 10.4.11, Python 2.5 and Python2.6 Here is Peter's summary and sample code: # Demonstration of application freeze on OSX. # Running "python osx_freeze.py" shows the symptom: # non-responsiveness after about 3 seconds. In theory # this will occur in any wxPython app which runs # the GUI event loop in a thread other than the one # in which the failing gestalt('sysu') call (see below) # is first executed. # Enabling any of these imports can trigger the problem # as each one imports the next one down in the list. # This will happen only with pkg_resources v0.6c10 or later # although it's not pkg_resources' fault. # import matplotlib.figure # import matplotlib.axes # import matplotlib.dates # import pytz # import pkg_resources # The next import alone doesn't lead to failure, # but the function call does. # This same code is executed by pkg_resources starting # with setuptools v0.6c10. # from platform import mac_ver; mac_ver() # The platform.mac_ver() call does the following, which # is what ultimately leads to the failure. Calls # to gestalt() with 'sysa' (for example) do not # trigger the problem, either because the problem is # related to the 'sysu' itself, or to the fact that # an exception is raised because the selector "sysu" # is no longer recognized. from gestalt import gestalt try: print gestalt('sysu') except Exception, ex: print 'gestalt call failed' if __name__ == '__main__': def gui(): import wx app = wx.App(False) frame = wx.Frame(None) wx.StaticText(frame, label='Goodbye, cruel world') frame.Show() app.MainLoop() import threading threading.Thread(target=gui).start() -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chris.Barker(a)noaa.gov

5 14

Pygame and py2app 0.5.2
by Dan Ross Oct. 12, 2010

Oct. 12, 2010

Hi all- I'm getting the following error when trying to launch a bundled Pygame app: 10/4/10 8:43:42 PM [0x0-0x584584].org.pythonmac.unspecified.Cupcake[73356] ImportError: dlopen(/Users/danr/Projects/cupcake/dist/Cupcake.app/Contents/Resources/lib/python2.6/lib-dynload/pygame/base.so, 2): no suitable image found. Did find: 10/4/10 8:43:42 PM [0x0-0x584584].org.pythonmac.unspecified.Cupcake[73356] /Users/danr/Projects/cupcake/dist/Cupcake.app/Contents/Resources/lib/python2.6/lib-dynload/pygame/base.so: no matching architecture in universal wrapper The game launches fine from VIM or the command line. This had been working with an earlier version of py2app. I'm guessing it's a 32 vs 64 bit problem of some sort? Any direction would be appreciated. Thanks, Dan

2 2

Sending stdout/err to a text console in a py2app App
by Gregory Jefferis Oct. 12, 2010

Oct. 12, 2010

Hello, I've made a simple python script to wrap a complex, long running shell script using easygui. Then I've used py2app to make a Mac Application. I'm happy except I would really like stdout/stderr from both my python wrapper script and the original shell script to be visible as the shell script runs. If I run the app from the Terminal that happens. But if I double click, everything gets sent to the system logs (which can be inspected with Console.app). Is there anyway I can send anything useful to that empty console windows that appears when I start the py2app ? Or a simple way to make a new console to which I can print. Thank you very much for any help you can offer, Greg. Python 2.5 (r25:51918, Sep 19 2006, 08:49:13) [GCC 4.0.1 (Apple Computer, Inc. build 5341)] on darwin MacOSX 10.5.8 intel -- Gregory Jefferis, PhD Division of Neurobiology MRC Laboratory of Molecular Biology, Hills Road, Cambridge, CB2 0QH, UK. http://www2.mrc-lmb.cam.ac.uk/group-leaders/h-to-m/g-jefferis http://www.neuroscience.cam.ac.uk/directory/profile.php?gsxej2 http://flybrain.stanford.edu

3 5

Creating environment to build re-distributable app
by Antonio Goméz Soto Oct. 12, 2010

Oct. 12, 2010

Hi I am new to this list. I have a Windows/Linux developed wxPython program that I need to create a OSX version for that runs on various OSX platforms. I modified the app to run on OSX from my source directory, and now it runs correctly from there (I use Snow Leopard). I have forced the OSX supplied Python to run in 32-bit using VERSIONER_PYTHON_PREFER_32_BIT=yes, because some of my modules require that, and I can't fix those. I use appscript, twisted, and plan to use WebKit, which appararently only runs 32-bit. I am playing with py2app to create a bundle of my app, but I run into problems: 1. py2app seems to work, but the created app seems to run in 64-bit even if I do the 'defaults write com.apple.versioner.python Prefer-32-Bit -bool yes' command. I get the 'module' object has no attribute TickCount error, which according to Google means I am running in 64-bit mode. 2. I read on this list that I should not use the Apple-supplied Python, because py2app is setup to NOT include that in the build, and this way I cannot distribute my app. the posting said to build python2.6 from python.org, install all my modules, and work from there. 3. I have had bad experience so far building WebKit, because I used macports to get git, and that apparently took over my build environment, and that's why building WebKit failed. I am afraid macports is getting in the way here too. So what is the best way to handle this? Thanks, Antonio.

2 1

Py2app problem
by Sam Nearhood Oct. 12, 2010

Oct. 12, 2010

I am trying to build a program with py2app ($ python setup.py py2app) using Mac OS X 10.6.4 and Python 2.7. Right after it finishes bundling the application, the terminal stops with this output: Traceback (most recent call last): File "/Users/sam/Desktop/Program/py2app-0.5.2-py2.7.egg/py2app/build_app.py", line 604, in _run self.run_normal() File "/Users/sam/Desktop/Program/py2app-0.5.2-py2.7.egg/py2app/build_app.py", line 675, in run_normal self.create_binaries(py_files, pkgdirs, extensions, loader_files) File "/Users/sam/Desktop/Program/py2app-0.5.2-py2.7.egg/py2app/build_app.py", line 772, in create_binaries target, arcname, pkgexts, copyexts, target.script) File "/Users/sam/Desktop/Program/py2app-0.5.2-py2.7.egg/py2app/build_app.py", line 1215, in build_executable copy_resource(src, dest, dry_run=self.dry_run) File "/Users/sam/Desktop/Program/py2app-0.5.2-py2.7.egg/py2app/util.py", line 96, in copy_resource copy_file(source, destination, dry_run=dry_run) File "/Users/sam/Desktop/Program/py2app-0.5.2-py2.7.egg/py2app/util.py", line 101, in copy_file zf, zp = path_to_zip(source) File "/Users/sam/Desktop/Program/py2app-0.5.2-py2.7.egg/py2app/util.py", line 133, in path_to_zip raise DistutilsFileError(path) DistutilsFileError: / > /Users/sam/Desktop/Program/py2app-0.5.2-py2.7.egg/py2app/util.py(133)path_to_zip() -> raise DistutilsFileError(path) (Pdb) I can't seem to find this problem answered elsewhere. Does anybody have any suggestions? Thanks, Sam

2 2