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

Python ODP category reminder
by Gordon Worley Feb. 25, 2001

Feb. 25, 2001

I haven't done one of these for a while, but I just had a link submitted recently and thought I should remind everyone: if you have a page, site, or anything Online that is MacPython related, then please visit <http://dmoz.org/Computers/Systems/Macintosh/Development/Languages/Python/> to have it listed in the Open Directory Project's MacPython category. Thanks. -- Gordon Worley http://www.rbisland.cx/ mailto:redbird@rbisland.cx PGP: C462 FA84 B811 3501 9010 20D2 6EF3 77F7 BBD3 B003

2 1

Re: [Pythonmac-SIG] CarbonLib incompatibilities
by Jack Jansen Feb. 24, 2001

Feb. 24, 2001

Paul, THANKS! THANKS! THANKS! THANKS! It wasn't exactly the problem you sketched (Python does have the HLEvents flags) but pretty near: you also need the MultiFinder aware flag. Why on _earth_ CarbonLib would require that flag is beyond me. Programs that aren't multifinder aware are going to be 68K code, so they're hardly going to call CarbonLib. -- 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

1 0

Re: [Pythonmac-SIG] CarbonLib incompatibilities
by Jack Jansen Feb. 23, 2001

Feb. 23, 2001

> A few suggestions (which you've probably thought of already): > > Which version of the Carbon stub library are you linking to? > Have you tried the one from the Carbon 1.2.5 SDK? > Check that you are linking to the stub library (in the Carbon Support > folder), and not the actual library (in the Implementation Libraries > folder). I'm linking against the stub lib that's included with CW Pro 6. That's a 1.0.4 stub library. I've started trying to compile/link against the 1.2.5 Universal Headers and stubs, but it turns out there's lots of undefineds (all the ...UPP aliases for the ...Proc routines appear to have gone). > I don't know haow to get more informative error reporting from the CFM. One > thing to note is that if the name of the library is in '>> <<', it means > that the libraries initialisation routine failed - the library has actually > been found and loaded. Ah, that's an interesting bit of knowledge! How do you happen to know this? One of the lines of thought I'm persuing is that maybe I'm linking against routines in CarbonLib 1.0.4 that got dropped in later versions of CarbonLib. The CarbonLib stub I have has the cfm version information all zeroed out, so the cfm loader probably wouldn't be able to notice this problem. Maybe using stub routines that are not defined in the implementation library could cause such an initialization error? And, if it could, how could I find out which routines I'm calling that cause the problem? -- 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

2 1

CarbonLib incompatibilities
by Jack Jansen Feb. 23, 2001

Feb. 23, 2001

Folks, I'm at my wits end as to the CarbonLib incompatibilities. I've installed 9.1 on my home machine, and now indeed Carbon MacPython refuses to run. Any toy program I try runs just fine. I've started looking through the archives of Apple's Carbon Developer mailing list, but it's unsearchable, so I haven't found anything yet. If anyone has any ideas of sources of information where I could go have a look for this problem please let me know. Oh yes: if people could mail me the *exact* wording of the error message they get that would also be helpful as it would make searching easier (my system is Dutch so my error message isn't much use). Also, if someone knows of a way to get my machine to be a bit more helpful than simply saying ">>CarbonLib<<" not found or ">>CarbonLib<<" could not start that would be nice too (running under the debugger doesn't help either: the problem happens before startup). Is there a "debugging cfm", maybe? -- 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/ ++++

2 1

Some new Python How To's in German
by Jörg Kantel Feb. 23, 2001

Feb. 23, 2001

To whom it may concern ;o) in my evergrowing collection of (Mac)Python How To's I've added three new one: Grafische Ausgabe mit Python und Tkinter: <http://DerSchockwellenreiter.editthispage.com/python/pybutt.html> How To: Das Modul W oder Grafische Ausgabe in MacPython: <http://DerSchockwellenreiter.editthispage.com/python/w_intro.html> http- und ftp-User Agenten in Python: <http://DerSchockwellenreiter.editthispage.com/python/xmlrss.html> They are only in Germn (sorry) but if you can read German, enjoy it. Feedback recommended. Script different! J"org Kantel (aka Der Schockwellenreiter) -- joerg(a)kantel.de -- http://www.kantel.de/ http://DerSchockwellenreiter.editthispage.com/ -- (M)ein Weblog http://rollbergnews.editthispage.com/ -- die etwas anderen News

2 1

