On 12.04.07, Andrea Valle wrote:
> >Now, we need a Python Guru who explains what happens when PyX calls
> >os.popen("kpsewhich ...") I never understood this.
>
> (IN case we can't solve it, maybe we can ask comp.lang.python?)
>
> Here you have a picture from my shell
> polifilo:/ andreavalle$ echo $SHELL
> /bin/bash
> polifilo:/ andreavalle$ echo $ENV
>
> polifilo:/ andreavalle$ echo $BASH_ENV
>
> polifilo:/ andreavalle$ echo $TEXMFCNF
>
> polifilo:/ andreavalle$ which kpsewhich
> /usr/texbin/kpsewhich
> polifilo:/ andreavalle$ echo 'which kpsewhich' | sh
> /usr/texbin/kpsewhich
> >Maybe this helps. Otherwise, I have no idea what went wrong.
OK. Now, there is yet another TeX installation popping up on your
computer? First, you had a result from kpsewhich from texlive at
/usr/local/texlive/2007
and now /usr/texbin/kpsewhich? If both locations correspond to the
same TeX installation, then it is indeed a strange one.
I am giving up at this point. My impression is that you have
systematically broken your TeX and PyX installation. There are too
many possibilities where the problem might come from. The invocation
of a shell from python is a too complicated task to to from outside.
You should trace it down, looking at all the configuation scripts for
the bash.
Good luck.
Michael.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
PyX-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/pyx-user
