Mailman 3 December 1999 - Pythonmac-SIG

newbie's Q
by KAWASAKI April 25, 2000

April 25, 2000

hello,all I am a newbie to mac python. when I double click a module in whatever folder the interpreter says to me it can't find the module. for example. Double click $PYTHON:Lib:binhex.py --->PythonInterpreter:: can't open file 'binhex.py:' I can import the binhex.py from the interpreter command line. I suspect it is not a problem of path settings.( indeed $PYTHON:Lib: is in the path) I thought I had no trouble when I was using ver 1.4 Please tell me what's wrong. Thank you in advance.

3 2

Director Xtra "Xpython" for MAC + Time Manager module
by Steve Spicklemire Dec. 31, 1999

Dec. 31, 1999

Just in time for the new millennium... there is a new stab at a Python Xtra for Director and a "Time Manager" module for MacPython. For some reason I can't get these to work with 1.5.2c1 anymore, since I built with the CVS sources, but they *do* work with the Python I built with CVS. In any case I've put the whole lot up at: http://opensource.spvi.com and you can check it out there. Please let me know if any of this stuff works, doesn't or whatever. Thanks also to Jack and Peter for all their help sorting out my various build problems. I'd like to get to the point where I can build something (like a dynamically linkable module) that can be used with 1.5.2b1, 1.5.2cx and 1.5.2c+ without a recompile ;-(. take care, -steve

1 0

Re: [Pythonmac-SIG] Cooperative threading on Mac (was: playing well with others (newbie question))
by Jack Jansen Dec. 31, 1999

Dec. 31, 1999

Recently, Skip Montanaro <skip(a)mojam.com> said: > > (I've redirected this from the main list to the PythonMac-SIG.) > > Michael> I'm stuck with the following problem with python 1.5.2c1 on > Michael> MacOS 8.6: > > Michael> while 1: > Michael> pass > > Michael> grinds my system to a halt. In other languages there are > Michael> commands that give away cycles to the rest of the system and > Michael> thus "playing well with others." Is there some similar command > Michael> in python? Something to replace that pass with that allows me > Michael> to do other things with my system? > > The code that implements pass in ceval.c could easily be modified to > periodically call whatever Mac toolbox function is used to release the > processor. That code is indeed in place (unless you specifically disable it by calling MacOS.SchedParams() with various arguments to turn it off). You can also use SchedParams() to change the actual allocation of cycles to others when Python is in foreground or background (default is pretty greedy in the foreground, not greedy in the background). There does seem to be a bug in the current release, though, that I haven't seen before: when you switch to a background application this causes Python to monopolize the CPU for 15 seconds (not even the clock runs). After that everything is as sketched above. I will investigate what is going on. > Unfortunately, the Mac-specific source code seems not to be > under CVS control, so while I can see some tantalizing hints of what needs > doing in the source on my Linux machine, I can't suggest anything specific. MacPython is under CVS, see the homepage (http://www.cwi.nl/~jack/macpython.html) for details. -- 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] Library "too new"?
by Jack Jansen Dec. 31, 1999

Dec. 31, 1999

Recently, Skip Montanaro <skip(a)mojam.com> said: > What's this mean? > > >>> import DateTime > ... > ImportError: PythonCore: An import library was too new for a client. > > This is using the precompiled mxDateTime module that comes with the > mxDateTime package. MacPython dynamic modules aren't portable between releases. The machinery is there, but because PythonCore also contains the whole C library the version number has to be upped not only for python API version number changes but also for new C libraries. The error message comes from the MacOS dynamic loader, which actually _checks_ that a dll is compatible with the version used during compilation (unlike some Other OS that shall remain nameless, which happily lets your application crash lateron:-) Or, in short: the message means exactly what it says:-) -- 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] [Q] how to disable stderr/stdout console?
by Jack Jansen Dec. 31, 1999

Dec. 31, 1999

