Mailman 3 May 2015 - pypy-dev

ImportError, No module named pycparser
by Yicong Huang May 22, 2015

May 22, 2015

Hi, I built pypy with some modules cut off, but met the errors as below for executing python scripts: debug: OperationError: debug: operror-type: ImportError debug: operror-value: No module named pycparser Which modules do pycparser depends on? I found the module might in /lib_pypy/cffi/_pycparser. But I did not exclude cffi module, and it did not have any problems of importing cffi. The modules I cut of are: ssl bz2 crypt _csv _minimal_curse fcntl _io mmap parser pyexpat select _socket _ssl zlib pwd And the list of used modules for the build: [usemodules] __pypy__ = True _ast = True _cffi_backend = True _codecs = True _collections = True _continuation = True _hashlib = True _locale = True _lsprof = True _md5 = True _minimal_curses = True _multibytecodec = True _multiprocessing = True _pickle_support = True _pypyjson = True _random = True _rawffi = True _sha = True _sre = True _testing = True _weakref = True array = True binascii = True cStringIO = True cmath = True cppyy = True cpyext = True errno = True gc = True imp = True marshal = True math = True micronumpy = True operator = True signal = True struct = True symbol = True termios = True thread = True time = True token = True unicodedata = True zipimport = True

2 2

Windows: pypyw.exe?
by Yaacov Finkelman May 22, 2015

May 22, 2015

Hi, I was wondering what the plan is for fixing: https://bitbucket.org/pypy/pypy/issue/1651/ It is just a hassle with each upgrade of pypy. I'd be happy to fix, but I don't know where to start. Best, Jacob

4 8

Cannot instantiate ctype 'struct *' of unknown size
by Yicong Huang May 21, 2015

May 21, 2015

Hi, The below is the code we met troubles; ffi.cdef(''' struct API { struct api_ret* (*pyudf)(char* str); }; ''') ffi.cdef(''' struct api_ret { char *ret1; char *ret2; char *ret3; }; ''') result = ffi.new('struct api_ret*') At first, we defined struct API with a function pointer that return a pointer to struct api_ret. And then we defined api_ret, and tried to new the object. The problem seems to happen when the function pointer and new structure are together. The below code had no problems. ffi.cdef(''' struct API { struct api_ret* (*pyudf)(char* str); }; ''') ffi.cdef(''' struct api_ret2 { char *ret1; char *ret2; char *ret3; }; ''') #we used different name api_ret2 to work around the issue. result = ffi.new('struct api_ret2*')

3 5

Could PyPy callback C code with C function pointer?
by Yicong Huang May 21, 2015

May 21, 2015

With PyPy "pypy_execute_source_ptr()", we could pass a C function pointer to python code. The funtion pointer was initilized in C code. Could PyPy use this function pointer callback to C code?

1 1

For embedding pypy, how to deal with None value
by Yicong Huang May 20, 2015

May 20, 2015

The document Embedding PyPy shows good examples, but did not tell how to deal with None value. As Python support None value, it might bring some troubles: 1. How to pass NULL from C to python for None? 2. If python function return None, how to handle the issue in C? For the above cases, we observed errors like these: >From cffi callback <function add_numbersInt at 0x00007f25f313e110>: Trying to convert the result back to C: TypeError: expected integer, got NoneType object

4 6

Exclude modules and functions from building libpypy.so
by Yicong Huang May 19, 2015

May 19, 2015

For pypy 2.5.1, the default buiding of libpypy-c.so is about 99MB. To my understanding, libypypy.so includes standard python libs. If we don't need some of those libs, could we exclude libs from building? For one thing, we might be able to get smaller libpypy.so lib. And for the other, we might exclude some *dangerous* lib that we don't need. ( Certainly, the more safer way is to use sandbox). >From pypy/config/pypyoption.py file, we found the below code: working_modules.update([ "_socket", "unicodedata", "mmap", "fcntl", "_locale", "pwd", "time" , "select", "zipimport", "_lsprof", "crypt", "signal", "_rawffi", "termios", "zlib", "bz2", "struct", "_hashlib", "_md5", "_sha", "_minimal_curses", "cStringIO", "thread", "itertools", "pyexpat", "_ssl", "cpyext", "array", "binascii", "_multiprocessing", '_warnings', "_collections", "_multibytecodec", "micronumpy", "_continuation", "_cffi_backend", "_csv", "cppyy", "_pypyjson" ]) If we would like to exclude some modules, could we modify this list? Further, is it possible to exclude some functions from modules?

