🌐 Mailman 3 August 2002 - Pythonmac-SIG - python.org

Re: [Pythonmac-SIG] ObjC stuff
by Jack Jansen March 20, 2003

March 20, 2003

Recently, Steve Spicklemire <steve(a)spvi.com> said: > So it's in CVS somewhere? I'll do a check-out and see if I can find it. I don't know, Steven Majewski may know (I think he is the one who looked at it). If it isn't in the repository it probably should be, preferrably in the Modules directory (because it is useful for non-Mac users) but if there's objections against that we'll put it in the Mac/Modules dir. > I just ordered CW-6 today so I might be able to pitch in a bit. While very useful for other things (like MacPython development) you don't need it for OSX unix-Python development: this is all make and gcc-based (and you have those on your OSX developer disc). -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen(a)oratrix.com | ++++ if you agree copy these lines to your sig ++++ www.oratrix.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm

5 4

Configure question
by bill fancher Dec. 14, 2002

Dec. 14, 2002

I'm running 10.2 and upgraded autoconf to 2.53 so that I can regenerate configure from configure.in. Having done so, I now notice that I get the following line in configure output: checking LINKCC... ld: Undefined symbols: ___gxx_personality_v0 Should I worry? Is it just something I overlooked before? Is anyone else seeing this? (He asked, hoping to avoid having to isolate, and perhaps remedy, the underlying cause.) -- bill "They laughed at Columbus, they laughed at Fulton, they laughed at the Wright brothers. But they also laughed at Bozo the Clown." Carl Sagan

2 2

Testing MachoPython
by Michael Esveldt Sept. 6, 2002

Sept. 6, 2002

This is a fairly basic question, but its answer might be of some small use to MacPython: How safe is it to perform test builds? I follow the list closely and, in the interest of a working MachoPython, I frequently would like to help perform some of the basic tests that are requested by Jack and others. I'm a little wary, however, because this is all very new stuff. I have an existing installation of python by fink, will I still be able to use that if I install MacPython from CVS? Will installing a test version cause problems when a neatly packaged installation eventually comes along? I do some fairly silly things with this box, considering it's my work computer, but what can I say? I'm a reckless student. (Apparently not quite /that/ reckless.) Thanks, Michael Hail Eris. Michael Esveldt Sarah Lawrence College, Bronxville, NY, USA http://raptor.slc.edu/~dante / http://extraneous.livejournal.com/

3 2

Need help debugging Python documentation install
by Jack Jansen Sept. 4, 2002

Sept. 4, 2002

Folks, I just checked in a couple of things that allow you to create a version of the Python documentation that is viewable from Apple Help Viewer and Project Builder. Special thanks go to Bill Fancher, who created the script to make this all work. Now, however, I need to debug the way I'm installing the documentation, and I can't do that myself, because it seems that once you've told Apple help Viewer about a documentation set there is absolutely no way to make it forget that documentation again, so my system is tainted. Here's the setup of things: - There's a script Mac/OSX/setupDocs.py. Call "python setupDocs.py build" to build the documentation, wait until the Help indexing tool is done, then call "python setupDocs.py install". For the moment, for testing purposes, this will install the 2.2.1 documentation. The script should only be used with a framework Python, and it will install the docs in the framework (in Resources/English.lproj/Documentation). - This is good enough for Project Builder (although the documentation does not show up in the help window it is viewable if you add Python.framework to your project and then open the reveal triangle of Python.framework). It isn't good enough for Help Viewer, though, it wants the documentation to be referred to from a .app bundle. For this reason Python.app contains the magic words in its Info.plist file, and has a symlink Resources/English.lproj/Documentation that points to the location above. Now, all this may be good enough, and it may not be, and I can't test it anymore. If someone could do the following: - cvs update - make frameworkinstall - python setupDocs.py build - python setupDocs.py install - Run a script with Python.app, something that stays open for a while so you can see the menu bar. Something like import EasyDialogs EasyDialogs.Message("Hello World") should do the trick. - Check whether there's a help menu, and whether the "Python Help" entry will open the Python docs in help viewer. - Open Help Viewer manually and check whether the Python documentation is mentioned in the index page. - Report your findings back here. -- - Jack Jansen <Jack.Jansen(a)oratrix.com> http://www.cwi.nl/~jack - - If I can't dance I don't want to be part of your revolution -- Emma Goldman -

