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

installer and .profile
by William Kyngesburye April 24, 2006

April 24, 2006

I just noticed a small issue with the new universal installer. It adds a path to the python bin folder to the user's ~/.profile. 1. The Apple-default bash shell doesn't read .profile (doesn't for me). (I think tcsh does, but I always used .login back then) 2. If it doesn't exist, .profile gets created with root ownership, since the installer must autorize to install. 3. Symlinks to the python binaries are installed in /usr/local/bin anyways. So really the installer should check if /usr/lcoal/bin is in the user's path. Since a user can choose their shell, maybe it shouldn't be trying to add to the user's path, but just tell the user that's what they need to do. Or if there is some way for the installer to figure out the user's default shell (I know it's a setting in the netinfo database for each user), the installer could intelligently edit the correct shell init (ie .bash_profile). ----- William Kyngesburye <kyngchaos(a)kyngchaos.com> http://www.kyngchaos.com/ "Those people who most want to rule people are, ipso-facto, those least suited to do it." - A rule of the universe, from the HitchHiker's Guide to the Galaxy

1 0

Re: [Pythonmac-SIG] Fwd: MacPython icon mockup
by Jordan Krushen April 22, 2006

April 22, 2006

On 4/22/06, Bill Janssen <janssen(a)parc.com> wrote: > > Alright, one more go with the egg icon. I agree, it did look a bit off: > > > > http://hcs.harvard.edu/~jrus/python/prettified-py-icons.png > > That's a great-looking egg! +1 :) J.

1 0

Re: [Pythonmac-SIG] on a tangent from new icons
by Brendan Simons April 22, 2006

April 22, 2006

On 21-Apr-06, at 6:13 PM, pythonmac-sig-request(a)python.org wrote: > On Apr 21, 2006, at 3:08 PM, Jacob Rus wrote: > >> Bob Ippolito wrote: >>> Jacob Rus wrote: >>>> * Do we want different icons for py2applet.app and >>>> BuildApplet.app? >>>> What exactly is the difference between these? >>> >>> BuildApplet isn't any good at creating self-contained applications. >>> py2applet is. py2app does not ship with Python. >> >> Ok, well neither of the apps has an icon yet, but I [updated][1] >> some of >> the icons. I think that the "applet" icon can be the default for >> applets created by BuildApplet, and the "generic python app" icon >> can be >> the default for apps created with py2app or py2applet. How does that >> sound? Is it possible to give py2app a default icon? > > Yes, of course we can give py2app-built apps a default icon. > py2applet should probably have a different icon though, so it's > distinguishable from the apps it generates. When/if you come up > with them, just shoot them over my way and I'll see about tossing > them in! > > -bob Jacob, In your composite image, does the applet.app icon refer to applications built with buildapplet.app, or buildapplet.app itself? If the former, what is the rationale for using different icons for py2app-built apps, and applets? They're both applications as far as the user is concerned. Brendan

1 0

Re: [Pythonmac-SIG] Fwd: MacPython icon mockup
by Jacob Rus April 22, 2006

April 22, 2006

Jordan Krushen wrote: > +1 on everything so far, including the recent changes on the egg, but > the egg still looks odd to me.. it looks like it's sitting on its thin > end.. would it be possible to flip the ends of the egg? Alright, one more go with the egg icon. I agree, it did look a bit off: http://hcs.harvard.edu/~jrus/python/prettified-py-icons.png -Jacob

2 1

Re: [Pythonmac-SIG] Fwd: MacPython icon mockup
by Brendan Simons April 22, 2006

April 22, 2006

On 22-Apr-06, at 4:59 AM, pythonmac-sig-request(a)python.org wrote: > Date: April 21, 2006 11:00:22 PM EDT (CA) > To: pythonmac-sig(a)python.org > Subject: Re: [Pythonmac-SIG] Fwd: MacPython icon mockup > > > Jacob Rus wrote: >> How's this then: >> http://hcs.harvard.edu/~jrus/python/prettified-py-icons.png > > Alright, 2 or 3 of the icons have since been updated, and that > picture is new and improved. Are there any more suggested tweaks, > or are the icons done so far ready to sail? Specifically, what do > people think of the "generic application" icon as a default for > apps created by py2app/py2applet? Also, is the pencil for the > IDLE.app icon now okay, or can it still use work? > > The icons still needing to be done are one for py2applet, and one > for BuildApplet.app. I'm thinking both of these can be stuffit- > esque grinders, or similar, one with the "applet" icon coming out > the bottom, and the other with the "generic app" icon coming out > the bottom, and with python scripts going in the top. > > -Jacob I like what you did with the idle pen, egg shadow, and generic app icons Jacob. Thanks again. For the build applet, if the grider icon doesn't work, what about the generic app icon self assembling from bits. Like this: http://www.flickr.com/photos/28928816@N00/133016352/ Brendan -- Brendan Simons

