🌐 Mailman 3 February 2006 - Pythonmac-SIG - python.org

Drag and drop apps?
by Ken Brooks Feb. 13, 2006

Feb. 13, 2006

Just curious, has anyone ever managed to make a drag-and-drop MacOS app with Python? I'd love to make an image-batch-processing app that works this way (to pad photos to match my extra-wide Powerbook 17' screen). If so, what is the protocol for discovering what file(s) have been dropped on you? Ken Brooks Sparkling Light Software

4 6

Fink vs. MacPython
by Markus Feb. 13, 2006

Feb. 13, 2006

Hi! Somewhere deep in the latest discussion I read a remark by Bob that he would not recommend the use of Finks python (there also was another that he didn't like Debian so that may explain it :) I came from Debian to OS X and nearly the first thing I did was to install Fink and thusly python. The three extensions I needed so far did install with 'python setup.py install' and everything works fine for me. So why is Fink 'bad'? Am I missing some features I would have had with MacPython? thanks, Markus

4 3

Re: [Pythonmac-SIG] My stab at a new page
by Ronald Oussoren Feb. 12, 2006

Feb. 12, 2006

On 12-feb-2006, at 19:28, Bill Janssen wrote: >>> So you're saying that the pre-installed version could never be >>> really >>> acceptable. In that case, perhaps we only need convince Apple to >>> move >>> /usr/bin/python to some more system-y place that wouldn't usually be >>> on users' paths. >>> >>> We then in the MacPython world take the position that Python isn't >>> really pre-installed on Macs, and the place for a person to start >>> would be to download the installer and run it. Perhaps then in >>> addition the installer could symlink /usr/local/bin/pythonw to >>> /usr/bin/python, thereby solving the PATH issue. >> >> That won't happen. Replacing system components is completely wrong, >> what if someone finds a security bug in /usr/bin/python and Apple >> ships >> a security update to fix it [*]. The installer should update the >> user's >> path to ensure that our version of python is earlier on the PATH. > > I guess that would be one way to get Apple to ship Python updates :-). > > You missed the first part of my message, I think. The system version > would be installed under /usr/libexec/, or some such place, not under > /usr/bin/. That would leave /usr/bin free for the MacPython gang to > install its version, or at least a symlink to /usr/local/bin/pythonw. The system version is installed in /usr/bin. Or do you mean we should only support some future version where Apple doesn't place python in /usr/bin (which I hope doesn't happen)? Ronald > > Bill

3 5

Re: [Pythonmac-SIG] New Page, first proposal
by Ronald Oussoren Feb. 12, 2006

Feb. 12, 2006

On 12-feb-2006, at 19:25, Bill Janssen wrote: >>> So it seems that a old Unix-style Python program which reads from >>> stdin (or a file or a tty) and writes to stdout would be >>> difficult to >>> explain to someone who has never used a command line. And there's >>> essentially no way to get Idle started without using a command line. >> >> If you install py2app and then run the setup script below you'll end >> up with IDLE-2.3.app in the dist directory. > > Don't you have to use the command line to run the setup script? Someone will have to do that, but this end-result can be stuffed into a DMG and made available on the web. Ronald

3 3

Re: [Pythonmac-SIG] My stab at a new page
by Ronald Oussoren Feb. 12, 2006

Feb. 12, 2006

On 12-feb-2006, at 20:38, Bill Janssen wrote: >> The system version is installed in /usr/bin. Or do you mean we should >> only support some future version where Apple doesn't place python in >> /usr/bin (which I hope doesn't happen)? > > Yes, that was the idea. /usr/libexec/python, or some other directory > unlikely to be on the user's path by default. > > I don't know about "only support". "Hope for" was more like it. If you want to install MacPython's python interpreter as /usr/bin/python without replacing system compontents the MacPython distribution wouldn't be useable on any existing OSX version. That's what I meant with "only support". Even if Apple were to move it's python interpreter of the default PATH (and I hope they won't do that), I wouldn't be in favor of installing into /usr/bin. It is very annoying when software gets installed into system locations, especially when you don't quite know what got installed. Ronald

1 0

My stab at a new page
by Bill Janssen Feb. 12, 2006

Feb. 12, 2006

I've made up a sample page, at http://bill.janssen.org/new-macpython-page.html. This is the kind of thing I'd like to see replace the page at http://www.python.org/download/download_mac.html. Bill

14 83

Re: [Pythonmac-SIG] How to fetch iCal todo description?
by has Feb. 12, 2006

Feb. 12, 2006

Paul Berkowitz wrote: >So now you're saying that - in spite of AppleScript not having 'description' >in the iCal 1.5.5 dictionary in Panther - appscript can still get it? Do you >mind explaining how that might be possible, has? I did check 1.5.5 in 10.4, but I know it's not iCal 2.0's dictionary I was looking at because the two dictionaries look different. iCal's .scriptTerminology file defines a 'description' property for calendar, event and todo classes, and always has. If they're not showing up on 10.3 it could be because the definitions themselves are suspect (there's an unfamiliar 'Sex' key), and 10.3 is fussier than 10.4 about this. I suspect that rather than fix the .scriptTerminology they relaxed the .scriptTerminology->aete conversion in 10.4. I'm not rebooting into 10.3 to check this theory just now though, but feel free to dink about with it yourself. But it'd certainly explain why I could see the properties on 10.4 while someone on 10.3 wouldn't. Plus it means that the problem may well be fixable on 10.3 with a bit of judicious editing of the relevant entries. has -- http://freespace.virgin.net/hamish.sanderson/

