his build directory in a different place than his source directory. I
do, and it is supposed to be supported. The naive patch caused an
endless recursion in the Make process. This should take care of that.
necessary. Do Grammar after Parser because Grammar needs Parser, and not the
other way 'round. This patch doesn't bother with dependencies because it's
tricky to get right (for instance for the modules that want graminit.h,
like cPickle) and other dependencies are broken to begin with.
The version there built the tags and TAGS files in the build
directory. I like them in the source directory. The simplest
solution is to cd to the source directory before running ctags or
etags.
Tested both superficially and they work for me, on Linux Red Hat 6.1.
-t. This ensures that each installation from source is
checked for compliance. This is needed to make sure .py
files in the various Lib/plat-foo/ directories are tested
even if the core developers do not have access to the
corresponding platforms.
lib-stdwin is no longer installed.
Increase the support level for other obsolete modules a bit: install
lib-old by default. It still isn't in the path by default, but at
least it's easier to add to your $PYTHONPATH this way. (This makes
sense because in 1.6 we're much more aggressive with declaring modules
obsolete.)
targets. On some platforms this would cause an infinite Make
recursion. Also remove "Doc" from the SUBDIRSTOO variable, since it
no longer exists in the standard distribution.
it seems harmless for other platforms. It plays tricks with the name
of the library used to link with. Apparently DG/UX really wants a
shared library to link with if it wants shared modules to use symbols
from the library. I'm not sure why this wasn't an issue with 1.4;
DG/UX seems to be the only platform where moving to a single library
made things harder!
BTW This adds a target to create libpython$(VERSION).so; however this
target is *only* for DG/UX.
Modules/Setup.local.
Guido: I hope this is ok; it seems to make a lot of sense to get the
whole trio of module config files installed as a set rather than
doing it partially.
in a few places -- so it can be set to .exe on GNUWIN32 platforms and
do the right thing. Whatever. (This was already done in
Modules/Makefile* but wasn't carried over here.)
python executable is built. (It still won't reflect builds of the
library only, but since the default make target builds the python
executable, that's alright.)