In article <CrG943.KB3@jabba.ess.harris.com> firstname.lastname@example.org (Mike McDonald) writes:
> How about a "special" directory name like SYS.PATH which substitutes in the
> current sys.path? The you can say things like:
I also agree, if i understand what steve majewski was saying, that it
would be a good idea to provide an explicit-path loadup functionality,
like emacs' load-file provides vs its' load-library function. Might
be nicer to have both functionalities rolled into the same import
statement, though, eg discriminating on whether or not the module name
includes explicit path components.
> Right now, the only method is to use my 'ImportFrom'
> hack to give an explicit pathname for import. ( Which,
> come to think of it, is probably the best way to do
> it anyway, but the above proposal would be a pretty
> minimal change. )
email@example.com, 301 975-3539