🌐 Mailman 3 December 2001 - Pythonmac-SIG - python.org

Re: Pythonmac-SIG digest, Vol 1 #929 - 12 msgs
by Jeff Harmon Dec. 20, 2001

Dec. 20, 2001

on 12/19/01 09:01 AM, pythonmac-sig-request(a)python.org wrote: > The interpreter works for me on OSX (10.1), but when I try to load a shared > lib that is linked against PythonCoreCarbon, I get a fatal error. Also, I > can't run the Python Prefs utility. I haven't gotten to a point of stability where I can see if I can use any glued DLLs. OBTW - Jack!!! Both the MacPython IDE and Interpreter fail for the same reasons but the IDE leaves me without access to a prompt so I can't hack/recover after I "die" there. The interpreter shows me a command prompt (if I return) at the point of failure so I can hack that one and get macfsn to import, etc. after editing sys.path[]. > Jeff - is this similar to the problem you're having? Since you're here, I'm > seeing it when my AE plug-in (which is linked against Python) is > dynamically loaded by AE. Sounds very similar. JR

2 2

MacPython 2.2c1 available
by Jack Jansen Dec. 20, 2001

Dec. 20, 2001

Folks, MacPython 2.2c1 is available via http://www.cwi.nl/~jack/macpython.html . This is a final candidate for MacPython 2.2, which is due this weekend, so please send any feedback to pythonmac-sig(a)python.org as soon as possible. The main differences with the last beta release are that this MacPython should now run on old systems again (from MacOS 8.1 onwards), and that the MacOS toolbox interface modules have been updated to Universal Headers 3.4. While neither of these should pose compatibility problems there's always the chance that something silly happened, so please give this release a try. As usual, it won't interfere with your normal Python: different pathnames, prefs files, etc, so there shouldn't be much trouble trying this and then going back to your usual MacPython release. -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen(a)oratrix.com | ++++ if you agree copy these lines to your sig ++++ www.cwi.nl/~jack | ++++ see http://www.xs4all.nl/~tank/ ++++

1 0

Re: [Pythonmac-SIG] Mach-O MacPython IDE!!!
by Jack Jansen Dec. 20, 2001

Dec. 20, 2001

Donovan, hats off!! Especially for just hacking your way along and showing that everything at least works in principle. I had also commented out the EnableAppSwitches, or actually replace them with if hasattr(MacOS, 'EnableAppSwitch'): MacOS.EnableAppSwitch(....) and then I got bogged down in macresource.py. After an hour or so I had to leave the project because 2.2 is due (and IDE won't make it, I'm afraid). A couple of random thoughts: - Should I add a dummy EnableAppSwitch() to MachoPython, or is the hasattr construction good enough? - macresource.py needs work, any takers? What I have in mind is that it allows you to open resource files in both MacPython and MachoPython. There are two problems it needs to solve. One is the pathname problem, for which there's also a solution that is less hacky than what Donovan has done (if the pathname is the wrong type convert to URL and then back to the other type pathname). The other problem is that if you have a Unix Python distribution the .rsrc files are not actually resource files but MacBinary encoded resource files. My idea was to unpack these on the fly, something like if exists(name.df.rsrc) and timestamp(name.df.rsrc) > timestamp(name.rsrc): open-datafork-resource-file(name.df.rsrc) elif has_resource_fork(name.rsrc): open-resource-file(name.rsrc) else: macbinary.decode(name.rsrc, name.df.rsrc, resource_only=1) open-datafork-resource-file(name.df.rsrc) - I think the macfs pathname calls should use native pathnames (i.e. unix-style pathnames in MachoPython). What do other people think? Should I add an optional parameter with which you can override the pathname style, as in fsr = macfs.FSRef('mac:style:pathname', 'mac') fsr = macfs.FSRef('/unix/style/pathname', 'unix') -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen(a)oratrix.com | ++++ if you agree copy these lines to your sig ++++ www.cwi.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm

1 0

Re: [Pythonmac-SIG] Is it just me or...?
by Jack Jansen Dec. 20, 2001

Dec. 20, 2001