7 20

Embedding & C utility routine question
by Sung Kim Aug. 31, 2002

Aug. 31, 2002

I have a C app which puts up a GUI, and calls Python scripts. The Python scripts write to stdout. After all is done, I see both the GUI and the console window. But I'm having trouble making the console active. I'm guessing there are routines which disable/enable things (i.e. event loop), and I will look into that. If anybody can help narrow my search, I would appreciate that very much! Thank you. --Sung H. Kim skim(a)adobe.com

1 0

10.2 and python
by Matthew Smith Aug. 30, 2002

Aug. 30, 2002

If someone doesn't mind helping me clarify this... It seems python comes installed with 10.2, but not the python framework. To embed a python app using 10.2 I'd need to install the python framework?? What about running the framework on a 10.2 machine? Thanks Matt Sorry about the cross-post but I want to here both groups ideas/responses

7 6

Script for building OS X disk image archives (.dmg)
by Dinu Gherman Aug. 27, 2002

Aug. 27, 2002

Hi, I've started to understand a little bit more about how to generate .dmg archives on OS X. So I coded this into a simple script which is very much beta, but some of you might want to test and/or improve that. It's currently here: http://python.net/~gherman/projects/buildpkg/builddmg.dmg This is a 72 KB file generated with builddmg.py contained inside. ;-) I'm not sure yet if it should merge one day with my other script named buildpkg or not... Eventually all this should go into distutils, but that hasn't reached a state where I could understand how to extend it. ;-) Feedback is welcome, especially on how to use the "really" needed maximum archive size in blocks and on how to get rid off the nasty messages by hdiutil. Regards, Dinu

1 0

RE: [Pythonmac-SIG] Which version of Python comes preinstalled wi th 10.2?
by Schollnick, Benjamin Aug. 27, 2002

Aug. 27, 2002

>From what I see....I believe it's the straight Unix version... - Benjamin -----Original Message----- From: Samuel Smith [mailto:smithsm@samuelsmith.org] Sent: Tuesday, August 27, 2002 1:32 AM To: pythonmac-sig(a)python.org Subject: [Pythonmac-SIG] Which version of Python comes preinstalled with 10.2? Which version of python comes preinstalled with 10.2. MachO or Unix? ********************************************************************** Samuel M. Smith Ph.D. 360 W. 920 N. Orem, Utah 84057 801-226-7607 x112 (voice) 801-226-7608 (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" ********************************************************************** _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG(a)python.org http://mail.python.org/mailman/listinfo/pythonmac-sig

1 0

problem with EditPythonPrefs
by Magladry, Stephen Aug. 27, 2002

Aug. 27, 2002

I am trying to run EditPythonPrefs and get the following error. Traceback (most recent call last): File "Mac OS X:Applications:Python 2.2.1:Mac:scripts:EditPythonPrefs.py", line 212, in ? main() File "Mac OS X:Applications:Python 2.2.1:Mac:scripts:EditPythonPrefs.py", line 205, in main edit_preferences() File "Mac OS X:Applications:Python 2.2.1:Mac:scripts:EditPythonPrefs.py", line 187, in edit_preferences options = handler.load() File "Mac OS X:Applications:Python 2.2.1:Mac:Lib:pythonprefs.py", line 83, in load dict['creator'], dict['type'] = self.gusi.load() File "Mac OS X:Applications:Python 2.2.1:Mac:Lib:pythonprefs.py", line 40, in load self.data = self.loader.load() File "Mac OS X:Applications:Python 2.2.1:Mac:Lib:preferences.py", line 57, in load self.data = self.default.load() File "Mac OS X:Applications:Python 2.2.1:Mac:Lib:preferences.py", line 119, in load self.data = self.default.load() File "Mac OS X:Applications:Python 2.2.1:Mac:Lib:preferences.py", line 21, in load raise Error, "No default given" Preferences.Error: No default given Can someone tell me what is going wrong? I am able to run ConfigurePythonCarbon, but after that EditPythonPrefs fails. Thanks, Stephen Magladry

