Mailman 3 April 2016 - pypy-dev

About gurobipy
by Luis José Novoa May 31, 2018

May 31, 2018

Hi All, My name is Luis Novoa. Im working on a large scale optimization problem using python/gurobipy for my implementation. I was wondering if any of you in this list has used gurobipy with pypy, or if it is even possible at this time. Thanks in advance, Luis.

9 9

Re: [pypy-dev] 5.1 has been released
by Matti Picus April 30, 2016

April 30, 2016

On 22/04/16 07:02, Phyo Arkar wrote: > Congrats PyPy Team! > It keeps getting better and better! > And thank you very much for improving cpyext. > > > Fix edge cases in the cpyext refcounting-compatible semantics (more > work on cpyext compatibility is coming in the cpyext-ext branch, but > isn’t ready yet) > > So thats mean , soon, infuture , cpyext will be fully supported? > For some definition of 'infuture' and 'fully' - yes. The larger goal is to enable the scientific python stack with only minor upstream changes, IMO cpyext-ext will be finished when numpy's test suite passes with no failures on the fork of numpy available on github at github.com/pypy/numpy (not to be confused with the one at bitbucket/pypy/numpy, which uses micronumpy and cffi) Eventually, we will modify micronumpy so that app-level python calls with ndarrays will somehow be hijacked to go through micronumpy rather than the C-API functions, assuming this is even possible. It is a big job, help is welcome Matti

2 2

jitlog 2.0
by Richard Plangger April 29, 2016

April 29, 2016

Hello, I have spent a lot of my free time to improve our jitviewer. Finally I'm happy to present some results and I want to get some feedback (bad or good). I run a test server (at http://217.172.172.207:8000) so without installing anything you can just have a quick look. Here [1] is richards.py uploaded to that server. Here some more information: What has changed? ================= We already host vmprof.com for profile data. This is only part of the information that is interesting. I think it would be very helpful to see what the JIT compiler currently produces in a more 'global view'. The combination of profile data available at vmprof.com and the log output of pypy can really help to understand what is going on inside the VM. The new log output is easier to process and allows to fully rebuild the information in jit viewer (with no dependency to the pypy source code). I have added a svg chart that displays the trace tree. It can be examined further which is really something. I think that is a much nicer high level view of our tracing JIT compiler than in the old jit viewer. Technically ----------- I have mostly rewritten the log format. It writes a binary file and currently encodes pretty much every information the PYPYLOG does. It is a custom binary format similar to the one in vmprof. It is intended to reduce the size of jitlog. We discussed that it would be a rather good idea to use a standardized binary protocol instead of creating our own. I agree with that, but there are no real options without significant effort. E.g. capnproto would have required me to write the encoder on the rpython side and adjust the javascript capnproto library that it is able to run in the browser (nodejs only). I decided to stick with the custom very simple binary format and extended it that it is able to version the jitlog. We can support several versions, ideally never dropping support for any official version of the jitlog. I extended vmprof-python [2] to read that binary file format and upload it along with the normal vmprof data. It has a pretty printer which you can use to get information on the console. It's state is very minimal and my current idea is to extend a very minimal api to be able to query the jitlog. I have something in mind like: $ python -m vmprof.prettyprint /tmp/abcdef.jitlog --query 'trace.get_func_name() == "schedule"' > 1x trace matched your query > trace started in the function schedule in path/to/richards.py:501 > label(...) > ... > jump(...) A sample command to upload jitlog data would be: python -m vmprof --jitlog --web --web-url http://217.172.172.207:8000 <path to script>/richards.py Here are some things I'm aware of and want to change: * No compression of JSON. That would greatly speed up loading! * The live ranges are not connected when assembler is shown (style fix) * The entry count (of a trace) displayed in the trace view is always 0, the data is present but not serialized when invoked with -m vmprof --jitlog What's next =========== I hope someone could take a look at the new-jit-log branch so we can discuss if it. I also want to achieve: * Feature parity with the old jitviewer (what is missing?) * Be able to jump from vmprof profile data to jitlog and back * Show the jumps in the trace view * Merge to default :) * Upload the source code to give a better pictures of what has been produced from which source line * Display merge point information in the resoperation list * Does it work on IE? Cheers, Richard [1] http://217.172.172.207:8000/#/92a1ff97c87d187eee3f60a0a088e669/traces [2] https://github.com/vmprof/vmprof-python

2 1

Garbage collection internals
by Raoul Veroy April 28, 2016

April 28, 2016

Hi all. Sorry if this is the wrong venue for this. First a question about the old reference counting implementation in Pypy. I wanted to learn and work on the garbage collection of Pypy. First, in this paper from <https://bitbucket.org/pypy/extradoc/raw/tip/eu-report/D07.1_Massive_Paralle…> 2007 about PyPy <https://bitbucket.org/pypy/extradoc/raw/tip/eu-report/D07.1_Massive_Paralle…>, it mentions a reference counting GC transformer, which is not mentioned anymore in the 2.4.x documentation ( https://pypy.readthedocs.org/en/release-2.4.x/garbage_collection.html). The latest documentation doesn't seem to have a version of this garbage_collection page. I wanted to do some studies on reference counting and the implementation does not have to be efficient or fast. What is the best way to get at the old refcount implementation? Would it be to work on the last version to have it? Secondly, I wanted to log a trace of all allocations of objects and all updates to references. Is there infrastructure or tool that exists for this? Thanks. - Raoul

2 1

Reflex home page?
by Armin Rigo April 27, 2016

April 27, 2016

Hi Wim, We are linking from the PyPy documentation to these pages: http://root.cern.ch/drupal/content/reflex http://root.cern.ch/drupal/content/generating-reflex-dictionaries They are 404 now. What should they be fixed to? A bientôt, Armin.

3 2

Error Messages
by Sayth Renshaw April 27, 2016

April 27, 2016

Hi Just wondering if PyPy error messages are or could be of a higher quality than the CPython error messages? One of the goals of Rubinius a former Ruby alternate implementation similar in intent to PyPy was improved developer feedback in error messages. Is this an area of opportunity for PyPy? Cheers Sayth

6 12

pypy 2.7 version 5.1.1
by Matti Picus April 27, 2016

April 27, 2016

1 0

5.1 has been released
by Matti Picus April 21, 2016

April 21, 2016

1 0

PyPY 5.1 release is close, help needed
by Matti Picus April 20, 2016

April 20, 2016

3 2

compilation problem while testing libffi
by Petr Hanousek April 10, 2016

April 10, 2016

Dears, I have tried to compile pypy 5.0.1 according to http://pypy.org/download.html#building-from-source. First compiled libffi-3.2.1 and installed to /software/pypy/5.0.0/gcc and then exported the PKG_CONFIG_PATH to the appropripate directory. Result from "python ../../rpython/bin/rpython -Ojit targetpypystandalone" is in the attachment. What could be wrong, please? The /software path is somewhere on AFS (network storage) and I have full rights on it. I assume there is no problem to run the compilation as root. When I try to run by hand the last two steps before error occurs, no error appears. Thank you, Petr -- +-------------------------------------------------------------------+ Petr Hanousek e-mail: petr.hanousek(a)cesnet.cz User Support phone: +420 950 072 112 CESNET z.s.p.o. mobile: +420 606 665 139 location: Zikova 4, Praha room: 90a Czech Republic +-------------------------------------------------------------------+

2 2