🌐 Mailman 3 - Pythonmac-SIG - python.org

Re: [PYTHONMAC-SIG] Compile under CW8?
by guzdial＠cc.gatech.edu April 1, 1996

April 1, 1996

At 5:34 PM 3/30/96, Jack Jansen wrote: >Ok, for the next release I'll make a source distribution available >too. What do people want: a mean-and-lean Python-only distribution, >one including everything else you need (stdwin, pbm/jpeg/etc >libraries, gusi) or both? I vote for everything -- Tk, too! (Thanks, Dennis, for the suggestion of looking up SunTar. I'll do that. Currently, I'm just using 'tar' -- a real small, simple freeware thing that does a reasonable job.) Mark -------------------------- Mark Guzdial : Georgia Tech : College of Computing : Atlanta, GA 30332-0280 (404) 894-5618 : Fax (404) 894-0673 : guzdial(a)cc.gatech.edu http://www.cc.gatech.edu/gvu/people/Faculty/Mark.Guzdial.html ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig(a)python.org administrivia to: pythonmac-sig-request(a)python.org =================

3 2

Re: [PYTHONMAC-SIG] Compile under CW8?
by just＠knoware.nl April 1, 1996

April 1, 1996

>I vote for everything -- Tk, too! (Thanks, Dennis, for the suggestion of >looking up SunTar. I'll do that. Currently, I'm just using 'tar' -- a >real small, simple freeware thing that does a reasonable job.) I guess even suntar cannot solve the problem with long filenames. I use the py documentation as html off line, but some of the file names are too long. Quite a problem, because even when I get those files, all the links to them don't work. Specific sad example: Macintosh_Specific_Services.html Is this fixable in the next release? Just | |- -|--|- |- |-\ |-\ /-\ |-\ http://www.letterror.com/ | |- | | |- |-/ |-/ | | |-/ |- |- | | |- | | | | \-/ | | ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig(a)python.org administrivia to: pythonmac-sig-request(a)python.org =================

1 0

Re: [PYTHONMAC-SIG] Compile under CW8?
by demars＠netcom.com March 30, 1996

March 30, 1996

>Ok, for the next release I'll make a source distribution available >too. What do people want: a mean-and-lean Python-only distribution, >one including everything else you need (stdwin, pbm/jpeg/etc >libraries, gusi) or both? >-- >Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ >Jack.Jansen(a)cwi.nl | ++++ if you agree copy these lines to your sig ++++ >http://www.cwi.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm > >================= >PYTHONMAC-SIG - SIG on Python for the Apple Macintosh > >send messages to: pythonmac-sig(a)python.org >administrivia to: pythonmac-sig-request(a)python.org >================= I think that would be great! Personally I'd like to have everything, ready to build with CW8. I recently made a build of the standard 1.3 distribution. (I did this because I wanted to play with the Numerical Python extensions, so I had to fold that source in to build for the Mac). I eventually got it to work, but there were some anomalies that might be due to something about the CW libraries and the way CW builds shared libraries that changed between when Python 1.3 was released and the standard distribution. F'rinstance, I had to comment out the __sinit routine in Python 1.3 since the CW8 linker seems to insist on generating its own and then complaining about the multiply-defined symbol. Also, I could not get the linker to stop pulling in the __start module from the library (even though I didn't fill in __start in the linker options) and since the standard __start has a call to "main," I had to put a dummy "main" routine in, which got put into PythonCore. Then, when I linked the Python app (which has the _real_ main routine) it complained about the extra main, but it was just a warning, and the correct main got linked in, so everything worked after that, but even so, I obviously was doing something not quite right! I had other problems before that, but I think those were mostly due to my not following the suggestion of where in the folder hierarchy to put the project files before building, and therefore having incorrect access paths set up initially. Also, some of the other 1.3 project files for building some of the optional Mac oriented modules seemed to be inconsistent or incomplete, referring to files that didn't seem to be present in the 1.3 distribution. Anyhow, if we could get a fresh source distribution with all of the necessary parts to do a build with CW8 I'd be very grateful (then I could do a grand unified build with all of the numerical stuff, Tk support, etc.) GUSI adds quite a bit to the size of the download, and I've probably got the most recent version anyway, so you might want to make a version available with URLs to any source that is publically available else. On the other hand, if the only version was with all the other stuff thrown in, I wouldn't mind downloading some redundant pieces (and of course the advantage of that is that the other pieces are being revised continuously, so one might not grab the correct version if having to go to different sites to collect it all -- having all source in one distribution assures that everything is consistent). - Dennis D. ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig(a)python.org administrivia to: pythonmac-sig-request(a)python.org =================

