Mailman 3 August 2016 - pypy-dev

About gurobipy
by Luis José Novoa 31 May '18

31 May '18

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

Any known tricks or effort made to make the PyPy source code build faster?
by Wang, Peter Xihong 07 Sep '16

07 Sep '16

Hi, By default, it appears most of the time during the build/compile process, only 1 single CPU core is busy, signaling missing of parallel compiling. Is there any best known practice to make it faster? Thanks, Peter

4 7

PyPy 5.4 release beginning
by Matti Picus 31 Aug '16

31 Aug '16

Hi. I would like to release PyPy2 v5.4. There is one failing test on linux64 which has to do with test_setrlimit() on bencher4. Are there any other release blockers? Branches to be merged? Matti

3 9

Re: [pypy-dev] Django DateField default value and migrations fail
by Sergey Kurdakov 19 Aug '16

19 Aug '16

Hi William, here is my traceback in console Traceback (most recent call last): File "manage.py", line 10, in <module> execute_from_command_line(sys.argv) File "/usr/local/lib/pypy2.7/dist-packages/django/core/management/__init__.py", line 353, in execute_from_command_line utility.execute() File "/usr/local/lib/pypy2.7/dist-packages/django/core/management/__init__.py", line 345, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/local/lib/pypy2.7/dist-packages/django/core/management/base.py", line 348, in run_from_argv self.execute(*args, **cmd_options) File "/usr/local/lib/pypy2.7/dist-packages/django/core/management/base.py", line 399, in execute output = self.handle(*args, **options) File "/usr/local/lib/pypy2.7/dist-packages/django/core/ management/commands/makemigrations.py", line 150, in handle self.write_migration_files(changes) File "/usr/local/lib/pypy2.7/dist-packages/django/core/ management/commands/makemigrations.py", line 178, in write_migration_files migration_string = writer.as_string() File "/usr/local/lib/pypy2.7/dist-packages/django/db/migrations/writer.py", line 167, in as_string operation_string, operation_imports = OperationWriter(operation). serialize() File "/usr/local/lib/pypy2.7/dist-packages/django/db/migrations/writer.py", line 124, in serialize _write(arg_name, arg_value) File "/usr/local/lib/pypy2.7/dist-packages/django/db/migrations/writer.py", line 76, in _write arg_string, arg_imports = MigrationWriter.serialize(item) File "/usr/local/lib/pypy2.7/dist-packages/django/db/migrations/writer.py", line 357, in serialize item_string, item_imports = cls.serialize(item) File "/usr/local/lib/pypy2.7/dist-packages/django/db/migrations/writer.py", line 433, in serialize return cls.serialize_deconstructed(path, args, kwargs) File "/usr/local/lib/pypy2.7/dist-packages/django/db/migrations/writer.py", line 318, in serialize_deconstructed arg_string, arg_imports = cls.serialize(arg) File "/usr/local/lib/pypy2.7/dist-packages/django/db/migrations/writer.py", line 540, in serialize "topics/migrations/#migration-serializing" % (value, get_docs_version()) ValueError: Cannot serialize: <bound method type.today of <class 'datetime.date'>> Regards Sergey On Wed, Aug 17, 2016 at 10:21 AM, William ML Leslie < william.leslie.ttg(a)gmail.com> wrote: > On 17 August 2016 at 16:50, Sergey Kurdakov <sergey.forum(a)gmail.com> > wrote: > > > > still causes error of the kind: > > > > topics/migrations/#migration-serializing" % (value, get_docs_version()) > > ValueError: Cannot serialize: <bound method type.today of <class > > 'datetime.date' > > Do you get a full traceback? That would be much more useful for > tracking down the problem. > > -- > 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. >

4 8

pypy segfault while playing around with odoo.
by Phyo Arkar 18 Aug '16

18 Aug '16

Hello Pypy team. i am using latest pypy , to try odoo with pypy , to see if it is compatible enough now . it fails while compliling gevent and pyscopg but i switched them to gevent>=1.1 psycopg2cffi>=2.5.4 . that get it going to the point that odoo able to run. But i got to a stop when creating new db and it crashed with segfault. How can i debug segfaults in pypy. Regards, Phyo.

2 2

[Cython] Fwd: Re: [Speed] New benchmark suite for Python (fwd)
by Yury V. Zaytsev 18 Aug '16

18 Aug '16

