Mailman 3 March 2007 - Pythonmac-SIG

py2app warning: may need to include email.Util
by Russell E Owen Aug. 6, 2007

Aug. 6, 2007

My py2app-bundled Mac application recently started failing with "no module named email.Util" when trying to display images. It turns out pyfits uses urllib which uses email.Util, which apparently has been renamed email.util with some kind of clever lazy import code so one can still use email.Util. Apparently the cleverness is too much for py2app's module finder. Anyway, the easy workaround is to specify email.Util as a necessary module to import. But I'll report a python bug or submit a urllib patch. -- Russell

5 6

Testing sqlite3 on python2.5
by Samuel M. Smith April 9, 2007

April 9, 2007

Anyone know how to verify that the sqlite3 bindings on Mac Python2.5 (macpackages installer) work or can access actual sqlite3? When I run the regression tests it works, but I don't know what they are testing. I am neophyte when it comes to sql. I am having problems getting roundup to work with the sqlite3 backend. It works with anydbm so I suspect my sqlite3 installation but don't know where to start. >>> import sqlite3 >>> import sqlite3.test.regression >>> sqlite3.test.regression.test() .... ---------------------------------------------------------------------- Ran 4 tests in 0.053s OK >>> does this mean that there is an sqlite3 backend ? ********************************************************************** Samuel M. Smith Ph.D. 2966 Fort Hill Road Eagle Mountain, Utah 84005-4108 801-768-2768 voice 801-768-2769 fax ********************************************************************** "The greatest source of failure and unhappiness in the world is giving up what we want most for what we want at the moment" **********************************************************************

4 12

Re: [Pythonmac-SIG] Macintosh modules/Carbon/documentation
by has April 2, 2007

April 2, 2007

Ronald Oussoren wrote: > One thing we (Jack and I) talked about is moving at least the > Carbon modules to its own separate project instead of being part of > the standard library. The most important reason for this is that > the Carbon modules and Python itself should be on a different > release schedule: the Carbon should track whatever Apple is doing > instead of having to wait until the next major release of Python > before new APIs can be added. Definitely. It also makes it harder to maintain the existing Carbon APIs, e.g. I ended up forking several Carbon extensions in order to fix and complete them for appscript, which isn't ideal. > A major stumbling block for that is that someone needs to step up > to commit to maintaining the thing. Furthermore, this stumbling block has a stumbling block of its own: bgen. There's very few folk around who understand it at all, and no documentation (AFAIK) for anyone else to make sense of it. Until there's some sort of decision made about bgen's future (maintain and document it? Replace it completely? Abandon it and maintain existing code by hand?), I can't see anyone really wanting to step into that tarpit. HTH has -- http://appscript.sourceforge.net http://rb-appscript.rubyforge.org http://appscript.sourceforge.net/objc-appscript.html

3 3

not mac related but OLPC
by Nehemiah Dacres April 2, 2007

April 2, 2007

I just wanted to tell you all about the One Laptop per Child Program in case any of you are interested in programming on a non mac and haven't heard of this yet. It is mostly programmed in python and most of the information is at laptop.org -- "lalalalala! it's not broken because I can use it" http://linux.slashdot.org/comments.pl?sid=194281&threshold=1&commentsort=0&…

2 1

Re: [Pythonmac-SIG] [ann] PyOSA 0.1.0, Appscript Installer 1.5.1 released
by has March 31, 2007

March 31, 2007