1 0

Re: [PYTHONMAC-SIG] Compile under CW8?
by guzdial＠cc.gatech.edu March 30, 1996

March 30, 1996

>Hmm. I could do this, but is there a point? The full source >distribution contains everything you need. There were some minor >problems with the "current" distribution (i.e. the 1.3 distribution as >it sits on the servers right now), and there was no mac-specific >readme file, but apart from that the unix distribution should work fine.... I guess it's just a user-interface/audience-type thing. I'm not a UNIX user, generally speaking, nor am I skilled at CodeWarrior. So, when I tried to grab the 1.3 distribution, I found that I couldn't de-tar it on my Mac because the filenames were too long. So, I grabbed the file again on my UNIX account and de-tarred it there. Now, I had to figure out which pieces to grab. The readme talked about grabbing these directories, but not these others. Faced with moving things back to my Mac and unsure which pieces were which, I surrendered. I'd be very interested in exploring the source code to Python on my Mac, and since people obviously must have gone through these various manipulations in order to get it in CodeWarrior format, I'm simply asking if someone could upload that. If it's too much bother, no problems -- thanks! Mark -------------------------- Mark Guzdial : Georgia Tech : College of Computing : Atlanta, GA 30332-0280 (404) 894-5618 : Fax (404) 894-0673 : guzdial(a)cc.gatech.edu http://www.cc.gatech.edu/gvu/people/Faculty/Mark.Guzdial.html ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig(a)python.org administrivia to: pythonmac-sig-request(a)python.org =================

2 1

Re: [PYTHONMAC-SIG] Compile under CW8?
by guzdial＠cc.gatech.edu March 26, 1996

March 26, 1996

BTW, can anyone post an archive of the Mac sources? I downloaded the distribution once, de-tarred it, and tried to pick out the pieces, but just got lost. A CW8-compilable archive would be wonderful. Thanks! Mark P.S. I do educational technology research, and my first Python-based tool goes into the classroom tomorrow! >Recently, gandreas(a)skypoint.com (Glenn Andreas) said: >> >> Has anybody gotten a stock 1.3 to compile under CW8? It use to work fine >> under CW7, but now compiling ceval.c hangs the compiler. > >Try lowering the optimization level. I had to do the same on my home >machine (although it didn't hang the machine, it just aborted). >-- >Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ >Jack.Jansen(a)cwi.nl | ++++ if you agree copy these lines to your sig ++++ >http://www.cwi.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm > >================= >PYTHONMAC-SIG - SIG on Python for the Apple Macintosh > >send messages to: pythonmac-sig(a)python.org >administrivia to: pythonmac-sig-request(a)python.org >================= -------------------------- Mark Guzdial : Georgia Tech : College of Computing : Atlanta, GA 30332-0280 (404) 894-5618 : Fax (404) 894-0673 : guzdial(a)cc.gatech.edu http://www.cc.gatech.edu/gvu/people/Faculty/Mark.Guzdial.html ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig(a)python.org administrivia to: pythonmac-sig-request(a)python.org =================

2 1

CGI scripting in python
by Jack Jansen March 26, 1996

March 26, 1996

Has anyone looked at writing CGI scripts in Python, by any chance? -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen(a)cwi.nl | ++++ if you agree copy these lines to your sig ++++ http://www.cwi.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig(a)python.org administrivia to: pythonmac-sig-request(a)python.org =================

1 0

Re: [PYTHONMAC-SIG] Compile under CW8?
by gandreas＠skypoint.com March 21, 1996

March 21, 1996

> > gandreas(a)skypoint.c writes: > : Has anybody gotten a stock 1.3 to compile under CW8? It use to work fine > : under CW7, but now compiling ceval.c hangs the compiler. > > I've seen CW8 hang when compiling ceval.c on a 6100 with optimization on. > I can compile it just fine on a 6100 and a 9500 with optimization off. > > The hang seems new to this version of CW. > > -jeff stearns > Well, strange as it may seem, this was a bit of a false alarm. It does compile fine, but it takes several minutes! I was just so use to nothing taking more than five seconds that after thirty seconds I paniced (I'm sure there is an important lesson here). I spent several hours commenting out various chunks of the routine, and noticed that it would work, but it sometimes took a while (but far enough below my panic threshold to not cause me to kill it). And while I had all optimizations on, I'm not convinced that that is related, since I got the same behaviour if I only did "Check Syntax" (which I assumed would not generate code, much less optimize it, unless some of the optimizations are done in then). So, everything is OK, and I didn't just go temporarily insane. Back to thinking about SOM wrappers for OpenDoc... Glenn Glenn Andreas Author of Macintosh games: gandreas(a)skypoint.com, gandreas(a)aol.com Theldrow 2.3 http://www.skypoint.com/members/gandreas Blobbo 1.0.1 ftp://ftp.skypoint.com/pub/members/g/gandreas <---- Available here! ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig(a)python.org administrivia to: pythonmac-sig-request(a)python.org =================

