From fijall at gmail.com Wed Nov 1 05:18:08 2017 From: fijall at gmail.com (Maciej Fijalkowski) Date: Wed, 1 Nov 2017 10:18:08 +0100 Subject: [pypy-dev] Leysin Winter sprint In-Reply-To: References: Message-ID: Hi Anto With the climate change >15/03 is not a very good winter sprint, is it? On Sun, Oct 29, 2017 at 11:47 PM, Antonio Cuni wrote: > Hi Armin, > > I would probably be unable to come during the first two weeks of march, so > for me the preference is basically "anything >= 15/03" > > On Sun, Oct 29, 2017 at 11:11 PM, Armin Rigo wrote: >> >> Hi all, >> >> I'm trying to organise the next winter sprint a bit in advance. It >> might tentatively be occurring in March 2018. If people have >> preferences for the exact week, please do tell :-) >> >> >> A bient?t, >> >> Armin. >> _______________________________________________ >> pypy-dev mailing list >> pypy-dev at python.org >> https://mail.python.org/mailman/listinfo/pypy-dev > > > > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > https://mail.python.org/mailman/listinfo/pypy-dev > From anto.cuni at gmail.com Wed Nov 1 05:58:45 2017 From: anto.cuni at gmail.com (Antonio Cuni) Date: Wed, 1 Nov 2017 10:58:45 +0100 Subject: [pypy-dev] Leysin Winter sprint In-Reply-To: References: Message-ID: I don't know the exact climate of behavior of Switzerland, but in the past few winters in Italy it has basically been a lottery; you just don't know when it's going to be cold or to have snow. For example, last year I skied on snow which ranged from ok-ish to very bad from december to april, and then I found the best snow/climate of the season on 2 May. But anyway, from my very personal point of view "sprint in Leysin with potentially higher temperatures" > "no sprint in Leysin" ? On Wed, Nov 1, 2017 at 10:18 AM, Maciej Fijalkowski wrote: > Hi Anto > > With the climate change >15/03 is not a very good winter sprint, is it? > > On Sun, Oct 29, 2017 at 11:47 PM, Antonio Cuni > wrote: > > Hi Armin, > > > > I would probably be unable to come during the first two weeks of march, > so > > for me the preference is basically "anything >= 15/03" > > > > On Sun, Oct 29, 2017 at 11:11 PM, Armin Rigo > wrote: > >> > >> Hi all, > >> > >> I'm trying to organise the next winter sprint a bit in advance. It > >> might tentatively be occurring in March 2018. If people have > >> preferences for the exact week, please do tell :-) > >> > >> > >> A bient?t, > >> > >> Armin. > >> _______________________________________________ > >> pypy-dev mailing list > >> pypy-dev at python.org > >> https://mail.python.org/mailman/listinfo/pypy-dev > > > > > > > > _______________________________________________ > > pypy-dev mailing list > > pypy-dev at python.org > > https://mail.python.org/mailman/listinfo/pypy-dev > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From me at manueljacob.de Sat Nov 4 10:19:07 2017 From: me at manueljacob.de (Manuel Jacob) Date: Sat, 04 Nov 2017 15:19:07 +0100 Subject: [pypy-dev] Leysin Winter sprint In-Reply-To: References: Message-ID: Hi, Between the second week of February and the first week of April I'm mostly freed from regular university duties. In the middle of March would probably be most suitable for me. I think it's fine if the temperatures are a bit higher (disclaimer: I'm not planning to go skiing, I prefer hiking). -Manuel On 2017-10-29 23:11, Armin Rigo wrote: > Hi all, > > I'm trying to organise the next winter sprint a bit in advance. It > might tentatively be occurring in March 2018. If people have > preferences for the exact week, please do tell :-) > > > A bient?t, > > Armin. > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > https://mail.python.org/mailman/listinfo/pypy-dev From matti.picus at gmail.com Mon Nov 6 10:45:19 2017 From: matti.picus at gmail.com (Matti Picus) Date: Mon, 6 Nov 2017 17:45:19 +0200 Subject: [pypy-dev] RPython proposed deprecation: translator.platform .distutils_platform Message-ID: <0fdb7f15-468a-be3e-f99c-8fcbcce65828@gmail.com> An HTML attachment was scrubbed... URL: From anto.cuni at gmail.com Thu Nov 9 04:07:02 2017 From: anto.cuni at gmail.com (Antonio Cuni) Date: Thu, 9 Nov 2017 10:07:02 +0100 Subject: [pypy-dev] [pypy-commit] pypy default: "eh". On pypy we need to be careful in which order we have pendingblocks. In-Reply-To: <5a03b59b.c39cdf0a.b72ee.bc53@mx.google.com> References: <5a03b59b.c39cdf0a.b72ee.bc53@mx.google.com> Message-ID: Hi, I suppose that the explanation that you put in the commit message should also go in a comment inside the source code, else when someone sees it it's just obscure. Also, it'd be nice to have some tests about ShuffleDict :) On Thu, Nov 9, 2017 at 2:55 AM, fijal wrote: > Author: fijal > Branch: > Changeset: r92981:cb9634421fa2 > Date: 2017-11-08 17:54 -0800 > http://bitbucket.org/pypy/pypy/changeset/cb9634421fa2/ > > Log: "eh". On pypy we need to be careful in which order we have > pendingblocks. Otherwise we end up in a setup where we have blocks > a, b and c where a and b are blocked because c needs to add an > attribute, but c is never appended since popitem() would always > return an a or b. I wonder if the same condition can be repeated on > CPython, but I cannot. Unclear how would you write a test for it > since it depends on dictionary order. > > diff --git a/rpython/annotator/annrpython.py b/rpython/annotator/ > annrpython.py > --- a/rpython/annotator/annrpython.py > +++ b/rpython/annotator/annrpython.py > @@ -15,10 +15,34 @@ > typeof, s_ImpossibleValue, SomeInstance, intersection, difference) > from rpython.annotator.bookkeeper import Bookkeeper > from rpython.rtyper.normalizecalls import perform_normalizations > +from collections import deque > > log = AnsiLogger("annrpython") > > > +class ShuffleDict(object): > + def __init__(self): > + self._d = {} > + self.keys = deque() > + > + def __setitem__(self, k, v): > + if k in self._d: > + self._d[k] = v > + else: > + self._d[k] = v > + self.keys.append(k) > + > + def __getitem__(self, k): > + return self._d[k] > + > + def popitem(self): > + key = self.keys.popleft() > + item = self._d.pop(key) > + return (key, item) > + > + def __nonzero__(self): > + return bool(self._d) > + > class RPythonAnnotator(object): > """Block annotator for RPython. > See description in doc/translation.txt.""" > @@ -33,7 +57,7 @@ > translator = TranslationContext() > translator.annotator = self > self.translator = translator > - self.pendingblocks = {} # map {block: graph-containing-it} > + self.pendingblocks = ShuffleDict() # map {block: > graph-containing-it} > self.annotated = {} # set of blocks already seen > self.added_blocks = None # see processblock() below > self.links_followed = {} # set of links that have ever been > followed > _______________________________________________ > pypy-commit mailing list > pypy-commit at python.org > https://mail.python.org/mailman/listinfo/pypy-commit > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fijall at gmail.com Thu Nov 9 16:14:21 2017 From: fijall at gmail.com (Maciej Fijalkowski) Date: Thu, 9 Nov 2017 21:14:21 +0000 Subject: [pypy-dev] RPython proposed deprecation: translator.platform .distutils_platform In-Reply-To: <0fdb7f15-468a-be3e-f99c-8fcbcce65828@gmail.com> References: <0fdb7f15-468a-be3e-f99c-8fcbcce65828@gmail.com> Message-ID: +1 On Mon, Nov 6, 2017 at 3:45 PM, Matti Picus wrote: > In addition to the arm, bsd, cygwin, darwin, freebsd, linux, maemo (really?) > netbsd, openbsd, posix, and windows rpython/translator/platforms, we have > one called "distutils_platform" that is allegedly supposed to allow one to > specify the target platform and use distutils factilities to compile an > RPython program for that target. I would like to deprecate (remove) it. The > trigger for my proposal is the need to import setuptools to enable disutils > to find the MSVC compiler on a system that uses the "Visual for Python" > compilers, which I came across when setting up a new win32 build slave. > Rather than try and fix the problem I would prefer to remove the platform. > > Any objections? > Matti > > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > https://mail.python.org/mailman/listinfo/pypy-dev > From dynamicgl at gmail.com Fri Nov 10 12:32:09 2017 From: dynamicgl at gmail.com (Gelin Yan) Date: Sat, 11 Nov 2017 01:32:09 +0800 Subject: [pypy-dev] a question about translating pypy for raspberry pi Message-ID: Hi All I followed the instructions from http://doc.pypy.org/en/release-2.4.x/arm.html and succeeded to build a pypy (it works in qemu environment) when I copied to my raspberry pi 3 (OS: raspbian) and tried to run pypy the program complained: "error while loading shared libraries: libpypy-c.so: cannot open shared object file: No such file or directory" Did I do something wrong here? Regards gelin yan -------------- next part -------------- An HTML attachment was scrubbed... URL: From anto.cuni at gmail.com Fri Nov 10 12:50:57 2017 From: anto.cuni at gmail.com (Antonio Cuni) Date: Fri, 10 Nov 2017 18:50:57 +0100 Subject: [pypy-dev] a question about translating pypy for raspberry pi In-Reply-To: References: Message-ID: Maybe it's a stupid advice but: are you sure to have copied also libpypy-c.so to the raspberry? Is it in the same directory as the "pypy" or "pypy-c" executable? I suggest you to run the script "pypy/tool/release/package.py", which builds a tarball containing all the necessary stuff (including the stdlib). Then you can simply untar on the raspberry and run it. You should run it this way: python package.py --archive-name=my-pypy-for-rpi On Fri, Nov 10, 2017 at 6:32 PM, Gelin Yan wrote: > Hi All > > I followed the instructions from > > http://doc.pypy.org/en/release-2.4.x/arm.html > > and succeeded to build a pypy (it works in qemu environment) > > when I copied to my raspberry pi 3 (OS: raspbian) and tried to run pypy > > the program complained: > > "error while loading shared libraries: libpypy-c.so: cannot open shared > object file: No such file or directory" > > Did I do something wrong here? > > Regards > > gelin yan > > > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > https://mail.python.org/mailman/listinfo/pypy-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From anto.cuni at gmail.com Fri Nov 10 14:53:39 2017 From: anto.cuni at gmail.com (Antonio Cuni) Date: Fri, 10 Nov 2017 20:53:39 +0100 Subject: [pypy-dev] a question about translating pypy for raspberry pi In-Reply-To: References: Message-ID: Hi Gelin, Please make sure to include pypy-dev in the CC, so that the others can read the answer. I suggest you to try two things: 1. Try to run pypy under strace: this way you can see where it tries to find .so libraries and which one it cannot find (it might be a dependency of libpypy-c itself) 2. Try a nightly build from here: http://buildbot.pypy.org/nightly/trunk/ Il 10 nov 2017 7:51 PM, "Gelin Yan" ha scritto: > > > On Sat, Nov 11, 2017 at 1:50 AM, Antonio Cuni wrote: > >> Maybe it's a stupid advice but: are you sure to have copied also >> libpypy-c.so to the raspberry? >> Is it in the same directory as the "pypy" or "pypy-c" executable? >> >> I suggest you to run the script "pypy/tool/release/package.py", which >> builds a tarball containing all the necessary stuff (including the stdlib). >> Then you can simply untar on the raspberry and run it. >> >> You should run it this way: >> python package.py --archive-name=my-pypy-for-rpi >> >> >> >> >> > Hi Antonio > > Yes. I did run the package.py to make a pypy package for ARM. I did > check libpypy-c.so which is placed on the same directory of where pypy is. > > Regards > > gelin yan > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From zlists at ns.sympatico.ca Mon Nov 13 15:20:16 2017 From: zlists at ns.sympatico.ca (zlists at ns.sympatico.ca) Date: Mon, 13 Nov 2017 16:20:16 -0400 Subject: [pypy-dev] bug in socket.py in pypy3-5.8_beta Message-ID: <20171113202016.GA4555@jdiamond-mb.acadiau.ca> (I'm sure somewhere there is a proper place to report a bug, but I gave up after hunting for a few minutes.) socket.py has the code import platform kern_version = tuple(map(int, platform.release().partition('-')[0].split('.'))) which is buggy, because the kernel version is not necessarily completely numeric. Check out CONFIG_LOCALVERSION in any kernel config. Thanks. Jim From armin.rigo at gmail.com Mon Nov 13 18:00:20 2017 From: armin.rigo at gmail.com (Armin Rigo) Date: Tue, 14 Nov 2017 00:00:20 +0100 Subject: [pypy-dev] bug in socket.py in pypy3-5.8_beta In-Reply-To: <20171113202016.GA4555@jdiamond-mb.acadiau.ca> References: <20171113202016.GA4555@jdiamond-mb.acadiau.ca> Message-ID: Hi Jim, On 13 November 2017 at 21:20, wrote: > (I'm sure somewhere there is a proper place to report a bug, but I > gave up after hunting for a few minutes.) > > socket.py has the code > > import platform > kern_version = tuple(map(int, platform.release().partition('-')[0].split('.'))) Grepping for ``platform.release``, I can only find similar code in ``lib-python/3/test/support/__init__.py``. I'm not sure that's the place you mean. If it really is, then it comes straight from CPython, and the corresponding problem should be reported to CPython instead at bugs.python.org (after checking that it still exists in the latest CPython release). A bient?t, Armin. From fijall at gmail.com Wed Nov 15 02:26:07 2017 From: fijall at gmail.com (Maciej Fijalkowski) Date: Wed, 15 Nov 2017 08:26:07 +0100 Subject: [pypy-dev] Let's fix buildbots Message-ID: Hi everyone I recently looked here: http://buildbot.pypy.org/summary and it looks quite grim. Can we stop for a second and fix most of those so we have some level of greenness around? Cheers, fijal From armin.rigo at gmail.com Sun Nov 19 17:07:02 2017 From: armin.rigo at gmail.com (Armin Rigo) Date: Sun, 19 Nov 2017 23:07:02 +0100 Subject: [pypy-dev] [pypy-commit] pypy default: "eh". On pypy we need to be careful in which order we have pendingblocks. In-Reply-To: References: <5a03b59b.c39cdf0a.b72ee.bc53@mx.google.com> Message-ID: Hi, On 9 November 2017 at 10:07, Antonio Cuni wrote: > I suppose that the explanation that you put in the commit message should > also go in a comment inside the source code, else when someone sees it it's > just obscure. Done in d00a16ef468f. I reverted the addition of ShuffleDict, and instead made a two-lines tweak to the logic at the place where ordering matters---with a long comment :-) A bient?t, Armin. From fijall at gmail.com Mon Nov 20 05:16:00 2017 From: fijall at gmail.com (Maciej Fijalkowski) Date: Mon, 20 Nov 2017 11:16:00 +0100 Subject: [pypy-dev] [pypy-commit] pypy default: "eh". On pypy we need to be careful in which order we have pendingblocks. In-Reply-To: References: <5a03b59b.c39cdf0a.b72ee.bc53@mx.google.com> Message-ID: ah indeed, that's a much better fix :-) The original was done a bit haphazardly :-) On Sun, Nov 19, 2017 at 11:07 PM, Armin Rigo wrote: > Hi, > > On 9 November 2017 at 10:07, Antonio Cuni wrote: >> I suppose that the explanation that you put in the commit message should >> also go in a comment inside the source code, else when someone sees it it's >> just obscure. > > Done in d00a16ef468f. I reverted the addition of ShuffleDict, and > instead made a two-lines tweak to the logic at the place where > ordering matters---with a long comment :-) > > > A bient?t, > > Armin. From armin.rigo at gmail.com Mon Nov 27 08:40:30 2017 From: armin.rigo at gmail.com (Armin Rigo) Date: Mon, 27 Nov 2017 14:40:30 +0100 Subject: [pypy-dev] Sprint in Leysin: 17-24 March 2018 (very probably) Message-ID: Hi all, The next sprint in Leysin is now planned on the week of the 17-24 March 2018. Please let me know if there is a good reason to change it. A bient?t, Armin.