On Thu, Oct 18, 2012 at 4:50 PM, Mike Gilbert <flop...@gentoo.org> wrote: > On Thu, Oct 18, 2012 at 3:29 PM, Brian Harring <ferri...@gmail.com> wrote: >> On Thu, Oct 18, 2012 at 11:28:59AM -0400, Mike Gilbert wrote: >>> Regarding your /usr/bin/python3.2 /usr/bin/sphinx-build example: >>> invoking python on a binary (or a symlink to a binary) isn't going to >>> work at all. So I don't see how you've solved that issue. >> >> Kindly provide reasoning/justification for such a claim in the future- >> saves a round of email ping/ponging, and saves me getting pissy >> towards people if they persist in it. :) >> >> Lecture aside, "nuh uh, it does work!" is appropriate. I already >> hacked up a prototype locally that works fine and does this via an >> env passing hack- w/ what was proposed, this can be done w/out those >> hacks, and would be faster. >> > > When you invoke a command like: > > /usr/bin/python3.2 /usr/bin/somebinary > > The python3.2 program assumes somebinary is a python script and tries > to parse it. Since somebinary is actually an ELF object, python bombs > out immediately. > > Am I missing something fundamental here?
Oh, perhaps you are suggesting that /usr/bin/python3.2 would no longer be the actual python binary, but instead be a link to your wrapper program? It's really not clear to me.
