Hello list,

Anyone having trouble with pypy? I can't find anything on the mailing
list or bug tracker. Running pypy for me gives:

$ pypy
'import site' failed
Python 2.7.2 (2346207d99463f299f09f3e151c9d5fa9158f71b, Feb 10 2012, 15:07:02)
[PyPy 1.8.0 with GCC 4.6.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
debug: OperationError:
debug: operror-type: AttributeError
debug: operror-value: 'module' object has no attribute 'warn'

I only use pypy when I am doing computationally intensive work so I'm
not sure when this started happening. I have tried rolling back to
pypy 1.7 and 1.6 with the same result. An strace is very busy and I
can't see anything at first glance. I am running [testing].

Regards,

Mike

Hello list,

just an update on this:

On Sat, Apr 14, 2012 at 7:25 PM, Mike Sampson <mike@sambodata.com> wrote:
[snip]
> $ pypy
> 'import site' failed
> Python 2.7.2 (2346207d99463f299f09f3e151c9d5fa9158f71b, Feb 10 2012, 15:07:02)
> [PyPy 1.8.0 with GCC 4.6.2] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> debug: OperationError:
> debug: *operror-type: AttributeError
> debug: *operror-value: 'module' object has no attribute 'warn'
>
[snip]

I tracked this down to a PYTHONPATH env variable set by libreoffice.
Running pypy with the -E flag fixes the errors. Not sure if this is a
bug or not.

Regards,

Mike

On Sun, Apr 15, 2012 at 11:39:26AM +1000, Mike Sampson wrote:
> Hello list,
>
> just an update on this:
>
> On Sat, Apr 14, 2012 at 7:25 PM, Mike Sampson <mike@sambodata.com> wrote:
> [snip]
> > $ pypy
> > 'import site' failed
> > Python 2.7.2 (2346207d99463f299f09f3e151c9d5fa9158f71b, Feb 10 2012, 15:07:02)
> > [PyPy 1.8.0 with GCC 4.6.2] on linux2
> > Type "help", "copyright", "credits" or "license" for more information.
> > debug: OperationError:
> > debug: *operror-type: AttributeError
> > debug: *operror-value: 'module' object has no attribute 'warn'
> >
> [snip]
>
> I tracked this down to a PYTHONPATH env variable set by libreoffice.
> Running pypy with the -E flag fixes the errors. Not sure if this is a
> bug or not.
>
> Regards,
>
> Mike

I found exactly the same on the pypy bugtracker (issues 505/506) and figured
you might find your way there yourself? [1]

cheers!
mar77i

[1] https://bugs.pypy.org/issue505