Mailman 3 January 2019 - pypy-dev

ARM cross-compiler build slaves for PyPy
by Matti Picus 31 Jan '19

31 Jan '19

2 1

save the date: PyPy Sprint in Düsseldorf February 4-9, 2019
by Carl Friedrich Bolz-Tereick 26 Jan '19

26 Jan '19

Hi all, I'll do a more proper sprint announcement soon, but to give some advance warning, I am organizing a PyPy sprint at the Heinrich-Heine-Universität Düsseldorf from February 4-9, 2019 (both days inclusive). The last sprint we had there was in 2010 :-). Cheers, Carl Friedrich

3 3

Procedure for releasing PyPy
by Antonio Cuni 24 Jan '19

24 Jan '19

Hi, I have starting the procedure for doing a 7.0 release, I'd like to have some feedback on the process, in particular for bumping the version number. If we don't do it correctly the risk is to revert the version change when we do a merge between default and the release branch or viceversa, which resulting in the need of commits like this: https://bitbucket.org/pypy/pypy/commits/6a1df86a6f7a So what I did was this: 1) hg up -r default 2) hg branch release-pypy2.7-7.x 3) bump the version number to 7.0.0-final (commit d47849ba8135) 4) hg up -r default 5) hg merge release-pypy2.7-7.x (commit c4dc91f2e037) 6) bump the version number (on default) to 7.1.0-alpha0 (commit f3cf624ab14c) 7) merge default into release-pypy2.7-7.x, editing the files before the commit to avoid changing the version again (commit 7986159ef4d8) This way we should be able to freely merge default into release and viceversa without problems. Also, what to do with pypy3.5? I think that at this point the best way would be to merge default into py3.5, and to the same commit dance for release-pypy3.5-7.x. I don't like this complicate procedure, but it is the only I could come up with: do you think it's reasonable? If so, I'll update how-to-release.rst accordingly. Can we think of something better? To start with, ideally we should have the version number in a single place instead of 3 (4 if you also count the hg branch name) :( ciao, Anto

3 2

how to build from source pypy-3
by Alexander Merkulov 19 Jan '19

19 Jan '19

hi i need pypy compatible to python3(django2.0) on centos portable versions and ubuntu version not work, centos have only 2.7 pypy question is *how to get python3 compatible result? * I got 2.7-compatible tree when i get source like this hg clone http://bitbucket.org/pypy/pypy pypy pypy get-pip.py /usr/lib64/pypy-5.0.1/bin/pip install virtualenv pypy -m virtualenv /tmp/pypy27_venv/ source /tmp/pypy27_venv/bin/activate pip install -r pypy/requirements.txt cd /usr/src/pypy/pypy/goal pypy ../../rpython/bin/rpython --opt=jit after build copleate i get /tmp/usession-default-19/build/pypy-3-centos7/bin/pypy Python 2.7.13 (0873ec79aa36, Jan 19 2019, 13:33:23) [PyPy 6.1.0-alpha0 with GCC 4.8.5 20150623 (Red Hat 4.8.5-36)] on linux2

2 1

Review for blog post
by Antonio Cuni 04 Jan '19

04 Jan '19

Hi, better to ask it here since I suspect that most people won't be much on irc during the next days: I wrote a blog post draft about the gc-disable branch which I have recently merged; it is available on extradoc: https://bitbucket.org/pypy/extradoc/src/extradoc/blog/draft/2018-12-gc-disa… Reviews, comments and remarks are welcome. I think I'd like to publish it after Christmas. ciao, Anto

4 4