Byte compile correctly with DESTDIR.

Logged In: YES 
user_id=21627

What is the rationale of this patch? If I set DESTDIR to,
say, /tmp/py, why is passing -d /tmp/py to compileall desirable?

Logged In: YES 
user_id=387193

A simple test, to describe the problem, below.

DESTDIR is set to "/home/users/user/tmp/python-2.3b1-root-user".
-----------------
import logging
 
class X:
    pass
 
logging.setLoggerClass(X)
-------------------

Code above gives following exception:

Traceback (most recent call last):
  File "tracedir.py", line 6, in ?
    logging.setLoggerClass(X)
  File
"/home/users/user/tmp/python-2.3b1-root-user/usr/lib/python2.3/logging/__init__.py",
line 729, in setLoggerClass
TypeError: logger not derived from logging.Logger: X

I _suppose_ that, after applying the patch the exception
will look like:

Traceback (most recent call last):
  File "tracedir.py", line 6, in ?
    logging.setLoggerClass(X)
  File "/usr/lib/python2.3/logging/__init__.py", line 729,
in setLoggerClass
TypeError: logger not derived from logging.Logger: X

There will be no DESTDIR part in the module filepath.

Logged In: YES 
user_id=21627

Please test this on your machine. The byte code of
__init__.py will still point to 

/home/users/user/tmp/python-2.3b1-root-user/usr/lib/python2.3/logging/__init__.py

with your patch applied.

Logged In: YES 
user_id=192186

I forgot to mention, that the patch was larger before, but I
saw many simmilar things applied in CVS, so this _should_
work with CVS version. However I will test it today...

Logged In: YES 
user_id=21627

The patch is incorrect: setting -d to DESTDIR will cause
DESTDIR to be hard-coded. Correct is to use LIBDEST,
committed as Makefile.pre.in 1.134

Logged In: YES 
user_id=192186

Yes, you're right, sorry for posting bad patch....