shiyao.ma added the comment:
Let me explain a bit. ;)
Suppose I just hg cloned the roundup repo from hg.p.o
When I install the roundup with: python setup install --prefix
../working/roundup
FOR THE INSTALLED FILES:
If this patch is NOT applied,
Files under working/roundup/bin will all have a "#! /hardcoded/path". The path
is the absolute path pointing to the python executable which is used for the
installation.
Besides, the files will all contain a line in the form of,
sys.path.insert("..working/roundup").
If this patch is applied,
Files under working/roundup/bin will all have a "#! /usr/bin/env python"
The sys.path.insert("../working/bar") will also become
sys.path.insert("/abspath/to/working/bar")
The reason I fired this issue is, I am new to psf-meta dev. So I found myself
constantly "modify the source; install it; preview the results;re-modify the
source;re-install".
Due to the relative "sys.path.insert" and the /hardcoded/path", I must use the
virutalenv python to install it, and I must have to stay in the right directory
to run rd-admin, which I often foget.
But now I found I can modify the source and directly rd-admin/rd-start based on
the source. No more installation!
So this issue doesn't pertain much to me now.
_______________________________________________________
PSF Meta Tracker <metatrac...@psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue565>
_______________________________________________________
_______________________________________________
Tracker-discuss mailing list
Tracker-discuss@python.org
https://mail.python.org/mailman/listinfo/tracker-discuss