3 2

Could PyPy be embeded running in sanbox?
by Yicong Huang May 19, 2015

May 19, 2015

In the document, we see PyPy could be embeded in C++ code as the following: pypy_execute_source_ptr(source, &api); The source is a string of python code. But I think by default the code does not run in sandbox. Are there any methods to run the code in sandbox?

2 3

[CFP] DLS 2015
by Manuel.Serrano＠inria.fr May 19, 2015

May 19, 2015

----------------------------- C A L L F O R P A P E R S ----------------------------- ======== DLS 2015 =========== 11th Dynamic Languages Symposium 2015 October, 2015 Pittsburgh, Pennsylvania, United States http://DLS2015.inria.fr Co-located with SPLASH 2015 In association with ACM SIGPLAN The 11th Dynamic Languages Symposium (DLS) at SPLASH 2015 is the premier forum for researchers and practitioners to share knowledge and research on dynamic languages, their implementation, and applications. The influence of dynamic languages -- from Lisp to Smalltalk to Python to Javascript -- on real-world practice and research continues to grow. DLS 2015 invites high quality papers reporting original research, innovative contributions, or experience related to dynamic languages, their implementation, and applications. Accepted papers will be published in the ACM Digital Library, and freely available for 2 weeks before and after the event itself. Areas of interest include but are not limited to: Innovative language features and implementation techniques Development and platform support, tools Interesting applications Domain-oriented programming Very late binding, dynamic composition, and run-time adaptation Reflection and meta-programming Software evolution Language symbiosis and multi-paradigm languages Dynamic optimization Hardware support Experience reports and case studies Educational approaches and perspectives Semantics of dynamic languages == Invited Speaker == DLS is pleased to announce a talk by the following invited speaker: Eelco Visser: Declare your Language. == Submissions and proceedings == Submissions should not have been published previously nor under review at other events. Research papers should describe work that advances the current state of the art. Experience papers should be of broad interest and should describe insights gained from substantive practical applications. The program committee will evaluate each contributed paper based on its relevance, significance, clarity, length, and originality. Papers are to be submitted electronically at http://www.easychair.org/conferences?conf=dls15 in PDF format. Submissions must be in the ACM format (see http://www.sigplan.org/authorInformation.htm) and not exceed 12 pages. Authors are reminded that brevity is a virtue. DLS 2015 will run a two-phase reviewing process to help authors make their final papers the best that they can be. After the first round of reviews, papers will be rejected, conditionally accepted, or unconditionally accepted. Conditionally accepted papers will be given a list of issues raised by reviewers. Authors will then submit a revised version of the paper with a cover letter explaining how they have or why they have not addressed these issues. The reviewers will then consider the cover letter and revised paper and recommend final acceptance or rejection. Accepted papers will be published in the ACM Digital Library. Important dates Abstract Submissions: Sun 7 Jun 2015 Full Submissions: Sun 15 Jun 2015 First phase notification: Mon 27 Jul Revisions due: Mon 3 Aug Final notification: Mon 17 Aug Camera ready: Fri 21 21 Aug Program chair Manuel Serrano, Inria Sophia-Antipolis, dls15(a)easychair.org Program committee Carl Friedrich Bolz, DE William R. Cook, UTexas, USA Jonathan Edwards, MIT, USA John Field, Google, USA Matt Flatt, USA Elisa Gonzalez Boix, Vrije Universiteit, BE Robert Hirschfeld, Hasso-Plattner-Institut Potsdam, DE Benjamin Livshits, Microsoft, USA Crista Lopes, UC Irvine, USA Kevin Millikin, Google, DN James Noble, Victoria University of Wellington, NZ Manuel Serrano, Inria, FR (General chair) Didier Verna, EPITA, FR Jan Vitek, Purdue, USA Joe Politz, Brown University, USA Olivier Tardieu, IBM, USA