Recently, Glenn Andreas <gandreas(a)visi.com> said: > >I was already going to change this, by adding a do_init_toolbox > >argument to PyMac_Initialize(), but then I remembered (or seem to > >remember:-) that multiple toolbox initializations shouldn't do any > >harm. And as PyMac_Initialize needs (some of) the toolboxes to be initialize > d > >the only option your program has is to initialize them earlier, in > >which case the init_mac_world() call in PyMac_Initialize is a no-op. > > Unless somebody wants to write a faceless background only application > that uses Python, since BOAs don't call all the toolbox init calls > (they don't call InitMenu() or InitWindow(), IIRC). Ah... I experimented with FBAs in Python for a while, but I never got them to work. This may be the reason why. I think this could be fixed by splitting the toolbox init calls in two sets: one to be done always, at the same place where currently everything is initialized, and one for the menu/window/etc init calls, to be done after reading the preferences but before popping the optional startup dialog. That way we can add a (per-application) preference flag "don't init windowing toolboxes", which could be set for FBA's (or by programs using embedded Python). I'll put it on my todo list, but it's low-priority, so if someone wants it quick: please donate code. -- 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

Cooperative threading on Mac (was: playing well with others (newbie question))
by Skip Montanaro Dec. 30, 1999

Dec. 30, 1999

(I've redirected this from the main list to the PythonMac-SIG.) Michael> I'm stuck with the following problem with python 1.5.2c1 on Michael> MacOS 8.6: Michael> while 1: Michael> pass Michael> grinds my system to a halt. In other languages there are Michael> commands that give away cycles to the rest of the system and Michael> thus "playing well with others." Is there some similar command Michael> in python? Something to replace that pass with that allows me Michael> to do other things with my system? The code that implements pass in ceval.c could easily be modified to periodically call whatever Mac toolbox function is used to release the processor. Unfortunately, the Mac-specific source code seems not to be under CVS control, so while I can see some tantalizing hints of what needs doing in the source on my Linux machine, I can't suggest anything specific. I'm sure Jack or someone else will know precisely what needs doing. Skip Montanaro | http://www.mojam.com/ skip(a)mojam.com | http://www.musi-cal.com/ 847-971-7098 | Python: Programming the way Guido indented...

1 0

Library "too new"?
by Skip Montanaro Dec. 29, 1999

Dec. 29, 1999

What's this mean? >>> import DateTime ... ImportError: PythonCore: An import library was too new for a client. This is using the precompiled mxDateTime module that comes with the mxDateTime package. I'd search for the error in the archives (it's probably come up before), but search.python.org is apparently down for the holidays. Searching at Google for "pythonmac import library" didn't turn up anything useful. Thx, Skip Montanaro skip(a)mojam.com

1 0

MailMan or Pipermail bug or just pilot error?
by Skip Montanaro Dec. 29, 1999

Dec. 29, 1999

I just joined the PythonMac SIG and decided to browse the list archives. I noticed that the most recent archives at http://www.python.org/pipermail/pythonmac-sig/ show 2009-December as the current month. Since this rollover stuff happens automatically my presumption is it's a bug in either MailMan or Pipermail. Skip Montanaro | http://www.mojam.com/ skip(a)mojam.com | http://www.musi-cal.com/ 847-971-7098 | Python: Programming the way Guido indented...

2 1

Re: [Pythonmac-SIG] [Q] how to disable stderr/stdout console?
by Jack Jansen Dec. 28, 1999

Dec. 28, 1999

Recently, Giorgio Brajnik <giorgio(a)dimi.uniud.it> said: > On the other hand, don't you think that initialization of python > should allow more freedom to the api programmer? Perhaps by leaving as > option the call to init_mac_world() ? I was already going to change this, by adding a do_init_toolbox argument to PyMac_Initialize(), but then I remembered (or seem to remember:-) that multiple toolbox initializations shouldn't do any harm. And as PyMac_Initialize needs (some of) the toolboxes to be initialized the only option your program has is to initialize them earlier, in which case the init_mac_world() call in PyMac_Initialize is a no-op. -- 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

Re: [Pythonmac-SIG] Re: [ANNOUNCE] PySol 3.10 - a solitaire game collection
by Nils Kassube Dec. 27, 1999

Dec. 27, 1999

just(a)letterror.com (Just van Rossum) wrote: > *Running* PySol is not the problem, compiling is.) Some widgets do not display correctly on my system. However, it looks like it's Tk's problem, not Python's. Cheers, Nils -- nika(a)kassube.de (preferred) 4kassube(a)informatik.uni-hamburg.de

1 0