Mailman 3 January 2017 - pypy-dev

About gurobipy
by Luis José Novoa June 1, 2018

June 1, 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

Modifying Interpreter-level Object from Application
by Frank Wang Feb. 8, 2017

Feb. 8, 2017

Hi, At the application level, I want to modify some interpreter-level attributes of an object. Right now, I have the interpreter level functions that allow me to modify the interpreter object. Is the easiest way to have an application access interpreter level attributes to use a Mixed Module with interpreter level definitions? I'm having a bit of trouble getting it to work, so I was wondering if there was a much easier way for an application to modify interpreter objects or call interpreter level functions that modify an object. Thanks, Frank

3 4

RPython hashes no longer preserved across translation
by Armin Rigo Jan. 29, 2017

Jan. 29, 2017

Hi all, I would like to merge the branch "rpython-hash". That branch drops the RPython requirement that hashes (notably of prebuilt instances) don't change across translation. By dropping it, I could remove some cruft at various places, and it makes the life a bit easier for other systems like STM, too. The motivation is that in py3.5 we're considering the hash randomization feature again, for strings. This feature is not compatible at all with the idea that hashes should not change. So with "rpython-hash" it should be possible, at translation-time, to choose the algorithm used by CPython 3.5 (siphash-2-4), and moreover with an optional seed at runtime. The main place that relied on the hashes not changing is prebuilt dictionaries. That branch fixes them by not including the "indexes" part at all during translation, and rebuilding the index on the first usage. There were only three places I found in PyPy that relied on this feature: weakrefs caching the hash of their referent; frozensets caching their own hash; and a detail inside _cffi_backend. All places needed fixing, but that was easy. I think it's a good move and a small simplification of RPython internals. Of course it might break other RPython-based interpreters out there. Any feedback about that would be appreciated. A bientôt, Armin.

2 2

