distutils ignores leading / of prefix in some circumstances
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fluidity |
Fix Released
|
Medium
|
Tim Greaves |
Bug Description
During the Fluidity install process, distutils appears to be behaving inconsistently in terms of how it treats the leading / in a prefix. This is specifically with regard to the python installer, called in the 'install' rule of the root Fluidity Makefile.
An example of where it fails to work is seen from the buildbot output at:
where the command is:
cd python ; python setup.py install --root="" --prefix=
but the install proceeds as:
creating home
creating home/fluidity
creating home/fluidity/
creating home/fluidity/
creating home/fluidity/
creating home/fluidity/
copying build/lib/
copying build/lib/
.....
If a double leading slash is provided to the prefix (ie, //home/
At present, no idea why this is happening.
Changed in fluidity: | |
status: | New → Triaged |
Changed in fluidity: | |
importance: | Undecided → Medium |
assignee: | nobody → Tim Greaves (tim-greaves) |
status: | Triaged → In Progress |
milestone: | none → 4.1.4 |
Changed in fluidity: | |
milestone: | 4.1.4 → 4.1.5 |
Changed in fluidity: | |
status: | Fix Committed → Fix Released |
Status update on this:
I've tried changing this to use setuptools rather than distutils, and get exactly the same problem. I'm unsure whether this is an inherited bug by setuptools from distutils, or whether it indicates a higher-level problem; I suspect the latter as setuptools says:
You are attempting to install a package to a directory that is not
on PYTHONPATH and which Python does not read ".pth" files from. The
installation directory you specified (via --install-dir, --prefix, or
the distutils default setting) was:
data/ tmb1/install/ lib/python2. 6/site- packages/
Investigation ongoing.