This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: --install-data doesn't effect resources destination
Type: behavior Stage: resolved
Components: Distutils2 Versions: Python 3.3
Status: closed Resolution: out of date
Dependencies: Superseder:
Assigned To: tarek Nosy List: alexis, eric.araujo, tarek, trevor
Priority: normal Keywords:

Created on 2011-08-24 10:18 by trevor, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (2)
msg142878 - (view) Author: trevor (trevor) Date: 2011-08-24 10:18
attempting to point the relative destination with "--install-data" does not seem to have an effect. the specified directory is created, but resources are still installed relative to the present working directory.


resources =
    externalfiles/tobemoved.txt = support

% pysetup3 run install_dist --install-data /tmp/example

/tmp/example is created with no files, ./support/tobemoved.txt is created
msg142889 - (view) Author: Éric Araujo (eric.araujo) * (Python committer) Date: 2011-08-24 17:29
This is one of the things that were left under-specified when the resources subsystem was introduced by adding working code instead of a PEP.  I think that --install-data is obsolete now, and that there should be another way to override specific sysconfig variables or paths (which are used to install data files/resources) from the command line and config files, to replace --install-data.
Date User Action Args
2022-04-11 14:57:21adminsetgithub: 57039
2014-03-13 03:49:55eric.araujosetstatus: open -> closed
resolution: out of date
stage: resolved
2011-08-24 17:29:47eric.araujosetmessages: + msg142889
2011-08-24 10:18:09trevorcreate