[Distutils] PEP 376 - RECORD file / Data files + pip feedback ?

Wolodja Wentland wentland at cl.uni-heidelberg.de
Sat Feb 6 12:21:57 CET 2010

On Sat, Feb 06, 2010 at 11:16 +0100, Tarek Ziadé wrote:

Hi all,

sorry for joining in so late. I am pretty busy with my thesis and
examinations, which is why I can't work on this right now.

I am still subscribed to python-distutils and read the mails regularly,
so there is no need to CC me.

> IOW some paths in the PREFIXES file (or the RECORD file as long as we
> are able to find-and-replace paths in there) *need* to be updated at
> installation time no matter what we decide to do here.


> So, it seems to me that we need to keep unexpanded paths [1] in the
> RECORD file and let the install command expand them using installation
> option .  But we have to avoid this expansion when doing binary
> releases.

I still think that a PREFIX file, that contains *all* prefixes which 
are configurable during installation right now, should make it to PEP
376 and to Python 2.7/3.2 . These prefixes could be kept unexpanded in
the RECORD file and it would therefore only be necessary to change them
within the PREFIX file if one wants to relocate an installation. (Is
this really a common use case?)

The PEP lists $PREFIX and $EXEC_PREFIX, but the set of prefixes that are
configurable during installation comprises:

Prefix              Default value       Command line option
PREFIX              sys.prefix          --install-purelib
EXEC_PREFIX         sys.exec_prefix     --install-platlib
SCRIPTS_PREFIX      $PREFIX/bin         --install-scripts
DATA_PREFIX         $PREFIX/share       --install-data                    

I think that it'll help Linux distribution developers *and* Python
developers a lot if these prefixes where available during runtime or
could be obtained by parsing the PREFIX file. This would mean the end of
__file__ magic to find data files and Python packagers could adapt their
tools to copy, for example, a configuration files from
$DATA_PREFIX/foo.cfg to a location that complies with the FHS (i.e.

> It seems feasible to me in both cases. And Wolojda could work later on
> adding more paths definitions and how to configure them through
> distutils options.

Will do :-)

Yours sincerely
  .''`.     Wolodja Wentland    <wentland at cl.uni-heidelberg.de> 
 : :'  :    
 `. `'`     4096R/CAF14EFC 
   `-       081C B7CD FF04 2BA9 94EA  36B2 8B7F 7D30 CAF1 4EFC
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://mail.python.org/pipermail/distutils-sig/attachments/20100206/2ff54a98/attachment.pgp>

More information about the Distutils-SIG mailing list