[Python-Dev] PEP 229 checked in
Fri, 19 Jan 2001 17:34:15 +0100
On Fri, Jan 19, 2001 at 11:26:34AM -0500, Guido van Rossum wrote:
> > This brings me to another point: how can 'make test' work at all ? Does
> > python always check for './Lib' (and './Modules') for modules ?
> Look at the logic in Modules/getpath.c, which calculates the initial
> (default) sys.path. It detects that it's running from the build tree
> and then modifies the default path a bit to include Lib and Modules
> relative to where the python executable was found.
Aye, I found it now.
> > If that's
> > specific for 'make test' and running python in the source distribution, that
> > sounds like a bit of a weird hack. I can't find any such hackery in the
> > source, but I also can't figure out how else it's working :)
> It's not jut for 'make test' -- it's to make life easy for developers
> in general (and me in particular :-) who want to try out their hacks
> without going through 'make install'.
Well, after some old SF movies & some sleep, I realized that :) But it is
going to have to change: you now have to include the build tree as well, and
that is quite a bit more difficult to figure out. I'd suggest a 'make run'
that calls python with the appropriate PYTHONPATH environment variable, but
that doesn't cover test-scripts (which I use a lot myself.)
Thomas Wouters <email@example.com>
Hi! I'm a .signature virus! copy me into your .signature file to help me spread!