From anto.cuni at gmail.com Thu Jan 3 09:28:20 2019 From: anto.cuni at gmail.com (Antonio Cuni) Date: Thu, 3 Jan 2019 15:28:20 +0100 Subject: [pypy-dev] Review for blog post In-Reply-To: References: <4711B7AD-CEE2-4FC5-AB04-006EB86D42CC@gmx.de> Message-ID: On Tue, Dec 25, 2018 at 8:59 AM Armin Rigo wrote: > Any clue about why the "purple line" graph, after adding some > gc.disable() and gc.collect_step(), is actually 10% faster than the > baseline? Is that because "purple" runs the GC when "yellow" would be > sleeping waiting for the next input, and you don't count that time in > the performance? If so, maybe we could clarify that we don't expect > better overall performance by adding some gc.disable() and > gc.collect_step() in a program doing just computations---in this case > it works because it is reorganizing tasks in such a way that the GC > runs at a moment where it is "free". > Yes, that's exactly the reason: the GC still runs, but runs "somewhere else" which is not shown in the graph. I added a paragraph to explain it better, thanks for the suggestion. Btw, the final blog post has been published here: https://morepypy.blogspot.com/2019/01/pypy-for-low-latency-systems.html ciao, Anto -------------- next part -------------- An HTML attachment was scrubbed... URL: From renesd at gmail.com Fri Jan 4 06:15:48 2019 From: renesd at gmail.com (=?UTF-8?Q?Ren=C3=A9_Dudfield?=) Date: Fri, 4 Jan 2019 12:15:48 +0100 Subject: [pypy-dev] Review for blog post In-Reply-To: References: <4711B7AD-CEE2-4FC5-AB04-006EB86D42CC@gmx.de> Message-ID: Hellos. Thanks Antonio and everyone. This is a wonderful present! Happy dance. I've been able to replicate the results with some pygame experiments. Less variance, and the spikes are gone. Additionally I was able to try running the GC in a thread when the GIL is released. This resulted in peak performance increasing by 11%. Details here: https://renesd.blogspot.com/2019/01/experiments-with-new-low-latency-pypy.html cheers, -------------- next part -------------- An HTML attachment was scrubbed... URL: From arheops at gmail.com Sat Jan 19 09:48:36 2019 From: arheops at gmail.com (Alexander Merkulov) Date: Sat, 19 Jan 2019 16:48:36 +0200 Subject: [pypy-dev] how to build from source pypy-3 Message-ID: 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From matt at vazor.com Sat Jan 19 16:45:20 2019 From: matt at vazor.com (Matt Billenstein) Date: Sat, 19 Jan 2019 21:45:20 +0000 Subject: [pypy-dev] how to build from source pypy-3 In-Reply-To: References: Message-ID: <010101686813476c-f62247ca-db35-40ea-ae03-6bc6e27df516-000000@us-west-2.amazonses.com> Try building from source tarball, I?ve used this some time ago on arch: https://github.com/mattbillenstein/ve/blob/master/pkgs/available/pypy3.sh M -- Matt Billenstein matt at vazor.com > On Jan 19, 2019, at 6:48 AM, Alexander Merkulov wrote: > > 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 > > > _______________________________________________ > 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 matti.picus at gmail.com Mon Jan 21 11:55:48 2019 From: matti.picus at gmail.com (Matti Picus) Date: Mon, 21 Jan 2019 18:55:48 +0200 Subject: [pypy-dev] ARM cross-compiler build slaves for PyPy Message-ID: An HTML attachment was scrubbed... URL: From nanjekyejoannah at gmail.com Wed Jan 23 04:31:05 2019 From: nanjekyejoannah at gmail.com (joannah nanjekye) Date: Wed, 23 Jan 2019 12:31:05 +0300 Subject: [pypy-dev] =?utf-8?q?save_the_date=3A_PyPy_Sprint_in_D=C3=BCssel?= =?utf-8?q?dorf_February_4-9=2C_2019?= In-Reply-To: <668b0c40-85aa-b55d-af96-ef846e573306@gmx.de> References: <668b0c40-85aa-b55d-af96-ef846e573306@gmx.de> Message-ID: Thanks Carl for Organizing the pypy sprint this year. I really tried again to be at the sprint but unfortunately due to my schedule, I cant attend the sprint again this year. I will be at Pycon in Cleveland. If there happens to be a pypy sprint, I will join. Best, Joannah On Mon, Oct 29, 2018 at 12:59 PM Carl Friedrich Bolz-Tereick wrote: > 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 > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > https://mail.python.org/mailman/listinfo/pypy-dev > -- Joannah Nanjekye +256776468213 F : Nanjekye Captain Joannah S : joannah.nanjekye T : @Captain_Joannah SO : joannah Checkout out and review : Python 2 and 3 compatibility *"You think you know when you learn, are more sure when you can write, even more when you can teach, but certain when you can program." Alan J. Perlis* -------------- next part -------------- An HTML attachment was scrubbed... URL: From anto.cuni at gmail.com Thu Jan 24 12:39:42 2019 From: anto.cuni at gmail.com (Antonio Cuni) Date: Thu, 24 Jan 2019 18:39:42 +0100 Subject: [pypy-dev] Procedure for releasing PyPy Message-ID: 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From armin.rigo at gmail.com Thu Jan 24 13:38:58 2019 From: armin.rigo at gmail.com (Armin Rigo) Date: Thu, 24 Jan 2019 19:38:58 +0100 Subject: [pypy-dev] Procedure for releasing PyPy In-Reply-To: References: Message-ID: Hi Anto, On Thu, 24 Jan 2019 at 18:40, Antonio Cuni wrote: > 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) I think you can in theory do it in less steps by doing only one merge with more complicated edits, if you set things up properly (maybe make the branch, commit the version number 7.0.0-final, and merge that back to default but editing the version to 7.1.0-alpha0 in the merge commit...). Looks like even more of a hack than your 7 steps, though. A bient?t, Armin From matti.picus at gmail.com Thu Jan 24 14:17:17 2019 From: matti.picus at gmail.com (Matti Picus) Date: Thu, 24 Jan 2019 21:17:17 +0200 Subject: [pypy-dev] Procedure for releasing PyPy In-Reply-To: References: Message-ID: <23d0f40a-8249-13c9-011e-ef045789b3ab@gmail.com> On 24/1/19 8:38 pm, Armin Rigo wrote: > Hi Anto, > > On Thu, 24 Jan 2019 at 18:40, Antonio Cuni wrote: >> 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) > I think you can in theory do it in less steps by doing only one merge > with more complicated edits, if you set things up properly (maybe make > the branch, commit the version number 7.0.0-final, and merge that back > to default but editing the version to 7.1.0-alpha0 in the merge > commit...). Looks like even more of a hack than your 7 steps, though. > > > A bient?t, > Armin > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > https://mail.python.org/mailman/listinfo/pypy-dev In the past I did the same, just without step 5, since anyway I needed to merge carefully in step 7 See 2e04adf1b89f-d2c8301f4536 which also renames the whatsnew-head Matti From cfbolz at gmx.de Fri Jan 25 09:29:59 2019 From: cfbolz at gmx.de (Carl Friedrich Bolz-Tereick) Date: Fri, 25 Jan 2019 15:29:59 +0100 Subject: [pypy-dev] =?utf-8?q?save_the_date=3A_PyPy_Sprint_in_D=C3=BCssel?= =?utf-8?q?dorf_February_4-9=2C_2019?= In-Reply-To: References: <668b0c40-85aa-b55d-af96-ef846e573306@gmx.de> Message-ID: <91a85c1d-4c76-2688-14de-536d8ea43279@gmx.de> Hi Joannah, Ah, sorry to hear that you can't make it! Let's hope it works at some point :-). Cheers, Carl Friedrich On 23/01/2019 10:31, joannah nanjekye wrote: > Thanks Carl for Organizing the pypy sprint this year. > > I really tried again to be at the sprint but unfortunately due to my > schedule, I cant attend the sprint again this year. > > I will be at Pycon in Cleveland. If there happens to be a pypy sprint, I > will join. > > Best, > Joannah > > On Mon, Oct 29, 2018 at 12:59 PM Carl Friedrich Bolz-Tereick > > wrote: > > 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 > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > https://mail.python.org/mailman/listinfo/pypy-dev > > > > -- > // > Joannah Nanjekye > +256776468213 > F : Nanjekye?Captain?Joannah > S : joannah.nanjekye > T : @Captain_Joannah > SO : joannah > > Checkout out and review : Python 2 and 3 compatibility > > > > /"You think you know when you learn, are more sure when you can write, > even more when you can teach, but certain when you can program." > Alan J. Perlis/ From webmaster at ICSRoscher.de Sat Jan 26 18:44:33 2019 From: webmaster at ICSRoscher.de (Dr. G. Roscher) Date: Sun, 27 Jan 2019 00:44:33 +0100 Subject: [pypy-dev] =?utf-8?q?save_the_date=3A_PyPy_Sprint_in_D=C3=BCssel?= =?utf-8?q?dorf_February_4-9=2C_2019?= In-Reply-To: References: <668b0c40-85aa-b55d-af96-ef846e573306@gmx.de> Message-ID: Hi, thank you very much for your e-mail and information on the PyPy sprint. I'm newcomer in PyPy however interested in application and further development. G?nther www.ICSRoscher.de Am 23.01.2019 um 10:31 schrieb joannah nanjekye: > Thanks Carl for Organizing the pypy sprint this year. > > I really tried again to be at the sprint but unfortunately due to my > schedule, I cant attend the sprint again this year. > > I will be at Pycon in Cleveland. If there happens to be a pypy sprint, > I will join. > > Best, > Joannah > > On Mon, Oct 29, 2018 at 12:59 PM Carl Friedrich Bolz-Tereick > > wrote: > > 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 > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > https://mail.python.org/mailman/listinfo/pypy-dev > > > > -- > // > Joannah Nanjekye > +256776468213 > F : Nanjekye?Captain?Joannah > S : joannah.nanjekye > T : @Captain_Joannah > SO : joannah > > Checkout out and review : Python 2 and 3 compatibility > > > > /"You think you know when you learn, are more sure when you can write, > even more when you can teach, but certain when you can program." > Alan J. Perlis/ > > _______________________________________________ > 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 webmaster at ICSRoscher.de Thu Jan 31 05:08:24 2019 From: webmaster at ICSRoscher.de (Dr. G. Roscher) Date: Thu, 31 Jan 2019 11:08:24 +0100 Subject: [pypy-dev] ARM cross-compiler build slaves for PyPy In-Reply-To: References: Message-ID: <58bff313-95ee-b741-f4df-2a8a85cb2f58@ICSRoscher.de> Dear colleagues, we are in discussion on CATI for a long time: CATI Computer Aided Trust Internet you can find some first ideas on as example: _http://commentneelie.eu/sentence.php?s=6327_ Now we are designing a new project, based on CATI: Computer Aided Smart & Trust Village Klein Ammensleben - CAST Village K.A. _http://www.icsroscher.de/CAST_Village_K.A.htm_ only in German: _http://www.icsroscher.de/CAST_Village_K.A/News.htm_. I want to use python for the implementation of the CLC ? Common Language Concept. A short history: The programming languages are designed in relation to natural languages as FORTRAN, Algol, Cobol, ? PL/1, Pascal, ? Python. I've designed the CLC in about 1970... in the framework of the design of a CAD/CAM-solution RTV ? Rechnerunterst?tzte Technische Vorbereitung. The CLC with Meta-language, compiler generator and the realized languages has been applied for the machine tool system ROTA FZ 200 since 1974 and some further applications. The CLC is going in the direction of Leibniz 'lingua universalis', however we have the tools today, to realize the 'lingua universalis' by using innovative computer technologies. The idea is, that each formalized natural language is Leibniz 'lingua universalis'. Our natural language is our most valuable and powerful tool! I'm interested in discussion of practical steps for realization by using Python, especially Pypy. Best regards G?nther Klein Ammensleben, 31. January 2019 ICS Dr. G. Roscher GmbH Dr.-Ing., Dipl.-Math. G?nther Roscher CEO Am Kirchberg 6 D - 39326 Klein Ammensleben Tel.: +49 39 202 52 12 6 Fax: +49 39 202 52 12 8 www.ICSRoscher.de webmaster at ICSRoscher.de Am 21.01.2019 um 17:55 schrieb Matti Picus: > > The slaves listed below do not seem very happy. We are also recieving > requests that we update our supplied image to xenial ubuntu 16.04 (I > think they are building precise-compatible binaries which is 12.04). > > It seems it is time to update the instructions at > https://rpython.readthedocs.io/en/latest/arm.html, and revive our ARM > build process. > > Is there something there that we can now simplify? Is there hardware > out there that can build PyPy natively on ARM? Do we need to continue > to support precise? > > > http://buildbot.pypy.org/buildslaves/hhu-cross-raspbianhf > > http://buildbot.pypy.org/buildslaves/hhu-pypy-pi2 > > http://buildbot.pypy.org/buildslaves/hhu-pypy-pi > > > Matti > > > _______________________________________________ > 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: