Mailman 3 January 2018 - pypy-dev

pypy 5.10.1 release candidates are up, please try them out
by Matti Picus Jan. 13, 2018

Jan. 13, 2018

I have uploaded pypy3.5 v5.10.1 bug-fix release candidates to https://bitbucket.org/pypy/pypy/downloads please test them out. The sha256 hashes are available at the end of the source for the website https://bitbucket.org/pypy/pypy.org/src/extradoc/source/download.txt?at=ext… Any comments/corrections to the release notice would also be appreciated http://doc.pypy.org/en/latest/release-v5.10.1.html Matti

4 6

PyPy sprint in Poland
by Maciej Fijalkowski Jan. 9, 2018

Jan. 9, 2018

Hi Everyone. It looks like I would be in Europe through April and maybe May. Anyone fancy a sprint somewhere in Poland? Potential venues: * we can have a sprint at my climbing spot - it's quite a problem to get to (~2-3h by train from either Prague or Wroclaw), but it's incredibly lovely at this time of the year. There is a venue and internet that we can use. Limited restaurant options are a con. Endless hiking options are a plus. * we can try to organize a venue in Warsaw. We don't have a … [View More]

4 3

Leysin Winter sprint: 17-24 March 2018
by Armin Rigo Jan. 8, 2018

Jan. 8, 2018

===================================================================== PyPy Leysin Winter Sprint (17th - 24th March 2018) ===================================================================== The next PyPy sprint will be in Leysin, Switzerland, for the thirteenth time. This is a fully public sprint: newcomers and topics other than those proposed below are welcome. (Note: this sprint is independent from the suggested April-May sprint in Poland.) ------------------------------ Goals and … [View More]topics of the sprint ------------------------------ The list of topics is open, but here is our current list: - cffi tutorial/overview rewrite - py3 test runners are too complicated - make win32 builds green - make packaging more like cpython/portable builds - get CI builders for PyPy into mainstream projects (Numpy, Scipy, lxml, uwsgi) - get more of scientific stack working (tensorflow?) - cpyext performance improvements - General 3.5 and 3.6 improvements - JIT topics: guard-compatible, and the subsequent research project to save and reuse traces across processes - finish unicode-utf8 - update www.pypy.org, speed.pypy.org (web devs needed) As usual, the main side goal is to have fun in winter sports :-) We can take a day off (for ski or anything else). ----------- Exact times ----------- Work days: starting March 18th (~noon), ending March 24th (~noon). I have pre-booked the week from Saturday March 17th to Saturday March 24th. If it is possible for you to arrive Sunday before mid-afternoon, then you can get a booking from Sunday only. The break day should be around Wednesday. It is fine to stay a few more days on either side, or conversely to book for a part of that time only. ----------------------- Location & Accomodation ----------------------- Leysin, Switzerland, "same place as before". Let me refresh your memory: both the sprint venue and the lodging will be in a pair of chalets built specifically for bed & breakfast: http://www.ermina.ch/. You can also arrange your own lodging elsewhere (as long as you are in Leysin, you cannot be more than a 15 minutes walk away from the sprint venue). Please *confirm* that you are coming so that we can adjust the reservations as appropriate. The options of rooms are a bit more limited than on previous years because the place for bed-and-breakfast is shrinking; but we should still have enough room for us. The price is around 60 CHF, breakfast included, in shared rooms (3 or 4 people). If there are people that would prefer a double or single room, please contact me and we'll see what choices you have. There is a choice of hotels in Leysin, starting at 65 CHF the room. Please register by Mercurial:: https://bitbucket.org/pypy/extradoc/ https://bitbucket.org/pypy/extradoc/raw/extradoc/sprintinfo/leysin-winter-2… or on the pypy-dev mailing list if you do not yet have check-in rights: http://mail.python.org/mailman/listinfo/pypy-dev You need a Swiss-to-(insert country here) power adapter. There will be some Swiss-to-EU adapters around, and at least one EU-format power strip. [View Less]

1 0

Re: [pypy-dev] Mysterious IndexError in service running with PyPy
by Armin Rigo Jan. 8, 2018

Jan. 8, 2018

Hi Hubo, On 5 January 2018 at 09:19, hubo <hubo(a)jiedaibao.com> wrote: > This issue is reproduced on PyPy 5.9. I will collect running information > (local variables, etc.) for hints. As I said, this is unlikely to help (unless of course there is a bug in your program logic and you find it by looking at the value of local variables). We need a way to reproduce the problem ourselves, and then we can attack it with lower-level tools like gdb, rr, and so on. Without it, we can't do … [View More]

2 1

pypy 5.10 release
by Matt Billenstein Jan. 4, 2018

Jan. 4, 2018

