Steve,
if a $JYTHON_HOME env var is set before calling jython, this overrides
the place jython is started from.
So for using virtualenv, I'd recommend to not preset $JYTHON_HOME.
best wishes,
Oti.
On Mon, Mar 30, 2009 at 5:29 PM, Steven Githens <swgithen@...> wrote:
> The issue seemed to be that I had a $JYTHON_HOME declared in my .bashrc
> for some other apps I was using, and this messed it up around lines
> 664-668 of go-pylons.py. After removing it completely it worked ok.
>
> Not sure if this would be considered a bug in go-pylons.py or if I just
> shouldn't use that in my bash startup. :p
>
> Cheers,
> Steve
>
> Philip Jenvey wrote:
>>
>> On Mar 28, 2009, at 2:05 PM, Steven Githens wrote:
>>
>>> Hi all,
>>>
>>> Just working through Phils slides after his talk, and seeing the
>>> following... not sure if it's a real issue or what.
>>>
>>> 14:04:16 pylonslearning: which jython
>>> /home/sgithens/bin/jython2.5b3//bin/jython
>>> 14:04:20 pylonslearning: jython go-pylons.py jypylonsenv
>>> New jython executable in jypylonsenv/bin/jython
>>> ERROR: The executable jypylonsenv/bin/jython is not functioning
>>> ERROR: It thinks sys.prefix is '/home/sgithens/bin/jython2.5b3' (should
>>> be '/home/sgithens/code/pylonslearning/jypylonsenv')
>>> ERROR: virtualenv is not compatible with this system or executable
>>> 14:05:01 pylonslearning:
>>>
>>
>> Oddly enough I can't reproduce this. Catch me later and we'll figure
>> it out on your environment.
>>
>> --
>> Philip Jenvey
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Jython-dev mailing list
> Jython-dev@...
> https://lists.sourceforge.net/lists/listinfo/jython-dev
>
|