Hi, Probably most of you have seen that already, but maybe some have not? Any interest in getting, e.g. PyPy releases in? -- Sincerely yours, Yury V. Zaytsev -------- Forwarded Message -------- Subject: Re: [Speed] New benchmark suite for Python Date: Wed, 17 Aug 2016 23:47:29 -0500 From: Zachary Ware <zachary.ware+pydev(AT)gmail.com> To: speed(AT)python.org On Wed, Aug 17, 2016 at 7:37 PM, Victor Stinner wrote: > PyPy, Pyston, Pyjion, Numba, etc. : Hey! it's now time to start to > take a look at my project and test it ;-) Tell me what is broken, what > is missing, and I will try to help you to move your project to this > new benchmark suite! Also, if you're interested in having your interpreter benchmarked on speed.python.org, contact me with clear instructions (preferably in the form of a shell or Python script) on how to build, test, install, and invoke your interpreter from a fresh Ubuntu 16.04 installation. As an example, here's an untested version for CPython 3.x: #!/bin/sh # set up dependencies sudo apt-get build-dep -y python3 sudo apt-get install -y --no-install-recommends mercurial # get the code hg clone https://hg.python.org/cpython cd cpython # build ./configure --prefix=/opt/python/default make -j12 # test make buildbottest TESTOPTS=-j12 # install make install # invoke /opt/python/default/bin/python3 I don't know when I'll have a chance to work on it, but I'd like to get as many projects as possible benchmarked on speed.python.org. Victor: Thanks for getting the new repository set up and for all your work on the new runner! I'm looking forward to trying it out. -- Zach _______________________________________________ Speed mailing list https://mail.python.org/mailman/listinfo/speed

1 0

Re: [pypy-dev] Django DateField default value and migrations fail
by William ML Leslie 17 Aug '16

17 Aug '16

Darn reply-to not being set. Sorry Sergey. On 17 August 2016 at 17:21, William ML Leslie <william.leslie.ttg(a)gmail.com> wrote: > On 17 August 2016 at 16:50, Sergey Kurdakov <sergey.forum(a)gmail.com> wrote: >> >> still causes error of the kind: >> >> topics/migrations/#migration-serializing" % (value, get_docs_version()) >> ValueError: Cannot serialize: <bound method type.today of <class >> 'datetime.date' > > Do you get a full traceback? That would be much more useful for > tracking down the problem. > > -- > 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. -- 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

Django DateField default value and migrations fail
by Sergey Kurdakov 17 Aug '16

17 Aug '16

Hi All, there was a problem https://bitbucket.org/pypy/pypy/issues/2062/inconsistency-in-__repr__-for-d… which caused Django not to make migrations https://code.djangoproject.com/ticket/24779 and the problem was fixed https://bitbucket.org/pypy/pypy/pull-requests/325/fixed-2062-treated-date-d… but it works for correct migrations fine for default values for Django with DateTimeField say class SomeClass(models.Model): date_add = models.DateTimeField(verbose_name=_('date created'), default=timezone.now) but code for DataField with default values from datetime import date class AnotherClass(models.Model): start_date = models.DateField( verbose_name=u'start date', default=date.today, ) end_date = models.DateField( verbose_name=u'end date', default=date.today, ) still causes error of the kind: topics/migrations/#migration-serializing" % (value, get_docs_version()) ValueError: Cannot serialize: <bound method type.today of <class 'datetime.date' so somehow something else should be fixed in the same way it was done - but I cannot figure out where to look at. ( and it works ok with standard Python and Django ) Any tips? Regards Sergey

1 0

jetbrains vulnerability and py3k money
by Maciej Fijalkowski 15 Aug '16

15 Aug '16

So apparently someone just made a big donation to pypy 3k project. Details here: http://blog.saynotolinux.com/blog/2016/08/15/jetbrains-ide-remote-code-exec… Cheers, fijal

3 2

Performance issues of socket.recv_into()
by hubo 09 Aug '16

09 Aug '16

I have been testing network I/O performance of Python and PyPy. I have used the small script in the attachment to test TCP bandwidth between two powerful servers, each has two 10Gb nics with multi-queue hardware support to form a bond, so the physical bandwidth between the servers are 20Gbps. The script is a simple socket client/server with multiple connections on multiple threads. The server tries its best to receive all data, and the client tries its best to send data, after 30 sec, the client stops and calculates the data sent. It seems that there is a huge performance difference for the server to use pypy or CPython: (python = CPython, pypy = PyPy, 100.102.4.7 is my test server IP address, and 32 is the number of concurrent connections) With python testio.py -s on another server: pypy testio.py -c 100.102.4.7 32 total time = 30.05s, total send = 66601 MB, speed = 17.31 Gbps python testio.py -c 100.102.4.7 32 total time = 30.08s, total send = 67008 MB, speed = 17.40 Gbps With pypy testio.py -s on another server: pypy testio.py -c 100.102.4.7 32 total time = 30.36s, total send = 5838 MB, speed = 1.50 Gbps python testio.py -c 100.102.4.7 32 total time = 30.36s, total send = 5742 MB, speed = 1.48 Gbps But when I change while s.recv_into(recv_buf, 0x200000): to while s.recv(0x200000): The performance difference disappears, and both PyPy server and CPython server have good performance (17+Gbps) It is worth to point out that when using socket.recv_into(), PyPy server only uses 100% CPU (one core), while CPython uses much more. Maybe there are some unexpected issues about socket.recv_into, e.g. GIL not released? P.S. it is interesting that though I thought recv_into() should be more efficient thant recv() since it reduces extra object creation / destruction, the test result shows that recv() outperforms recv_into(), even with CPython. With CPython, it seems server with recv() costs less CPU time than recv_into(), but having the same I/O performance. 2016-08-08 hubo

3 6