> > There are some problems with MacPython on MacOS X. For one thing, it does not > > currently work on a MacOSX multiprocessor. And, since 10.1, it does not work > > on all single-processors anymore either. For some people (like myself) ti > > works fine, for others it doesn't. > > > > We are working hard to resolve this issue, but it now looks that it won't be > > solved before 2.2 :-( I will probably do a 2.2.1 release when it is solved. > > > > But, just to make sure that you're not seeing a different issue: could you > > post the symptoms you see when you try to use MacPython on OSX? > > Is the problem more this installer, or MacPython itself? I haven't used the > installer under 10.1, yet I use MacPython every day. Ok, this is not quite fair, > I built it from the source, with lots of help from Jack. Maybe the installer > screws things up? Hmm, that's also a possibility. I was thinking that it was a problem to do with machine type. Maybe we can have a heads-up on who has problems with OSX and who doesn't, and what their hardware is? Here goes: Deskside G4, 450Mhz, 10.1.1 - No problems iBook (old), 350Mhz, 10.1.1 - No problems -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen(a)oratrix.com | ++++ if you agree copy these lines to your sig ++++ www.cwi.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm

4 3

Re: [Pythonmac-SIG] Re: Pythonmac-SIG digest, Vol 1 #929 - 12 msgs
by Jack Jansen Dec. 19, 2001

Dec. 19, 2001

Recently, Jeff Harmon <jeff.harmon(a)adobe.com> said: > on 12/19/01 09:01 AM, pythonmac-sig-request(a)python.org wrote: > > > But, just to make sure that you're not seeing a different issue: could you > > post the symptoms you see when you try to use MacPython on OSX? > > Here is a summary of what I've encountered. The machine in question is a > dual500 (g4) (with gobs o' RAM and perty much all the fix'ns). It's running > a fully current (as of yesterday) 10.1.1 [...] This is the known problem I was referring to. Sorry, but MacPython does not currently run on OSX multiprocessors, it will hang almost immedeately. This will most likely not be fixed before 2.2, but a maintainance release will be forthcoming as soon as the problem is fixed. We more-or-less know where the problem lies, but unfortunately the only person who can fix it appears to be very busy. In the mean time you can either use MacPython in classic mode or use (for some applications) unix-Python from the commandline. -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen(a)oratrix.com | ++++ if you agree copy these lines to your sig ++++ www.cwi.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm

1 0

Re: Pythonmac-SIG digest, Vol 1 #929 - 12 msgs
by tracy shaun ruggles Dec. 19, 2001

Dec. 19, 2001

on 01.12.19 11:01 AM, Jack Jansen wrote: >> Is the problem more this installer, or MacPython itself? I haven't used the >> installer under 10.1, yet I use MacPython every day. Ok, this is not quite >> fair, >> I built it from the source, with lots of help from Jack. Maybe the installer >> screws things up? > > Hmm, that's also a possibility. I was thinking that it was a problem to do > with machine type. > > Maybe we can have a heads-up on who has problems with OSX and who doesn't, and > what their hardware is? > > Here goes: > Deskside G4, 450Mhz, 10.1.1 - No problems > iBook (old), 350Mhz, 10.1.1 - No problems For me: ibook (old), 366MHz, 10.1.1 - No problems --Tracy -- Tracy S. Ruggles :: tracy @ reinventnow.com

2 1

2.2b2 Mac OS X 10.1.1, iBook, worked no prob.
by Pete Moore Dec. 19, 2001

Dec. 19, 2001

1 0

Re: [Pythonmac-SIG] Large number sets on MacPython (Carbon)
by Jack Jansen Dec. 19, 2001

Dec. 19, 2001

> > Hi All, > > I have just installed MacPython on OS X and converted my unix scripts over. > These scripts deal with large matrix calculations. Unfortunately I find that > when I drop one of these scripts on the interpreter I get a Math range error > but I don't seem to get that when running from the IDE. This is definitely not well-covered ground, I can think of absolutely no reason why math behaviour would be different under the raw interpreter than under the IDE. If this behaviour is easy to reproduce, could you send me a script that shows it? Oh yes: you are indeed dropping your script on the PythonInterpreter, you're not running it with the commandline python interpreter? (Because that is a completely different beast inside than the IDE, so there I could well imagine differrent behaviour for math boundary cases). -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen(a)oratrix.com | ++++ if you agree copy these lines to your sig ++++ www.cwi.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm

1 0

Large number sets on MacPython (Carbon)
by Chris Lee Dec. 19, 2001

Dec. 19, 2001

Hi All, I have just installed MacPython on OS X and converted my unix scripts over. These scripts deal with large matrix calculations. Unfortunately I find that when I drop one of these scripts on the interpreter I get a Math range error but I don't seem to get that when running from the IDE. What I really want to do is drop several of these scripts on the interpreter and leave them to run in background will the interpreter do this? Sorry if I am covering well covered ground Cheers Chris

1 0

Large number sets on MacPython (Carbon)
by Chris Lee Dec. 19, 2001

Dec. 19, 2001

Hi All, I have just installed MacPython on OS X and converted my unix scripts over. These scripts deal with large matrix calculations. Unfortunately I find that when I drop one of these scripts on the interpreter I get a Math range error but I don't seem to get that when running from the IDE. What I really want to do is drop several of these scripts on the interpreter and leave them to run in background will the interpreter do this? Sorry if I am covering well covered ground Cheers Chris

1 0