1 0

Fail to build pypy-c-sandbox
by Yicong Huang May 18, 2015

May 18, 2015

I followed the document to build pypy-c-sandbox based on souce code 2.5.1: rpython/bin/rpython -O2 --sandbox pypy/goal/targetpypystandalone.py In the stdout, I did observe sandbox option is true: [translation] [translation] [translation] check_str_without_nul = True [translation] gc = generation [translation] gcrootfinder = shadowstack [translation] gctransformer = framework [translation] list_comprehension_operations = True [translation] rweakref = True [translation] sandbox = True [translation] shared = True [translation] thread = False [translation] withsmallfuncsets = 5 However, after the build process completed, only pypy-c generated and I did not find pypy-c-sandbox. [platform:execute] make -j 5 in /tmp/usession-master-16/testing_1 [platform:WARNING] pypy_module__warnings_interp_warnings.c: In function ‘pypy_g_normalize_module’: [platform:WARNING] pypy_module__warnings_interp_warnings.c:8565:5: warning: assuming signed overflow does not occur when assuming that (X - c) > X is always false [-Wstrict-overflow] [translation:info] copied: /home/yicong.hyc/odps-pypy/libpypy-c.so [translation:info] usession directory: /tmp/usession-master-16 [translation:info] created: /home/yicong.hyc/odps-pypy/pypy-c [1ebe2] translation-task} [Timer] Timings: [Timer] annotate --- 309.6 s [Timer] rtype_lltype --- 355.1 s [Timer] backendopt_lltype --- 179.8 s [Timer] stackcheckinsertion_lltype --- 17.5 s [Timer] database_c --- 208.2 s [Timer] source_c --- 179.9 s [Timer] compile_c --- 102.6 s [Timer] =========================================== [Timer] Total: --- 1352.7 s Grep "sandbox" in the log, there were some warnings, but no errors: [sandbox:WARNING] Not Implemented: sandboxing for external function 'RPython_StartupCode' [sandbox:WARNING] Not Implemented: sandboxing for external function 'pypy_debug_catch_fatal_exception' [sandbox:WARNING] Not Implemented: SomeImpossibleValue() [sandbox:WARNING] Not Implemented: SomeImpossibleValue() [sandbox:WARNING] Not Implemented: sandboxing for external function 'clock_gettime' [sandbox:WARNING] Not Implemented: sandboxing for external function 'clock_getres' [sandbox:WARNING] Not Implemented: sandboxing for external function 'fcntl'

2 5

pypy + cProfile
by Stanislav Bohm May 15, 2015

May 15, 2015

Hi I have observed that Pypy is faster when cProfile is enabled than its normal execution. I would like to ask if it is a normal behavior or a kind of anomaly? E.g. one of my benchmarks: Pypy: ~24.5s Pypy + cProfile: ~19s CPython: ~22s Tested with 2.5.1+dfsg-1~ppa1+ubuntu14.04, but I have observed a similar behavior with older versions of Pypy shipped with Ubuntu 14.10 and 15.04. My application is a pure python application that communicates through sockets. (It is a state-space analytical tool that communicates with a modified Valgrind process through TCP/IP connection). A replication of results: Build: https://github.com/spirali/aislinn (Installation instructions: http://verif.cs.vsb.cz/aislinn/doc/userguide.html#_installation) cd aislinn/tests/complex/workers ../../../bin/mpicc workers.c # build an analyzed program time pypy ../../../src/aislinn/aislinn.py -p4 ./a.out 10 90 time pypy -m cProfile ../../../src/aislinn/aislinn.py -p4 ./a.out 10 90 time python ../../../src/aislinn/aislinn.py -p4 ./a.out 10 90 Best regards, Stanislav Bohm

4 6