Fwd: [MoreVMs'17] Call for Contributions: 1st Workshop on Modern Language Runtimes, Ecosystems, and VMs at <Programming> 2017
by William ML Leslie Jan. 28, 2017

Jan. 28, 2017

Hello pypy contributors and rpython users, In case any of you missed this CFP this looks like an exciting workshop! ---------- Forwarded message ---------- From: Stefan Marr <java(a)stefan-marr.de> Date: 6 December 2016 at 00:56 Subject: [MoreVMs'17] Call for Contributions: 1st Workshop on Modern Language Runtimes, Ecosystems, and VMs at <Programming> 2017 To: mlvm-dev(a)openjdk.java.net ============================================================================ Call for Papers: MoreVMs’17 1st Workshop on Modern Language Runtimes, Ecosystems, and VMs Co-located with <Programming> 2017 April, 2017, Brussels, Belgium http://2017.programming-conference.org/track/MoreVMs-2017-papers ============================================================================ The MoreVMs'17 workshop aims bring together programmers from industry and academy to discuss the design, implementation, and usage of modern languages and runtimes. This includes aspects such as reuse of language runtimes, modular implementation, or design and compilation strategies to target existing runtimes. The main goals of the workshop is to bring together both researchers and practitioners and facilitate effective sharing of their respective experiences and ideas on how languages and runtimes are utilized and where they need to improve further. We welcome presentation proposals in the form of extended abstracts discussing experiences, work-in-progress, as well as future visions from the academic as well as industrial perspective. Relevant topics include, but are definitely not limited to, the following: - extensible VM design (compiler- or interpreter-based VMs) - reusable runtime components (e.g. interpreters, garbage collectors, intermediate representations) - static and dynamic compiler techniques - techniques for compilation to high-level languages such as JavaScript - runtimes and mechanisms for interoperability between languages - tooling support (e.g. debugging, profiling, etc.) - programming language development environments and virtual machines - case studies of existing language implementations, virtual machines, and runtime components (e.g. design choices, tradeoffs, etc.) - language implementation challenges and trade-offs (e.g. performance, completeness, etc.) - surveys and applications usage reports to understand runtime usage in the wild - surveys on frameworks and their impact on runtime usage - new research ideas on how we want to build languages in the future ### Workshop Format and Submissions This workshop welcomes the presentation and discussion of new ideas and emerging problems to facilitate interaction among workshop participants and exchange of ideas. We accept presentation proposals in the form of extended abstracts (1-2 pages). Accepted abstracts will be published on the workshop's website before the workshop date. For preparing your abstract, please use the provided author kit: https://github.com/smarr/morevms17-author-kit. It is based on the ACM SIGPLAN Conference Format with 10 point font, and includes a Creative Commons License, which will allow us to publish the abstract on the workshop web site. Please submit abstracts through http://ssw.jku.at/morevms17/ ### Important Dates Abstract submission: 15 February 2017 Author notification: 01 March 2017 Workshop: 3 April 2017 All deadlines are Anywhere on Earth (AoE), i.e. GMT/UTC−12:00 hour ### Program Committee Matthis Grimmer, Oracle Labs Christine H. Flood, Red Hat Tony Hosking, Australian National University Hannes Payer, Purdue University Jeremy Singer, University of Glasgow Mark Stoodley, IBM Canada Sam Tobin-Hochstadt, Indiana University ### Workshop Organizers Laurence Tratt, King's College London, United Kingdom Adam Welc, Oracle Labs, United States Stefan Marr, Johannes Kepler University Linz, Austria -- Stefan Marr Johannes Kepler Universität Linz http://stefan-marr.de/research/ _______________________________________________ mlvm-dev mailing list mlvm-dev(a)openjdk.java.net http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev -- William Leslie Notice: Likely much of this email is, by the nature of copyright, covered under copyright law. You absolutely MAY reproduce any part of it in accordance with the copyright law of the nation you are reading this in. Any attempt to DENY YOU THOSE RIGHTS would be illegal without prior contractual agreement.

1 0

pypy tensorflow compatibility
by Christoph Lassner Jan. 26, 2017

Jan. 26, 2017

Dear pypy devs, I'm a big fan of pypy's ideas and was very happy to see the great improvements introduced with the cpyext library in the latest release. I could out-of-the box compile numpy, scipy and scikit learn, which allows to use pypy easily for machine learning. Tensorflow would be another great package to use for deep learning and other tensor computations. It builds out-of-the box, however it is not possible to import the SWIG generated python module. Looking at it with `ldd -r`, several undefined symbols become apparent, hinting at a missing linked file. The missing symbols are, for example: PyPyInt_FromLong PyPyList_SET_ITEM PyPyErr_Occurred _PyPyInstance_Lookup PyPyDict_SetItem ... so it looks like the pypy standard library it `missing'. Which file would have to be linked against to resolve them? For reference, I also commented on this github issue: https://github.com/tensorflow/tensorflow/issues/252 . Thank you for the infos! Best, Christoph

2 2

PyPy Leysin Winter Sprint: 25/26th Feb. - 4th March 2017
by Armin Rigo Jan. 24, 2017

Jan. 24, 2017

Hi all, The next PyPy sprint will be in Leysin, Switzerland, for the twelveth time. This is a fully public sprint: newcomers and topics other than those proposed below are welcome. Work days: starting 26th Feb (~noon), ending March 4th (~noon). ---------------------------------------- Goals and topics of the sprint ---------------------------------------- The list of topics is very open. * The main topic is Python 3.5 support in PyPy, as most py3.5 contributors should be present. It is also a good topic if you have no or limited experience with PyPy contribution: we can easily find something semi-independent that is not done in py3.5 so far, and do pair-programming with you. * Any other topic is fine too: JIT compiler optimizations, CFFI, the RevDB reverse debugger, improving to speed of your program on PyPy, etc. * And as usual, the main side goal is to have fun in winter sports :-) We can take a day off (for ski or anything else). ------------- More info ------------- For more information, see the complete announcement at: http://bitbucket.org/pypy/extradoc/raw/extradoc/sprintinfo/leysin-winter-20… A bientôt, Armin.

1 0

Leysin sprint?
by Armin Rigo Jan. 20, 2017

Jan. 20, 2017

Hi all, I'm starting to organize the Leysin sprint for this winter. The first note is that the Swiss Python Summit will take place on Feb 17th near Zurich (http://www.python-summit.ch/). I'll give a talk about RevDB, the reverse debugger. One option would be to add a few days of sprint at or near the conference location. That may be a way to attract more people. The other option would be a regular sprint in Leysin. For that case, the dates are still completely open. (It snowed a lot!) Anyone that thinks about coming, please tell me your preferences and dates! A bientôt, Armin.

6 6

Compiling PyPy without JIT
by Frank Wang Jan. 20, 2017

Jan. 20, 2017

Hi, When I compile PyPy in the "goal" folder, I compile it with the following options: pypy ../../rpython/bin/rpython --opt=2 Is this the proper way to compile pypy without JIT, or am I doing something wrong? Thanks, Frank

2 1

cppyy fails to build on gcc 5 and clang
by Tobias Oberstein Jan. 20, 2017

Jan. 20, 2017

Hi guys, please see (reposting here to grab attention as hinted by Armin) https://bitbucket.org/pypy/pypy/issues/2467/cppyy-fails-to-build-on-gcc-5-a… Note: for now I am fine, I managed to build it using gcc 4.9 toolchain. Need to see how far I get with captnproto now .. Cheers, /Tobias

5 33

numpypy include files
by Antonio Cuni Jan. 20, 2017

Jan. 20, 2017

Hello Matti, I am having some troubles with the latest pypy and numpypy: basically, numpy.get_include() returns the wrong directory. I investigated a bit and I think the culprit are these two commits: https://bitbucket.org/pypy/pypy/commits/ad36a29d0fcc https://bitbucket.org/pypy/numpy/commits/26e09b343f Probably it's just a typo in the numpy commit, which specify '_numpy' instead of '_numpypy'. However, before committing the fix I wanted to ask you, to make sure I am not missing anything important :). ciao, Anto

3 3