Jacob Rus wrote: > > For example, you could create a Mail rule that runs an 'AppleScript' > > action whenever new messages are received. > > Could someone make such an example script (or something similar), and > put it up somewhere? There is a very simple example script included with PyOSA that prints the arguments for the 'perform_mail_action_with_messages' call to stdout, which you can view in Console.app. > What happens when a specific handler is called on > that script? It presumably calls a python function of the same name. Yes. Top-level functions act as event handlers. A 'run' event calls the 'run' function, an 'open' event calls the 'open' function, a 'perform_mail_action_with_messages' event calls the 'perform_mail_action_with_messages' function, etc. (Events that don't have a human-readable name and user-defined subroutine calls are treated differently, however, so ask if you need to support those sorts of events.) > Is there some mapping of applescript handlers with named parameters to > python functions, etc.? It's the same as the mapping used by appscript commands, except that calls are going in the opposite direction, of course. If an event provides a direct parameter, that will be assigned to the first (i.e. positional) parameter of your function. Any keyword parameters are then assigned to function parameters of the same names. e.g. Mail's 'perform_mail_action_with_messages' event has the following dictionary definition: perform_mail_action_with_messages -- Script handler invoked by rules and menus that execute AppleScripts. The direct parameter of this handler is a list of messages being acted upon. list of message -- the message being acted upon [in_mailboxes mailbox] -- If the script is being executed by the user selecting an item in the scripts menu, this argument will specify the mailboxes that are currently selected. Otherwise it will not be specified. [for_rule rule] -- If the script is being executed by a rule action, this argument will be the rule being invoked. Otherwise it will not be specified. The corresponding event handler would be: def perform_mail_action_with_messages(messages, in_mailboxes, for_rule): ... The positional parameter's name can be anything you like (I used 'messages' here), just as long as doesn't match a keyword parameter name. One more thing: it's okay for an event handler to leave out parameters that it doesn't need. So you could also write: def perform_mail_action_with_messages(messages): ... def perform_mail_action_with_messages(in_mailboxes, for_rule): ... def perform_mail_action_with_messages(): ... and so on, depending on which parameters you're interested in. HTH has p.s. If anyone comes up with better scripts they'd like to share, please let me know. Help with improving the documentation would also be very welcome. -- http://appscript.sourceforge.net http://rb-appscript.rubyforge.org http://appscript.sourceforge.net/objc-appscript.html

1 0

[ann] PyOSA 0.1.0, Appscript Installer 1.5.1 released
by has March 31, 2007

March 31, 2007

Hi all, Announcing the first release of PyOSA, a new OSA language component for Python. PyOSA allows you to write Python scripts in Script Editor and attach them to OSA-enabled applications such as Mail (Mail Rules), iTunes (Scripts menu) and System Events (Folder Actions). PyOSA is very much a work-in-progress at this point, but it's already sufficiently advanced to allow both experimental and real-world use (caveat a few bugs and limitations). Comments, criticisms and suggestions for improvements are very welcome. Also released is Appscript Installer 1.5.1, containing binary installers for appscript 0.17.2. This update fixes several minor bugs and is recommended for all Appscript Installer 1.5/appscript 0.17.0 users. PyOSA and Appscript Installer are available for download at: http://appscript.sourceforge.net/download.html Enjoy! has -- http://appscript.sourceforge.net http://rb-appscript.rubyforge.org http://appscript.sourceforge.net/objc-appscript.html

5 8

Macintosh modules/Carbon/documentation
by Kevin Walzer March 31, 2007

March 31, 2007

Looking at the "Macintosh Library" documentation that ships with 2.5, I see a lot of outdated stuff: references to the old PythonIDE, PackageManager, and so on. What is the process for updating these docs, submitting a bug report, etc.? Also, there appears to be a lot of modules in the "Macintosh Library"--Carbon modules, generally--that are undocumented, or are broken, or (almost as bad) no one know if they work or not. Has anyone gone through these to sort out what works, what should be deprecated, etc.? Does it make sense to deprecate the entire Carbon module? What's the process for this? -- Kevin Walzer Code by Kevin http://www.codebykevin.com

4 4

py2app, eggs and entry points
by Nathan R. Yergler March 31, 2007

March 31, 2007

I have an application that I'd like to package using py2app, but I'm getting a little stuck with things. I *think* my problem is that my setup.py is fully setuptools-ized and my application script lives inside my package. Here's the call I make to setup(): setup(name='cclookup', version='2.0', url='http://wiki.creativecommons.org/CcLookup', author='Nathan R. Yergler', author_email='nathan(a)creativecommons.org', packages = ['cclookup', 'tagger', 'eyeD3'], setup_requires = setup_requirements, install_requires = ['setuptools', 'rdflib==2.3.3', 'ccrdf>=0.6a4', 'cctagutils>=0.5a1', 'rdfadict', ], include_package_data = True, zip_safe = False, entry_points = { 'console_scripts':['cclookup = cclookup:main'], }, app=['cclookup/app.py'], options={ "py2exe": {"packages": ["encodings", 'rdflib']}, "py2app": {"argv_emulation": True, "iconfile": os.path.join('cclookup', 'resources', 'cc.icns') } }, ) When I try to run this with py2app, it crashes into pdb complaining that it can't locate pkg_resources. Running the super-simplified version of setup.py generated by py2applet builds correctly, but has the following problems: * dependencies aren't included (I'm not sure if py2app actually attempts to scan for them like py2exe or not, so this may not be py2app's fault in the least) * app.py is included by itself, as opposed to as part of the package. I think that ideally I'd be able to specify my application as a gui_scripts entry point to setup(), and have it play nicely with the eggs specified in install_requires. I saw the docs mentioned that a future version would use eggs (I think it was in reference to recipes), and I was wondering what the status of that effort is. Thanks, Nathan

2 2

Re: [Pythonmac-SIG] Macintosh modules/Carbon/documentation
by has March 31, 2007

March 31, 2007

Jack Jansen wrote: > On 30-Mar-2007, at 22:55 , Kevin Walzer wrote: > >> Looking at the "Macintosh Library" documentation that ships with >> 2.5, I >> see a lot of outdated stuff: references to the old PythonIDE, >> PackageManager, and so on. What is the process for updating these >> docs, >> submitting a bug report, etc.? >> >> Also, there appears to be a lot of modules in the "Macintosh >> Library"--Carbon modules, generally--that are undocumented, or are >> broken, or (almost as bad) no one know if they work or not. Has >> anyone >> gone through these to sort out what works, what should be deprecated, >> etc.? Does it make sense to deprecate the entire Carbon module? >> What's >> the process for this? > > I had a chat about this with Ronald a few months ago, where we > basically went through all the modules. Ronald, > do you have your notes handy? We went over this issue last year as well (although nothing got done in time for 2.5's release). See the 'fixing the documentation' thread from April 2006. > Carbon itself should be fine. Well, it does have some technical problems. Most of the extensions haven't been adequately tested and debugged, and there are sometimes mapping errors in the auto-generated code. Also, having been created some time ago, the Carbon extension APIs may not have kept up with more recent changes to the system APIs. In addition, it's going to need an as-yet undetermined amount of work to support 64-bit Leopard. > It is indeed undocumented within the Python documentation, but the > transformation from the official Apple C documentation is pretty > clear (I think). Yeah, it takes a little getting used to, but it's mostly straightforward. The one thing which could be better explained is constructors as it's not obvious how to create new instances of Carbon types. Type instantiation follows Carbon, not Python, idioms, so instead of calling a type's constructor method, e.g. AEDesc(...), which doesn't work, you have to call a separate module function, e.g. AECreateDesc(...). My own position remains that the best thing for Python would be to junk many of the Mac-specific modules and move the rest, including Carbon, into a separate osxall package a-la win32all where it can be updated and maintained separately to the main Python framework. Easier said than done, of course, but perhaps the 64-bit problem will force the issue for 2.6? Cheers, has -- http://appscript.sourceforge.net http://rb-appscript.rubyforge.org http://appscript.sourceforge.net/objc-appscript.html

1 0

Re: [Pythonmac-SIG] Interesting use of Python and Django on the Mac
by has March 31, 2007

March 31, 2007

Jan Erik Moström wrote: >> Not sure it's what you're looking for, but are you aware of MoinX >> (http://moinx.antbear.org)? It's a Twisted-based wiki packaged as >> a standalone OS X app. Source is also available. > > Yep, but from what I understand it's would be the same as I set up > any wiki on my laptop, Which means that my laptop would need to > have connected to the net for allowing access from other computers. > > Unless I've misunderstood anything. Don't think so; it's probably me. So are you looking for some sort of client-server arrangement that allows you to take pages with you when you go offline, then update the original versions with your changes the next time you're online? Or are you after some kind of peer-to-peer thing? I did a quick search, but there doesn't seem to be much by way of options short of rolling up your sleeves and hacking an existing wiki to provide support. This looked the likeliest candidate: <http:// www.socialtext.com/node/152>. Or you might be able to cook up some sort of alternative solution using a collaborative text editor like SubEthaEdit, or a general CVS system like Subversion. HTH has -- http://appscript.sourceforge.net http://rb-appscript.rubyforge.org http://appscript.sourceforge.net/objc-appscript.html

1 0