From Jack.Jansen@cwi.nl Tue Jul 9 15:03:20 1996 From: Jack.Jansen@cwi.nl (Jack Jansen) Date: Tue, 09 Jul 1996 16:03:20 +0200 Subject: [PYTHONMAC-SIG] chdir(), listdir() on other volumes [was Mac Open] In-Reply-To: Message by "Steven D. Majewski" , Fri, 21 Jun 1996 14:08:29 -0400 (EDT) , Message-ID: <9607091403.AA01629=jack@schelvis.cwi.nl> Recently, "Steven D. Majewski" said: > > > While we're on the subject, Yet Another Mac pathname gotcha : > > I was going crazy trying to chdir() onto another volume, with > no luck. I was about to finally decide that it *wasn't* a pathname > syntax problem, but a bug in the Python code, when I noted that > getbootvol() returns the name with a *TRAILING* ":" -- which is > not how the volumes are displayed when you chdir all the way to > the root and do a listdir(). This is interesting, I never knew of the "virtual" toplevel above all disks! Still, it is reasonable that listdir() returns the names without trailing colon even here: otherwise any pathname manipulating routines would become even more complicated than they already are... Now that we're on the subject of pathnames, there's something else that bothers me: if I read the docs correctly MacOS doesn't mind in the least if you have two disks with the same name (apparently it can't get confused, because it uses FSSpecs everywhere internally). Anyone feel like trying out how Python reacts to having two disks with the same name mounted? -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen@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@python.org administrivia to: pythonmac-sig-request@python.org ================= From Jack.Jansen@cwi.nl Tue Jul 9 15:03:20 1996 From: Jack.Jansen@cwi.nl (Jack Jansen) Date: Tue, 09 Jul 1996 16:03:20 +0200 Subject: [PYTHONMAC-SIG] chdir(), listdir() on other volumes [was Mac Open] In-Reply-To: Message by "Steven D. Majewski" , Fri, 21 Jun 1996 14:08:29 -0400 (EDT) , Message-ID: <9607091403.AA01629=jack@schelvis.cwi.nl> Recently, "Steven D. Majewski" said: > > > While we're on the subject, Yet Another Mac pathname gotcha : > > I was going crazy trying to chdir() onto another volume, with > no luck. I was about to finally decide that it *wasn't* a pathname > syntax problem, but a bug in the Python code, when I noted that > getbootvol() returns the name with a *TRAILING* ":" -- which is > not how the volumes are displayed when you chdir all the way to > the root and do a listdir(). This is interesting, I never knew of the "virtual" toplevel above all disks! Still, it is reasonable that listdir() returns the names without trailing colon even here: otherwise any pathname manipulating routines would become even more complicated than they already are... Now that we're on the subject of pathnames, there's something else that bothers me: if I read the docs correctly MacOS doesn't mind in the least if you have two disks with the same name (apparently it can't get confused, because it uses FSSpecs everywhere internally). Anyone feel like trying out how Python reacts to having two disks with the same name mounted? -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen@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@python.org administrivia to: pythonmac-sig-request@python.org ================= From Jack.Jansen@cwi.nl Fri Jul 12 21:57:07 1996 From: Jack.Jansen@cwi.nl (Jack Jansen) Date: Fri, 12 Jul 1996 22:57:07 +0200 Subject: [PYTHONMAC-SIG] What is needed for MacPython 1.4? Message-ID: <9607122057.AA00520=jack@schelvis.cwi.nl> Folks, if people have simple wishes for what should be included in MacPython 1.4 (based on what is available in 1.3.3): let me know. I'm thinking here of modules like the software developed by the image or numerics SIG, not of things that I would have to actually program myself:-) Also, have people looked at the documentation and examples in 1.3.3? Anything critical missing? Anyone who has examples to add? -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen@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@python.org administrivia to: pythonmac-sig-request@python.org ================= From Jack.Jansen@cwi.nl Sun Jul 14 22:42:04 1996 From: Jack.Jansen@cwi.nl (Jack Jansen) Date: Sun, 14 Jul 1996 23:42:04 +0200 Subject: [PYTHONMAC-SIG] What is needed for MacPython 1.4? In-Reply-To: Message by da@maigret.cog.brown.edu (David Ascher) , Fri, 12 Jul 1996 17:18:28 -0400 (EDT) , <199607122118.RAA18232@maigret> Message-ID: <9607142142.AA14633=jack@schelvis.cwi.nl> Recently, da@maigret.cog.brown.edu (David Ascher) said: > Does this mean that you'll make NumPython-aware versions available? If there is enough demand: yes, why not? It does depend, however, on it not being too much work (or on someone else doing the work:-). David, since you appear to be following the NumPython stuff: would it be possible to ship the numeric extensions as a dynamically loadable module? I.e. are there no changes in the python core (syntax, etc)? > PS: I don't know enough about modern Mac OS'es to know: is the DLL/DSO > setup on macs fairly similar to that on Unix/Win32/NT? In other > words, can one ship python modules as binary dynamically loaded > libraries? Yes, for PowerPC the MacOS shared libraries are effectively similar to what is available on unix or NT. For 68K macintoshes there is a problem, though: Apple provide CFM68K which gives you this architecture on 68K macs, but support for it in the Metrowerks compiler was sub-optimal when I last tried it. I haven't given it a shot yet with CW8 or CW9 since I was too busy with other things (and I'd already tried with no success with CW6 and CW7). Has anyone tried to build a CFM68K Python? -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen@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@python.org administrivia to: pythonmac-sig-request@python.org ================= From Jack.Jansen@cwi.nl Sun Jul 14 22:55:49 1996 From: Jack.Jansen@cwi.nl (Jack Jansen) Date: Sun, 14 Jul 1996 23:55:49 +0200 Subject: [PYTHONMAC-SIG] chdir() and Standard File Message-ID: <9607142155.AA14682=jack@schelvis.cwi.nl> A design question: speak up now or forever hold your silence:-) Currently, the Standard File working directory and the "other" working directory (i.e. what you set with os.chdir() and what relative paths are relative to) are completely separated. This has the advantage that python programs have a "MacOS feel", i.e. the initial macfs.StandardGetFile dialog will come up in the place people expect from other mac programs. On the other hand it feels strange to Python: you chdir() somewhere and ask the user for a file, but it comes up in a different folder from where you just chdir'd to. Possibilities: - keep it as it is (chdir and Standard File completely uncoupled) - make them tightly coupled (chdir immedeately changes Standard File folder) - make them optionally coupled (setting "macfs.followchdir" to one makes Standard File follow chdir) - create macfs.chdir() which would set Standard File working directory. I'd personally be in favor of the last solution, but let's hear other people's opinions. -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen@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@python.org administrivia to: pythonmac-sig-request@python.org ================= From just@knoware.nl Sun Jul 14 23:53:48 1996 From: just@knoware.nl (Just van Rossum) Date: Mon, 15 Jul 1996 00:53:48 +0200 Subject: [PYTHONMAC-SIG] chdir() and Standard File Message-ID: Jack, At 11:55 PM 7/14/96, Jack Jansen wrote: >Currently, the Standard File working directory and the "other" working >directory (i.e. what you set with os.chdir() and what relative paths >are relative to) are completely separated. This has the advantage that >python programs have a "MacOS feel", i.e. the initial >macfs.StandardGetFile dialog will come up in the place people expect >from other mac programs. On the other hand it feels strange to Python: >you chdir() somewhere and ask the user for a file, but it comes up in >a different folder from where you just chdir'd to. > >Possibilities: >- keep it as it is (chdir and Standard File completely uncoupled) No! (err, yes but...) >- make them tightly coupled (chdir immedeately changes Standard File > folder) No! Either way it will confuse users. >- make them optionally coupled (setting "macfs.followchdir" to one > makes Standard File follow chdir) Hmm... nah. >- create macfs.chdir() which would set Standard File working > directory. Yes! That way it will be easy to implement this: when you choose "Save As..." you automatically get to the folder where the original file lives. I hate it when apps send you to the apps' home folder when you choose "Save As..." after doubleclicking a document... And you'd be independent of os.chdir(), which might be used for other reasons (like if you import modules that live in the same directory as __main__ and that directory is not in the Python search path). It should be clearly documented to avoid confusion. (but I guess you knew my point of view somehow...) Just ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig@python.org administrivia to: pythonmac-sig-request@python.org ================= From hansbo@math.chalmers.se Tue Jul 16 08:46:25 1996 From: hansbo@math.chalmers.se (Peter Hansbo) Date: Tue, 16 Jul 1996 09:46:25 +0200 (MET DST) Subject: [PYTHONMAC-SIG] What is needed for MacPython 1.4? Message-ID: <199607160746.JAA02141@jacobi.math.chalmers.se> > Folks, > if people have simple wishes for what should be included in MacPython 1.4 > (based on what is available in 1.3.3): let me know. I'm thinking here > of modules like the software developed by the image or numerics SIG, > not of things that I would have to actually program myself:-) Just let me cast my vote for a numeric+Tkinter version. I could really use that! ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig@python.org administrivia to: pythonmac-sig-request@python.org ================= From dave@zeus.hud.ac.uk Wed Jul 17 10:00:49 1996 From: dave@zeus.hud.ac.uk (Dave Dench) Date: Wed, 17 Jul 96 09:00:49 BST Subject: [PYTHONMAC-SIG] What is needed for MacPython 1.4? Message-ID: <9607170800.AA01534@zeus.hud.ac.uk> > From owner-pythonmac-sig@python.org Tue Jul 16 14:13:31 1996 > From: Peter Hansbo > Date: Tue, 16 Jul 1996 09:46:25 +0200 (MET DST) > To: pythonmac-sig@python.org > Subject: Re: [PYTHONMAC-SIG] What is needed for MacPython 1.4? > Content-Md5: r7/pzF+uLvaJU/pCLWJp+Q== > Sender: owner-pythonmac-sig@python.org > Mime-Version: 1.0 > Content-Type> : > text/plain> ; > charset="us-ascii"> > Content-Length: 563 > > > Folks, > > if people have simple wishes for what should be included in MacPython 1.4 > > (based on what is available in 1.3.3): let me know. I'm thinking here > > of modules like the software developed by the image or numerics SIG, > > not of things that I would have to actually program myself:-) > > > > Just let me cast my vote for a numeric+Tkinter version. I could > really use that! > Ditto, + PIL (of course)! ________________________________________________________________________________ ************************************************ * David Dench * * The University of Huddersfield , UK * * Tel: 01484 472083 * * email: dave@zeus.hud.ac.uk * ************************************************ ________________________________________________________________________________ ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig@python.org administrivia to: pythonmac-sig-request@python.org ================= From powers@petroglyph.com Wed Jul 17 19:49:37 1996 From: powers@petroglyph.com (Michael Powers) Date: Wed, 17 Jul 1996 11:49:37 -0700 Subject: [PYTHONMAC-SIG] What is needed for MacPython 1.4? Message-ID: How about connecting the new Game Sprockets libraries from Apple. There is the combination of NetSprockets, 3DSprockets, InputSprockets, and SoundSprockets. Make Python a new media savvy language?! Mike www.dev.apple.com ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig@python.org administrivia to: pythonmac-sig-request@python.org ================= From Jack.Jansen@cwi.nl Wed Jul 17 21:45:37 1996 From: Jack.Jansen@cwi.nl (Jack Jansen) Date: Wed, 17 Jul 1996 22:45:37 +0200 Subject: [PYTHONMAC-SIG] What is needed for MacPython 1.4? In-Reply-To: Message by powers@petroglyph.com (Michael Powers) , Wed, 17 Jul 1996 11:49:37 -0700 , Message-ID: <9607172045.AA08357=jack@schelvis.cwi.nl> Okay, here's what I'll do before 1.4 (which, as you can see will have very little changes over 1.3.3, except for the machine-independent stuff): - Add a stackcheck occasionally (probably when the cmd-dot check is done), - Add macfs.chdir() - Add PIL - Check how much work adding the numeric stuff is. - Add some stuff Just did, if it is finished and OK with him (the class browser, a much nicer EditPythonPrefs). - See if there is some way to make tcl/tk a better citizen memory-wise (even if I can only make python crash with an "out of memory" dialog it would be better than the current situation). The sprocket stuff I haven't looked at at all, maybe someone else could have a look whether this is (a) interesting and (b) implementable? Also, if someone feels the urge to have a look at a CFM68K python (how come I have this deja-vu feeling:-): please please please. Oh yes: nobody had any comments on the documentation and examples. Does this mean nobody looked at them or that everyone loves it as it is? -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen@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@python.org administrivia to: pythonmac-sig-request@python.org ================= From da@maigret.cog.brown.edu Thu Jul 18 20:18:54 1996 From: da@maigret.cog.brown.edu (David Ascher) Date: Thu, 18 Jul 1996 15:18:54 -0400 (EDT) Subject: [PYTHONMAC-SIG] What is needed for MacPython 1.4? In-Reply-To: <9607142142.AA14633=jack@schelvis.cwi.nl> from "Jack Jansen" at Jul 14, 96 11:42:04 pm Message-ID: <199607181918.PAA02725@maigret> > If there is enough demand: yes, why not? It does depend, however, on > it not being too much work (or on someone else doing the > work:-). David, since you appear to be following the NumPython stuff: > would it be possible to ship the numeric extensions as a dynamically > loadable module? I.e. are there no changes in the python core (syntax, > etc)? Sorry for the delay. There are changes to the python core in 1.3 -- I don't know if 1.4 includes all the necessary changes. Might want to ask Guido about that. --david ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig@python.org administrivia to: pythonmac-sig-request@python.org ================= From Jack.Jansen@cwi.nl Sun Jul 21 22:54:46 1996 From: Jack.Jansen@cwi.nl (Jack Jansen and/or Erika Mesters) Date: Sun, 21 Jul 1996 23:54:46 +0200 Subject: [PYTHONMAC-SIG] Sprocket support Message-ID: I had a quick look through the apple sprocket documentation (from the Apple developers website), and it does indeed look interesting! For those here that haven't check it out yet: the sprocket stuff is a set of toolboxes that allow programmers (the main market is game programmers, but I think lots of other people would be interested too) to do common things in a simple way, without having to worry about details like network protocols, display types, etc.. The currently available sprockets are - netsprockets, which allow you to implement multi-player games over any network, enter/leave/host games, send messages to groups, etc. - sound sprockets allow you to have 3-d localization of sounds - display (or was that graphics??) sprockets give you an easy all-black screen, do 256/thousand/millions color switching, colormap fiddling. - input sprockets give access to input devices like joysticks, or emulates them with existing devices. I checked out the netsprockets and the design looks nice and clean, and easy to implement with bgen. It also feels "pythonish", in that things are opaque whenever possible, etc. So, I'm tempted to do a bgen-generated interface to the sprocket libraries, but I have one problem: I don't have an application for sprockets at the moment (although one will probably come up as soon as they're implemented). So, here's the offer: if someone is willing to look into sprockets, help me design the "right" python interface and develop some (toy?) applications I'll mumble the secret incantations needed to get bgen to do its work. Any takers? -- Jack Jansen, jack@cwi.nl. Currently at home and, thus, without Emma Goldman quote (the neigbours don't like dancing:-) ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig@python.org administrivia to: pythonmac-sig-request@python.org ================= From evb@knoware.nl Mon Jul 22 01:27:18 1996 From: evb@knoware.nl (Erik van Blokland) Date: Mon, 22 Jul 96 02:27:18 +0200 Subject: [PYTHONMAC-SIG] Sprocket support Message-ID: <199607220026.CAA23230@kalvermarkt.denhaag.dataweb.net> >So, here's the offer: if someone is willing to look into sprockets, help me >design the "right" python interface and develop some (toy?) applications >I'll mumble the secret incantations needed to get bgen to do its work. I don't know how complicated it would be compared to my still infant knowledge of python, but the things you mention are interesting, and I definitely would be interested if it were there (network toys, stuff). I don't know of I could help you _make_ it though :( Probably not the answer you need.. erik erik van blokland, LettError What's wrong with my sigfile? letterror http://www.letterror.com typelab http://www.dol.com/TypeLab/ ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig@python.org administrivia to: pythonmac-sig-request@python.org ================= From powers@petroglyph.com Tue Jul 23 20:43:12 1996 From: powers@petroglyph.com (Michael Powers) Date: Tue, 23 Jul 1996 12:43:12 -0700 Subject: [PYTHONMAC-SIG] Sprocket support Message-ID: Jack, >So, I'm tempted to do a bgen-generated interface to the sprocket libraries, >but I have one problem: I don't have an application for sprockets at the >moment (although one will probably come up as soon as they're implemented). >So, here's the offer: if someone is willing to look into sprockets, help me >design the "right" python interface and develop some (toy?) applications >I'll mumble the secret incantations needed to get bgen to do its work. > >Any takers? > Ah, music to my ears. I run a game company called Headgames, L.L.C. that produces primarily for the PC. I have been looking for an avenue onto the Mac platform for some time but publishers are very skittish about the finances. With Python connected to the Sprockets library the case looks better. So, I volunteer to do some decent toy applications (3D pong perhaps to start with). I am not a Mac programmer, although I and my staff are strong in Python. I also have years of experience in C++ and Lisp. At Headgames we have some good 3D modelers and such. Sprockets, I believe, runs on Mac and PC so if we can create a Python connection that is crossplatform it would be a stupendous achievement for those of us who like 3D visuals! I will dig around more on the game dev website. One additional benefit is that I know the head of the game SDK division personally so we could even get support if we need it from Apple! Mike ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig@python.org administrivia to: pythonmac-sig-request@python.org ================= From Jack.Jansen@cwi.nl Wed Jul 31 12:13:10 1996 From: Jack.Jansen@cwi.nl (Jack Jansen) Date: Wed, 31 Jul 1996 13:13:10 +0200 Subject: [PYTHONMAC-SIG] Removing modules from python Message-ID: <9607311113.AA21918=jack@schelvis.cwi.nl> I'm looking at making the next Python distribution smaller by removing things that I feel aren't very useful (and probably not used at all). If I were to remove the following modules from the next MacPython release, would anyone be bothered by this? Or should I make Mac distributions with as many modules as possible? - mactcp/macdnr (socket provides the same functionality) - macspeech (incomplete, and should be bgen-generated) - ctb (idem) Note that even if I remove them they'll still be available in the source distribution, so people who really want them could still use them... -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen@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@python.org administrivia to: pythonmac-sig-request@python.org ================= From jstrout@ucsd.edu Wed Jul 31 15:45:20 1996 From: jstrout@ucsd.edu (Joseph Strout) Date: Wed, 31 Jul 1996 07:45:20 -0700 (PDT) Subject: [PYTHONMAC-SIG] Removing modules from python In-Reply-To: <9607311113.AA21918=jack@schelvis.cwi.nl> Message-ID: On Wed, 31 Jul 1996, Jack Jansen wrote: > I'm looking at making the next Python distribution smaller by removing > > - mactcp/macdnr (socket provides the same functionality) > - macspeech (incomplete, and should be bgen-generated) > - ctb (idem) How about making them available (without the source) as more-modules.hqx or some such? I sometimes use macspeech, though I could do without the others... ,------------------------------------------------------------------. | Joseph J. Strout Department of Neuroscience, UCSD | | jstrout@ucsd.edu http://www-acs.ucsd.edu/~jstrout/ | `------------------------------------------------------------------' ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig@python.org administrivia to: pythonmac-sig-request@python.org ================= From mike@xochi.com Wed Jul 31 17:20:09 1996 From: mike@xochi.com (Michael Diehr) Date: Wed, 31 Jul 1996 09:20:09 -0700 Subject: [PYTHONMAC-SIG] Removing modules from python Message-ID: >I'm looking at making the next Python distribution smaller by removing >things that I feel aren't very useful (and probably not used at all). >If I were to remove the following modules from the next MacPython >release, would anyone be bothered by this? Or should I make Mac >distributions with as many modules as possible? > >- mactcp/macdnr (socket provides the same functionality) >- macspeech (incomplete, and should be bgen-generated) >- ctb (idem) > >Note that even if I remove them they'll still be available in the >source distribution, so people who really want them could still use >them... >-- >Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ >Jack.Jansen@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 > I was wondering if it was possible to fold the python interpreter into some of my code for use as a scripting language? I'd want the smallest subset possible (probably just the basic language plus string commands). Has anyone experimented with this? I'm looking for a target size of under 64K for the interpreter. Thanks -- Michael Diehr E-mail : mike@xochi.com Xochi Media WWW : http://www.xochi.com/ 3123 SW Dolph Ct #1 Voice : +1.503.293.9268 Portland, OR 97219-3846 Fax : +1.503.245.1859 ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig@python.org administrivia to: pythonmac-sig-request@python.org ================= From Jack.Jansen@cwi.nl Wed Jul 31 22:29:01 1996 From: Jack.Jansen@cwi.nl (Jack Jansen) Date: Wed, 31 Jul 1996 23:29:01 +0200 Subject: [PYTHONMAC-SIG] Tiny python In-Reply-To: Message by mike@xochi.com (Michael Diehr) , Wed, 31 Jul 1996 09:20:09 -0700 , Message-ID: <9607312129.AA28120=jack@schelvis.cwi.nl> Recently, mike@xochi.com (Michael Diehr) said: > I was wondering if it was possible to fold the python interpreter into some > of my code for use as a scripting language? I'd want the smallest subset > possible (probably just the basic language plus string commands). Has > anyone experimented with this? I'm looking for a target size of under 64K > for the interpreter. Hmm, 64K is *very* small. Unless you do some very heavy hacking you will need everything from the Parser, Python, Objects and Mac/Python directories, and there are probably some things in Modules too that you might theoretically live without but need in practice. I wouldn't give you much chance of a Python of less that about 200K, but this is pure guesswork. Why don't you ask again on the full python-list/comp.lang.python? The problem isn't mac-specific, I guess... -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen@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@python.org administrivia to: pythonmac-sig-request@python.org =================