Yes, I was re-translating in order to test the CINT backend for PyPyROOT.  
After importing syslog as root, I can now import syslog as non-root.  

I can send an email or bug report to MacPorts, but I'm not sure how to describe 
the bug, as I'm unfamiliar with the syslog module.

Jean-François

On 2013-09-10, at 08:02 , wlavrij...@lbl.gov wrote:

> Hi Armin,
> 
>> This is a mis-installed PyPy.  To fix it, run PyPy as root and type:
>> 
>>   import syslog
>> 
>> You may have to also import a few other modules as needed.  ("syslog"
>> appears in the traceback above.)
> 
> thanks for the recipe!
> 
>> Note also that cppyy is now included in PyPy by default (on
>> non-Windows platforms), so you don't need to retranslate if that's the
>> only reason.
> 
> Is for the CINT backend. There are a couple of optimizations in RPython for
> that backend, so those need to be translated, and the latest pieces are on
> the reflex-support branch, not in trunk at the moment.
> 
> On the CPython side, we're closing in (finally, yay! :) ) on having an LLVM
> (Cling, that is: http://root.cern.ch/drupal/content/cling) backend. After
> that, I can consolidate; dependencies and re-packaging is going to take a
> bit of time. Way nicer, though. Not only C++11, but also since Cling is
> dynamic, it is a much better fit to Python. Think cross inheritance, calling
> Python from C++, automatic template instantiations, the cffi interface for
> C++ as well, etc.
> 
> Best regards,
>           Wim
> -- 
> wlavrij...@lbl.gov    --    +1 (510) 486 6411    --    www.lavrijsen.net

_______________________________________________
pypy-dev mailing list
pypy-dev@python.org
https://mail.python.org/mailman/listinfo/pypy-dev

Reply via email to