Examples under debian:

    docutils/__init__.py          ->     located in
/usr/local/lib/python2.6/site-packages/
    ../../../bin/rst2html.py       ->  located in /usr/local/bin
    /etc/whatever                  ->     located in /etc

I'm wondering if there's really any benefit to having ../../../bin/rst2html.py vs. /usr/local/bin/rst2html.py.  Was there a use case for that, or should we just go with relative paths ONLY for children of the libdir?
">

(original) (raw)

On Wed, Apr 7, 2010 at 12:45 PM, P.J. Eby <pje@telecommunity.com> wrote:

Examples under debian:

docutils/\_\_init\_\_.py -> located in
/usr/local/lib/python2.6/site-packages/
../../../bin/rst2html.py -> located in /usr/local/bin
/etc/whatever -> located in /etc

I'm wondering if there's really any benefit to having ../../../bin/rst2html.py vs. /usr/local/bin/rst2html.py. Was there a use case for that, or should we just go with relative paths ONLY for children of the libdir?

(I only suggested this setup in order to preserve as much of the prefix-relativity proposal as possible, but I wasn't the one who proposed prefix-relativity so I don't recall what the use case is, and I don't even remember who proposed it. I only ever had a usecase for libdir-relativity personally.)

Yes, in a virtualenv environment there will be ../../../bin/rst2html.py that will still be under the (virtual) sys.prefix, and the whole bundle can be usefully moved around.

--

Ian Bicking | http://blog.ianbicking.org