Well - I wasn't necessarily advising this method. The operative word
there was "COULD". Sometimes that IS the appropriate thing to do, but
I was pointing out that there are SOME cases where it just doesn't
work well.
I'm going to put SOME sort of path processing in the next version,
so suggestions are welcome. ( One possibility: an optional pathlist -
if passed it will search on that path. sys.path or some slice of it
could be passed to restrict the search. )
[ unrelated topic - but connected in my mind via "import" ]:
BTW: Has anyone done any hacking of the Mac version of Python to
make it use resource file-forks ?
A couple of possibilities suggest itself:
* dynamic loading of compiled modules on the Mac via code resources.
[ It would be REALLY NEAT to be able to distribute new code modules
to Mac-ers without a development system to compile it on! ]
* put pyc byte code into the resource fork of the py file, rather
than a separate file. [ which may be able to speed up imports ]
* an option to save pyc code into the Python application's resource
fork - a sort of builtin bytecode module. Might give a method of
creating stand alone Python applications on Mac.
Are there many Mac-Python users out there ?
( Please raise your 16-ton Icon, if you are there! :-)
[ I haven't done any Mac hacking for a while, but the POWER-MAC
release ( using the next generation of the same RISC I've got
on my AIX machine ) has got me itching! ]
- Steve Majewski (804-982-0831) <sdm7g@Virginia.EDU>
- UVA Department of Molecular Physiology and Biological Physics