time and MacPython 2.1a2
by Tattoo Mabonzo K. Feb. 22, 2001

Feb. 22, 2001

Yo, I've just noticed that on Mac OS X PB, time.time() as well as some related time functions (os.path.getmtime()) return *negative* values. The doc says that time.time() expected behavior is to " Return the time as a floating point number expressed in seconds since the epoch, in UTC. Note that even though the time is always returned as a floating point number, not all systems provide time with a better precision than 1 second. " time.gmtime(0) returns (1903, 12, 31, 23, 0, 0, 3, 365, 0) which is Thu Dec 31, 1903 23:00:00 as the epoch both on Mac OS X PB et on Python 2.0 on Mac OS 9.1. I'd expect that time.time() would yield a positive value. On OS XP: t = time.time() -> -1229352415.5447249 time.asctime(time.localtime(t)) -> 'Wed Feb 21 15:41:21 2001' On Mac OS 9.1 (MacPython 2.0) t = time.time() -> 3065614820.2202692 time.asctime(time.locatime(time.time()) -> 'Wed Feb 21 15:40:20 2001' = tmk = PS: Jack, I'm cc'ing you because I don't see my posts making it to the list.

2 1

(no subject)
by Steven Burr Feb. 22, 2001

Feb. 22, 2001

> > I've just noticed that on Mac OS X PB, time.time() as well as some > > related time functions (os.path.getmtime()) return *negative* values. > > The doc says that time.time() expected behavior is to > > > > " > > Return the time as a floating point number expressed in seconds since > > the epoch, in UTC. Note that even though the time is always returned as > > a floating point number, not all systems provide time with a better > > precision than 1 second. > > " > > Oww, blech. And I just checked in a mod to the Python repository to work > around this. > > I'll have a look to see what caused the time to go negative. I think it may be > the new carbonized GUSI library we use. And yet: >>> import time >>> time.time() -1229371370.154659 >>> time.ctime(time.time()) 'Wed Feb 21 10:25:34 2001' time.localtime() returns the correct time tuple. Somehow the the other time functions are able to use the negative value from time.time() to produce the correct local calendar and clock values. I checked time.time() on the command line version of Python for Darwin, and it returns a reasonable looking positive value. BTW, I downloaded 2.1a2 this morning and am using it on a Beige G3/300/192. It's working fine, except just now when I clicked the red gumdrop to close a script window in IDE, the application "quit unexpectedly." Just the kind of thing one expects from an alpha. This is a great start for Python on Mac OSX. Thanks, Jack!

1 0

OSA Range references
by bkenniso＠att.net Feb. 21, 2001

Feb. 21, 2001

> > Bill Bedford billb(a)mousa.demon.co.uk > Wed, 21 Feb 2001 01:04:14 +0000 > > >Range in appleevents is a record (Python = dictionary) with the keys >'star' and 'stop' and the values object specifiers. Python simplifies >this to slightly in that you only have to specify the objects. So >your line should read (and I haven't tested this):- > >>>>> db.get_data(record(Range(cell(1),cell(3))) > I should have seen that the Range needs to be expressed as class objects! db.get_data(record(Range(record(1),record(3))) The above brings back the range of records that I was after. Thanks to everyone who responded, -- Brian

2 1

Re: [Pythonmac-SIG] MacPython 2.1a2 available
by Jack Jansen Feb. 21, 2001

Feb. 21, 2001

> Running the IDE I as soon as I do some editing, I get the same error: 'IndexError: list index out of range' > > 'File "Wtext.py", line 455, in can_undo > which, redo = self.ted.WEGetUndoInfo() > which = UNDOLABELS[which] Ah, this is Waste 2.0 related. WEGetUndoInfo() can return a whole lot more values. I fixed it (and made sure it won't crash in the future). -- 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

1 0

Re: [Pythonmac-SIG] MacPython 2.1a2 available
by Jack Jansen Feb. 21, 2001

Feb. 21, 2001

> Next step helping debugging EditPythonPrefs crashes. No, don't bother: it's fixed. And so is the EasyDialogs problem. It turns out that on OS9 you can pass a NULL pointer to the UPP-creation routines and you get a NULL pointer out, but not so on OSX. You get a pointer to a routine that happily jumps to address zero:-) Dlg.ModalDialog ran into this problem. I've hunted across the source for other places where this might be a problem but I didn't find any. But, of course, I may have missed some things, so if people run into crashes on OSX and it seems that it may be related to callback routines or somesuch please let me know. -- 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

1 0