2 1

xcode as IDE?
by I. Vinogradov Feb. 12, 2006

Feb. 12, 2006

Hello All, while on the topic of IDEs, would it be possible to somehow adapt Xcode to the task? It has Python keyword highlight, and PyObjC is one of the possible types of documents. I have some vague notion that perhaps a pure python file template can be made, that uses framework installation and all. Is something like that even possible? Regards, Ivan.

4 3

Re: [Pythonmac-SIG] My stab at a new page
by Ronald Oussoren Feb. 12, 2006

Feb. 12, 2006

On 10-feb-2006, at 4:24, Bill Janssen wrote: >> Could a Mac ever ship with an >>> acceptable pre-installed Python? If not, perhaps the solution for >>> Apple is to move /usr/bin/python to some other spot, like >>> /usr/libexec/, or some such place. >> >> The issue of not being able to produce redistributable applications >> still exists, and also backwards compatibility with previous versions >> of Mac OS X. > > So you're saying that the pre-installed version could never be really > acceptable. In that case, perhaps we only need convince Apple to move > /usr/bin/python to some more system-y place that wouldn't usually be > on users' paths. > > We then in the MacPython world take the position that Python isn't > really pre-installed on Macs, and the place for a person to start > would be to download the installer and run it. Perhaps then in > addition the installer could symlink /usr/local/bin/pythonw to > /usr/bin/python, thereby solving the PATH issue. That won't happen. Replacing system components is completely wrong, what if someone finds a security bug in /usr/bin/python and Apple ships a security update to fix it [*]. The installer should update the user's path to ensure that our version of python is earlier on the PATH. Ronald [*] the first part being very unlikely of course :-) > > Bill > _______________________________________________ > Pythonmac-SIG maillist - Pythonmac-SIG(a)python.org > http://mail.python.org/mailman/listinfo/pythonmac-sig

2 1

Re: [Pythonmac-SIG] New Page, first proposal
by Ronald Oussoren Feb. 12, 2006

Feb. 12, 2006

On 9-feb-2006, at 4:24, Bill Janssen wrote: >> I am one of those too, of course, but I do know a lot of Mac users >> who spend most of their time in applications like Photoshop, >> Dreamweaver, BBEdit, etc. and rarely venture towards the Terminal. >> Not quite the same audience, but at least some of them would be >> potential Python users by way of appscript or web development tools. > > Sure, that make perfect sense. > >>> But my point was simply that it seems hard to be a Mac user these >>> days >>> without some basic use of the Terminal. >> >> That's not true at all. > > OK, I'm probably the wrong person to assess that. > > So it seems that a old Unix-style Python program which reads from > stdin (or a file or a tty) and writes to stdout would be difficult to > explain to someone who has never used a command line. And there's > essentially no way to get Idle started without using a command line. If you install py2app and then run the setup script below you'll end up with IDLE-2.3.app in the dist directory. This application bundle is 64KByte small and will start the IDLE GUI. Feel free to enhance this with a nice icon. # Begin of setup.py import idlelib, os import py2app from distutils.core import setup setup( name="IDLE-2.3", app=[os.path.join(os.path.dirname(idlelib.__file__), 'idle.py')], options=(dict( py2app=dict(argv_emulation=True) )), ) # End of setup.py > > Bill > _______________________________________________ > Pythonmac-SIG maillist - Pythonmac-SIG(a)python.org > http://mail.python.org/mailman/listinfo/pythonmac-sig

2 1