On Wed, Apr 7, 2010 at 12:45 PM, P.J. Eby <span dir="ltr"><<a href="mailto:pje@telecommunity.com">pje@telecommunity.com</a>></span> wrote:<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Examples under debian:<br>
<br>
docutils/__init__.py -> located in<br>
/usr/local/lib/python2.6/site-packages/<br>
../../../bin/rst2html.py -> located in /usr/local/bin<br>
/etc/whatever -> located in /etc<br>
</blockquote>
<br></div>
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?<br>
<br>
(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.)</blockquote>
</div><div><br></div>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.<br clear="all"><br>-- <br>
Ian Bicking | <a href="http://blog.ianbicking.org">http://blog.ianbicking.org</a><br>