2 1

Re: [Pythonmac-SIG] Fwd: MacPython icon mockup
by Brendan Simons April 22, 2006

April 22, 2006

On 21-Apr-06, at 6:00 AM, donovan wrote: >> I don't think stealing the Apple Installer icon is a good idea for >> .egg though - double-clicking it doesn't install anything. Perhaps >> something closer to a StuffIt archive icon (a closed box) or a Python >> logo behind Apple's zipper icon with "EGG" underneath. Or an egg? >> Anyone remember Software Ventures' logo? :) > > How about just the lego brick used for components with the python > logo on the side. Look in /System/Library/Components. I'm wary of using the brick logo, because as far as I can see Apple uses them extensively for OS components. I don't want to dilute their visual meaning by co-opting the icon for something different. I agree that the box isn't great either though since eggs aren't executable. On 21-Apr-06, at 6:00 AM, donovan preston wrote: > On Apr 20, 2006, at 8:38 PM, Nicholas Riley wrote: > >> On Thu, Apr 20, 2006 at 11:11:19PM -0400, Brendan Simons wrote: >>> I've attached a few more mockups using Jacob's excellent aquified >>> logo. Have a look here: >>> http://www.flickr.com/photos/28928816@N00/132185325/ > > Awesome. I love them. Ship it. :-) > >> I don't think stealing the Apple Installer icon is a good idea for >> .egg though - double-clicking it doesn't install anything. Perhaps >> something closer to a StuffIt archive icon (a closed box) or a Python >> logo behind Apple's zipper icon with "EGG" underneath. Or an egg? >> Anyone remember Software Ventures' logo? :) > > How about just the lego brick used for components with the python > logo on the side. Look in /System/Library/Components. > >> The PYTHON text appears to be in the wrong font. By analogy with >> AppleScript, perhaps the text shouldn't be there at all (although how >> many people will recognize the Python logo anyway?) > > Probably the python logo is enough, since the file ends in .py. > > dp OK, here I have to disagree again. I use icon view all the time, and I really appreciate having filetypes written on file icons. It's one of the reasons I switched to the mac. It lets me know what type of is what without having to decode some unfamiliar icon, or look to the file extension (which is still optional on the mac, though I admit, required for python). I'll look into the font, but I thought it was supposed to be Lucida Grande. Does anyone have a wiki where I could throw up a straw poll? On 21-Apr-06, at 6:00 AM, jacob rus wrote: > Brendan Simons wrote: >> I've attached a few more mockups using Jacob's excellent aquified >> logo. Have a look here: >> http://www.flickr.com/photos/28928816@N00/132185325/ > > Alright, I tried the monochrome idea for bytecode files, and also > put up my own attempt at an embossed logo on a rocket: > > http://hcs.harvard.edu/~jrus/python/docs-and-rocket.png > > All of these are also included in the psd file (which keeps getting > bigger... I should maybe remove some unused layers): > > http://hcs.harvard.edu/~jrus/python/python-icons.psd > > -Jacob These are great Jacob. I like the disk image in particular. There's a couple of changes I'd like to try this evening: - I will incorporate your new icon, - I want to see what real python bytecode looks like on the pyc/pyo icon. - The rocket logo looks better to me centered over the widest bit - The mechanical pencil needs a bit of perspective so that it appears to lay flat on the sheet. If you're looking for more pencil images, here's two good ones: http://www.keyboardmag.com/Pictures/web/y/h/c/Pentel_Pencil.jpg http://www.misterart.com/grouppix/280x210/2000/g2417.jpg I'll check back with something tonight, Brendan

9 18

Re: [Pythonmac-SIG] Fixing the documentation...
by Ronald Oussoren April 22, 2006

April 22, 2006