1 0

Compile under CW8?
by gandreas＠skypoint.com March 21, 1996

March 21, 1996

Has anybody gotten a stock 1.3 to compile under CW8? It use to work fine under CW7, but now compiling ceval.c hangs the compiler. Everything else works, but something in the main interp routine kills it (even if I just "check syntax"). I've tried turning on CASE_TOO_BIG, but this doesn't help either - it still dies somewhere in eval_code2. (commenting the whole routine out has it working fine, but that doesn't help much). Glenn Glenn Andreas Author of Macintosh games: gandreas(a)skypoint.com, gandreas(a)aol.com Theldrow 2.3 http://www.skypoint.com/members/gandreas Blobbo 1.0.1 ftp://ftp.skypoint.com/pub/members/g/gandreas <---- Available here! ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig(a)python.org administrivia to: pythonmac-sig-request(a)python.org =================

3 2

Announce: TkPython for 68k and PPC available
by Jack Jansen March 7, 1996

March 7, 1996

I've built a PPC python with Tk as a dynamically loadable extension, available in <ftp://ftp.cwi.nl/pub/jack/python/mac>. For sake of completeness, I've also put a 68K distribution there, some bugs with regard to funny working directory behaviour were fixed since Guido built his 68K TkPython distribution. These are complete self-contained distributions. They should be regarded as alpha-test software, even if you are not using the Tk stuff: the I/O system is based on the GUSI library, and I've only been using it for a few weeks so not everything may work as expected. Another warning is also in place here: these distributions use 'Pyth' as creator-code in stead of 'PYTH'. A script is included to automatically change your old python files, but if you decide to go back to 1.3 or 1.3.1 you'll have to modify the script to do the reverse operation. I'll leave you all to look at this stuff for a week or so before I advertise it to a larger audience. In that time I may replace the archives with newer versions if bug reports come in. -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen(a)cwi.nl | ++++ if you agree copy these lines to your sig ++++ http://www.cwi.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig(a)python.org administrivia to: pythonmac-sig-request(a)python.org =================

1 0

Re: [PYTHONMAC-SIG] Forwarded message: extension module
by Jack Jansen March 7, 1996

March 7, 1996

> > Here is what I did: > * Wrote a tiny module with just one function (source is included at the end.) > Source file name: "myfirstmodule.c", shared lib name: > "myfirstmodule". The library name should end in .slb, as you already noted. > * Copied the CW7 PythonCore project file, removed the sources from that and > added my module source file (retained the run-time and shared lib glue stuff). This is probably not the best way to do it. There is a skeleton project file xxmodule.{mu} that is ready for use. One thing to keep in mind (it recently bit me): if your extension module contains C++ code anywhere you will have to supply a PEF init function that (at the very least) calls __sinit() to do C++ static initializers. The MetroWerks documentation has details. > * Built the shared lib successfully and copied it to the system extension > folder. It shouldn't go into the extension folder, you should put it somewhere along sys.path. "PlugIns" is the standard place. This whole process, by the way, is documented since a few months, check out <http://www.cwi.nl/~jack/macpython/>. Besides this extension example it also has some stuff on using toolbox calls and appleevents from python. -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen(a)cwi.nl | ++++ if you agree copy these lines to your sig ++++ http://www.cwi.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig(a)python.org administrivia to: pythonmac-sig-request(a)python.org =================

1 0