..\setup.py relative invocation (was: [issue108] develop install fails if path to setup.py is relative)
setup.py fails miserably when invoked using relative path, i.e. `python ../../setup.py ...`. In this case it attempts to look up referenced files in current directory - not in its own dir.
What is it needed for? Does distutils2 fix this?
I ask, because it adds another "save cwd;cd;...;restore cwd" yak shaving wrapper to development process, and the error message for failure is not very intuitive.
On Sun, May 9, 2010 at 2:21 PM, anatoly techtonik techtonik@gmail.com wrote:
setup.py fails miserably when invoked using relative path, i.e. `python ../../setup.py ...`. In this case it attempts to look up referenced files in current directory - not in its own dir.
What is it needed for? Does distutils2 fix this?
No, but one long term goal of distutils2 is to make setup.py optional, meaning that the commands will be run using for example a -m call that could look like this:
$ python -m distutils2 run install
And could take the project root path as an option :
$ python -m distutils2 run install -p /here/is/the/project
Regards Tarek
-
anatoly techtonik -
Tarek Ziadé