Re: [Pyobjc-dev] Testsuite adventures
Brought to you by:
ronaldoussoren
From: Jack J. <Jac...@cw...> - 2003-05-20 09:36:29
|
On Monday, May 19, 2003, at 14:52 Europe/Amsterdam, Dinu Gherman wrote: > Jack Jansen: > >> The easy answer is that FrameWork is a very old module (I think Guido >> even wrote the original himself, otherwise I did many many years >> ago), it's a minimal application framework. It has nothing to do with >> MacOSX "Framework"s. >> >> The better answer is that this confusion is going to occur more >> often. Do you have any suggestions as to how I could document this? >> In the documentation? The help string? Anywhere else? > > Well, we're talking about non-portable platform-specific modules and/or > packages, don't we? Of course, "portable" and"specific" are not always > clearly defined or might change for a given module (say, PyObjC, once > Apple decides to distribute Cocoa on Intel boxes). This was discussed on python-dev (moving platform-dependent modules into a platform-specific package, so you would have to do "import mac.FrameWork" or "import win.winsound") but rejected. Note that all platforms have specific modules (see all the plat-* subdirectories of Lib), it's just that the Mac has very many of them. -- Jack Jansen, <Jac...@cw...>, http://www.cwi.nl/~jack If I can't dance I don't want to be part of your revolution -- Emma Goldman |