Hi all, So the general issue seems to be Apple not shipping the header files for these shared libs-- not linking to the brew libffi works (I'm not sure it's linking to the system libffi at all now however -- or if it needs to), but then the problem became openssl headers. I've hacked around this by manually placing the LibreSSL 2.2.7 headers in /usr/include -- this is what matches the 'openssl' binary on my High Sierra system. mattb@mattb-mbp2:/Users/pypy/buildarea $ openssl version LibreSSL … [View More]2.2.7 So now I have a build with no brew linkage dependencies: mattb@mattb-mbp2:/Users/pypy/buildarea $ find . -name 'libpypy*' -type f | xargs otool -L ./pypy-c-jit-macosx-x86-64/build/pypy/goal/libpypy-c.dylib: @rpath/libpypy-c.dylib (compatibility version 0.0.0, current version 0.0.0) /usr/lib/libutil.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1252.0.0) /usr/lib/libbz2.1.0.dylib (compatibility version 1.0.0, current version 1.0.5) /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.11) /usr/lib/libssl.35.dylib (compatibility version 36.0.0, current version 36.0.0) /usr/lib/libcrypto.35.dylib (compatibility version 36.0.0, current version 36.0.0) /usr/lib/libexpat.1.dylib (compatibility version 7.0.0, current version 8.0.0) /usr/lib/libffi.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libncurses.5.4.dylib (compatibility version 5.4.0, current version 5.4.0) Which is closer to an older release: mattb@mattb-mbp2:/Users/pypy/buildarea $ otool -L ~pypy/pypy2-v5.9.0-osx64/bin/libpypy-c.dylib /Users/pypy/pypy2-v5.9.0-osx64/bin/libpypy-c.dylib: @rpath/libpypy-c.dylib (compatibility version 0.0.0, current version 0.0.0) /usr/lib/libutil.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1197.1.1) /usr/lib/libbz2.1.0.dylib (compatibility version 1.0.0, current version 1.0.5) /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.5) /usr/lib/libssl.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8) /usr/lib/libcrypto.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8) /usr/lib/libexpat.1.dylib (compatibility version 7.0.0, current version 7.2.0) /usr/lib/libffi.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libncurses.5.4.dylib (compatibility version 5.4.0, current version 5.4.0) The problem now is that probably this build won't work on older OSX releases with only older openssl versions... Apple does ship the older dylib: mattb@mattb-mbp2:/Users/pypy/buildarea $ ls -l /usr/lib/*ssl* -rwxr-xr-x 1 root wheel 1217072 Oct 25 09:37 /usr/lib/libboringssl.dylib -rwxr-xr-x 1 root wheel 392912 Oct 25 09:37 /usr/lib/libssl.0.9.7.dylib -rwxr-xr-x 1 root wheel 630144 Oct 25 09:37 /usr/lib/libssl.0.9.8.dylib -rw-r--r-- 1 root wheel 947104 Oct 25 09:37 /usr/lib/libssl.35.dylib -rw-r--r-- 1 root wheel 890800 Oct 25 09:37 /usr/lib/libssl.43.dylib lrwxr-xr-x 1 root wheel 15 Nov 3 01:59 /usr/lib/libssl.dylib -> libssl.35.dylib So maybe linking to that and manually supplying the openssl 0.9.8 headers is desirable? Let me know if anyone has a better idea of how to go about this. thx m > On 31/12/2017 10:59 AM, blanch wrote: > > > hello, thanks for the 5.10 release! > > > > just a problem on the mac: it seems that the pypy3 binaries are linked against a libffi provided by a package manager (homebrew?), since dyld is looking for /usr/local/opt/libffi/lib/libffi.6.dylib (see below the error reported and otool output). > > since i do not use homebrew, it fails to execute on my mac. > > i have the problem with the pypy3 pre-sierra version, but according to a comment on the morepypy blog [0], the problem exist for high sierra version of pypy3 and for pypy2 (which looks for /usr/local/opt/openssl/lib/libssl.1.0.0.dylib) > > > > thanks again for your work, and best wishes for 2018! > > > > renaud > > > > 0. https://www.blogger.com/comment.g?blogID=3971202189709462152&postID=3223396… > We need someone who uses that OS and knows how to fix it to help us out. > Any ideas? SInce the same buildslave creates our pypy2 binaries as well, > I guess the problem occurs there too. > If anyone can help out, please issue a pull request or at least file an > issue on https://bitbucket.org/pypy/pypy/issues (login required) with a > proposal for a fix. -- Matt Billenstein matt(a)vazor.com http://www.vazor.com/ [View Less]

7 19

Re: [pypy-dev] Pypy's facelift and certificate issues
by Kotrfa Jan. 3, 2018

Jan. 3, 2018

Yeah, that's a very good point worth mentioning. I am not against an idea going just with a static version. po 1. 1. 2018 v 18:05 odesílatel anatoly techtonik <techtonik(a)gmail.com> napsal: > On Sat, Dec 30, 2017 at 12:41 PM, Kotrfa <kotrfa(a)gmail.com> wrote: > > Hey, > > > > as I said, I am not a professional, but I would be willing to help with > the > > site. I have built couple of websites in Django/Wagtail (or plain HTML), > > have some … [View More]

2 3

Re: [pypy-dev] Pypy's facelift and certificate issues
by John Camara Jan. 3, 2018

Jan. 3, 2018

http://packages.pypy.org/ Question about the web site -- does PyPy currently have anything similar to > this page for Python 3? > http://py3readiness.org/ > > I think a page like this, showing which major libraries are compatible > with PyPy, could really help drive adoption of PyPy. I know for our team, > the Python 3 page was a strong reason we felt "safe" starting to make the > switch to Python 3. > I'm not sure how we'd get this information about PyPy library > … [View More]

5 6

Re: [pypy-dev] pypy 5.10 release
by blanch Jan. 2, 2018

Jan. 2, 2018

hello, thanks for the 5.10 release! just a problem on the mac: it seems that the pypy3 binaries are linked against a libffi provided by a package manager (homebrew?), since dyld is looking for /usr/local/opt/libffi/lib/libffi.6.dylib (see below the error reported and otool output). since i do not use homebrew, it fails to execute on my mac. i have the problem with the pypy3 pre-sierra version, but according to a comment on the morepypy blog [0], the problem exist for high sierra version of … [View More]

2 1

Pypy's facelift and certificate issues
by Kotrfa Jan. 1, 2018

Jan. 1, 2018

Hi, thank you for all your hard work, I really appreciate it. Firstly, it seems that the website SSL certificate expired or something. At my latest Chromium reports "Not secure". Secondly, I totally understand that there are more pressing issues than cool website, but the current design and functionality is IMO really putting people off. So I am going to through away some things which seems weird to ME (and I understand it's subjective - please take it as a friendly feedback). The jQuery … [View More]

3 6