1 0

Re: [Pythonmac-SIG] Private frameworks - BINGO!
by Dan Grassi Aug. 26, 2002

Aug. 26, 2002

On Sunday, August 25, 2002, at 04:44 PM, tmk wrote: > On Sunday, Aug 25, 2002, at 22:00 Europe/Brussels, Dan Grassi wrote: > >> On Sunday, August 25, 2002, at 03:31 PM, tmk wrote: >> >>> In fact, I'd advocate that we rather leave Apple's install untouched >>> and provide our own, different. The main reason being that Apple may >>> upgrade its version at anytime and we don't want anything to break. >> >> Should Python be a special case, that is handled differently than >> perl, tcl, OpenSSH, OpenSSL, apache, ruby, php, etc? Consider what >> a mess if all these also followed the same method of installing >> separate versions. Following such a policy is little different than >> the old days when many applications installed SimpleText and there >> were so many copies and versions that it became a nightmare. >> Installing multiple versions of Python by default creates confusion on >> the part of the user. > > From what I see around the Web (e.g. Fink), people usually take great > care *NOT* to install stuff over Apple's. So the exception would be to > "update" Apple's installation :-). From what I've seen the Fink phylosphy has created problems even for building Python. Other than Fink installations do indeed install into the Apple standard locations. It is also unix/Linux phylosphy to install into the standard locations. > I would not be surprised if there were Apple guidelines to that effect > (especially because in most case, it's totally easy stuff without > touching Apple's stuff e.g. look at what Fink does) IMO it is a mistake to take Fink's phylosphy as the gold standard, they are not Apple. > There's a reason for the current layout of the filesystem both from > Apple and from the Unix side of things. Separation of responsibility. Yes, the unix (BSD) side of thinks are in the Darwin cvs and that includes Python. >> >> Let's say that we install a new version of Python and then Apple in >> their stupidity updates their version to an older version and updates >> symlinks in /usr/local/bin, etc. Now the user gets Apple's version >> anyway. Further if the user may well execute different version of >> Python based on _how_ it is called. This should _not_ be the default >> case. > > First the problem is not that Apple would do stupid things. For example > you could have a tuned version of Python with additionnal modules. > You'd rather install it under /usr/local/ instead of replacing Apple's. While this can be done it is not the usual install and should not be considered as a default. Anyone wanting to do this should be on their own in the same manner that putting Apache in a non-standard location is possible but not a default. > It's only normal that when Apple upgrades they only upgrade their > version and leave yours untouched. >> There is a versioning system in place in frameworks that allows >> multiple versions for those who are astute enough and handles the >> default case for the average user as well. > > Well, you could have a tuned version of python with additional modules > but with the same version. They're different but have the same version > number. The versioning does not handle this case (neither does it > handle minor point releases IIRC) There is an implicit assumption that Apple will _remove_ things, why should we assume this? >> IMO we should not fight Apple, not assume that Apple is going to do >> the stupid thing and we must follow the path best suited to the base >> user, that is run programs developed by others. > > I agree. But than again what you advocate goes contrary to this > philosophy. Don't you think that "fighting Apple" would be installing > over their version? No, fighting Apple, IMO, is for all the various package maintainers to make their individual idiosyncratic decisions, this is exactly what the problem that Linux Standard is addressing. With such a situation one would not see any consistancy and it would make things more difficult. >> KISS > > Exactly. Suppose two different providers each install their own version > of python over Apple's, or your own fine tuned one, would you be happy? If I do the install yes. Consider Perl, I don't want to write programs in it but I do have Perl programs that I use -- the last thing I want is even more confusion about using Perl. KISS -- put it where people expect it. Dan

1 0