On 19-apr-2006, at 2:23, Bill Janssen wrote: > Just looking at the docs, I'm trying to figure out what's good and > what's bad. > > 1) We should no longer point people to Jack's site, we point them to > the python.org Mac download page instead. Right. > > 2) references to PythonIDE and PackageManager should go. Right again. I want to remove those from python2.5 if I can, or at least move them somewhere where they cannot do harm. > > 3) What about the following: > > 2. MacPython Modules > 2.1 macpath -- MacOS path manipulation functions > 2.2 macfs -- Various file system services > 2.2.1 FSSpec Objects > 2.2.2 Alias Objects > 2.2.3 FInfo Objects > 2.3 ic -- Access to Internet Config > 2.3.1 IC Objects > 2.4 MacOS -- Access to Mac OS interpreter features > 2.5 macostools -- Convenience routines for file manipulation > 2.6 findertools -- The finder's Apple Events interface > 2.7 EasyDialogs -- Basic Macintosh dialogs > 2.7.1 ProgressBar Objects > 2.8 FrameWork -- Interactive application framework > 2.8.1 Application Objects > 2.8.2 Window Objects > 2.8.3 ControlsWindow Object > 2.8.4 ScrolledWindow Object > 2.8.5 DialogWindow Objects > 2.9 autoGIL -- Global Interpreter Lock handling in event loops > 3. MacPython OSA Modules > 3.1 gensuitemodule -- Generate OSA stub packages > 3.2 aetools -- OSA client support > 3.3 aepack -- Conversion between Python variables and > AppleEvent data containers > 3.4 aetypes -- AppleEvent objects > 3.5 MiniAEFrame -- Open Scripting Architecture server support > 3.5.1 AEServer Objects > 4. MacOS Toolbox Modules > 4.1 Carbon.AE -- Apple Events > 4.2 Carbon.AH -- Apple Help > 4.3 Carbon.App -- Appearance Manager > 4.4 Carbon.CF -- Core Foundation > 4.5 Carbon.CG -- Core Graphics > 4.6 Carbon.CarbonEvt -- Carbon Event Manager > 4.7 Carbon.Cm -- Component Manager > 4.8 Carbon.Ctl -- Control Manager > 4.9 Carbon.Dlg -- Dialog Manager > 4.10 Carbon.Evt -- Event Manager > 4.11 Carbon.Fm -- Font Manager > 4.12 Carbon.Folder -- Folder Manager > 4.13 Carbon.Help -- Help Manager > 4.14 Carbon.List -- List Manager > 4.15 Carbon.Menu -- Menu Manager > 4.16 Carbon.Mlte -- MultiLingual Text Editor > 4.17 Carbon.Qd -- QuickDraw > 4.18 Carbon.Qdoffs -- QuickDraw Offscreen > 4.19 Carbon.Qt -- QuickTime > 4.20 Carbon.Res -- Resource Manager and Handles > 4.21 Carbon.Scrap -- Scrap Manager > 4.22 Carbon.Snd -- Sound Manager > 4.23 Carbon.TE -- TextEdit > 4.24 Carbon.Win -- Window Manager > 4.25 ColorPicker -- Color selection dialog > 5. Undocumented Modules > 5.1 applesingle -- AppleSingle decoder > 5.2 buildtools -- Helper module for BuildApplet and Friends > 5.3 cfmfile -- Code Fragment Resource module > 5.4 icopen -- Internet Config replacement for open() > 5.5 macerrors -- Mac OS Errors > 5.6 macresource -- Locate script resources > 5.7 Nav -- NavServices calls > 5.8 PixMapWrapper -- Wrapper for PixMap objects > 5.9 videoreader -- Read QuickTime movies > 5.10 W -- Widgets built on FrameWork > 5.11 waste -- non-Apple TextEdit replacement > > My inclination is to delete them all :-). Except for ones where > someone pipes up and tells me it still works. Let folks use the Wiki > to find modules. I don't think you can remove them. IIRC some of this is generated somehow (although I don't know how). Macpath deals with OS9/Carbon style paths (Volume:directory:file instead of /Volume/directory/file). This might be usefull when using Carbon API's. The documentation for this module (and several others) does need to mention this instead of confusing users by mentioning it is for the mac. Section 4 (MacOS Toolbox Modules) definitely needs some text. At the very least it needs a general explanation about how to translate between the C interface as described in Apple's documentation and the Python interface. W (5.10) and waste (5.11) should probably go, waste won't work on intel systems anyway and W is ancient and not update for Carbon Events. Gensuitemodule should be deprecated, at the very least in the documentation. I don't know if we can point users to software that's not in the stdlib, but if we can I'd add a reference to appscript in the deprecation message in the documentation. Has can probably comment on the usefulness of the rest of section 3. I don't know enough about the rest to make useful comments about them. I do think however that we shouldn't remove all documentation, but should instead work on improving both the documentation and actual code. > > 4) Should we document some of the newer stuff? py2app comes to mind. Not in the official python documentation. You can't add documentation for stuff that is not part of the stdlib. More documentation for py2app is of course welcome, and I'm sure Bob is willing to add it to the py2app package when you write it :-) Ronald

3 7

No arbitrary precison math on Mac-tel say it ain't so!
by Daniel Lord April 22, 2006

April 22, 2006

The analog of a single gene pool in nature has come to pass for arbitrary precison math (APM) for OS X (native not Python). GMP is 'it' for APM as far as I can tell unless I want to write my own. And GMP doesn't compile on Mac-tel and won't for some time: The current release is 4.2, released 2006-03-26. It fixes all bugs found in 4.1.4, as well as several portability problems. It also adds several new features. Note that we chose not to work around all new GCC bugs in this release. Never forget to do a make check after building the library to make likely it was not miscompiled! Issues with GMP 4.2: Miscompilation on several platforms using several different compilers. Remember to run make check! GMP does not build on MacInteltoch machines. Since Apple uses their own, creative assembly syntax, it is not trivial to fix this.

2 1

Re: [Pythonmac-SIG] Fwd: MacPython icon mockup
by Jacob Rus April 22, 2006

April 22, 2006

has wrote: > The pen on the IDLE icon could use some subtle tweaking as it's > looking a bit flat, grey and lifeless, and a tad long and thin too... > > I've attached a rough version to give an idea. I might've taken > slightly too much off the barrel, and I've lost some highlights. It > was quick-n-dirty and I didn't have my tablet to hand, so don't > take it as gospel truth; you'll have to fine-tune your own version > yourself. :) I just grabbed the pencil off the internet, shortened it, and stuck it on. I should probably change the perspective, and make the changes you suggest. Maybe a different pencil would be a better model. I'll give it another shot, though other submissions would be great. :) > The only icon that isn't working yet is the generic icon: the > snakes and the pencil/brush/ruler are both battling to be center of > attention - the eye keeps bouncing uncomfortably back and forward > between the two - and the icon as a whole is a bit similar to the > IDLE icon. I agree. > One thing you might try is making the snakes appear like those on > the .dmg - lighter greyscale, perhaps without the glass effect - so > the overall look is closer to the Mac's standard generic > application icon and the original "A" is clearly dominant, but > still with an indication of its Pythonness. Alright, how is this: > If it still doesn't work then it'll be a case of coming up with a > more radical alternative. (I know folk don't want an AppleScript > applet clone, but certainly something as different to the generic > app icon as that is.) However, I think it probably will. I think that it'd be good to keep the applet icon for use with Build Applet.app, and let this icon be for icons created with py2app/ py2applet (I think that's in line with the traditional distinction between applets and apps as well, the former not really being standalone). Thanks for all the suggestions and encouragement. Keep the insight coming. -Jacob

3 4

import sip problem (Universal Mac 2.4.3) and build options
by Adam Tenderholt April 22, 2006

April 22, 2006

I'm trying to get sip and PyQt working with Universal MacPython 2.4.3. It compiles fine however trying to import sip results in the error: "ImportError: Inappropriate file type for dynamic loading". I posted on the PyKDE/PyQt/sip mailing list, and it was suggested that I try to reconfigure and rebuild Python-2.4.3 with: DYNLOADFILE=dynload_shlib.o ./configure --enable-framework --enable-toolbox-glue --enable-shared Unfortunately, I get the following error during make: /usr/bin/ld: warning Python.framework/Versions/2.4/Python cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded) /usr/bin/ld: Undefined symbols: _PyMac_Error _Py_Main collect2: ld returned 1 exit status I've looked online for the options used to compile Universal MacPython, but I haven't had any luck. Is there a someplace I should be looking? Thanks, Adam

1 0