Re: [Python-Dev] PyPy progress: list of CPython 3.5 crashers and bugs

2016-12-06 Thread Armin Rigo
Hi Nick, On 5 December 2016 at 13:22, Nick Coghlan wrote: > I think 3 omnibus issues would be a reasonable way to go, with the > discussion on those issues then splitting things out to either new > issue reports, or entries in > https://hg.python.org/cpython/file/default/Lib/test/crashers/ (if an

Re: [Python-Dev] PyPy progress: list of CPython 3.5 crashers and bugs

2016-12-06 Thread Armin Rigo
Hi Raymond, On 6 December 2016 at 05:59, Raymond Hettinger wrote: > Also, we use {...} instead of OrderedDict(...). No, at least CPython 3.5.2 uses ``...`` for OrderedDict, and not ``{...}``. Following that example, deques should also use ``...`` instead of ``[...]``. But I bow to your choice

Re: [Python-Dev] PyPy progress: list of CPython 3.5 crashers and bugs

2016-12-05 Thread Serhiy Storchaka
On 05.12.16 20:38, Terry Reedy wrote: I believe that this item in your list is a design choice rather than a bug. "* _collectionsmodule.c: deque_repr uses "[...]" as repr if recursion is detected. I'd suggest that "deque(...)" is clearer---it's not a list." I strongly suspect that Raymond H.

Re: [Python-Dev] PyPy progress: list of CPython 3.5 crashers and bugs

2016-12-05 Thread Raymond Hettinger
> On Dec 5, 2016, at 10:38 AM, Terry Reedy wrote: > > I believe that this item in your list is a design choice rather than a bug. > "* _collectionsmodule.c: deque_repr uses "[...]" as repr if recursion is > detected. I'd suggest that "deque(...)" is clearer---it's not a list." > > I strongly

Re: [Python-Dev] PyPy progress: list of CPython 3.5 crashers and bugs

2016-12-05 Thread Terry Reedy
On 12/5/2016 3:42 AM, Armin Rigo wrote: [what to do with] http://bitbucket.org/pypy/extradoc/raw/extradoc/planning/py3.5/cpython-crashers.rst Independent isssues ultimately need separate tracker issues, but a few collective issues are definitely better than nothing on the tracker. Few free t

Re: [Python-Dev] PyPy progress: list of CPython 3.5 crashers and bugs

2016-12-05 Thread Nick Coghlan
On 5 December 2016 at 18:42, Armin Rigo wrote: > In 3.5.2+ at least, I'm reasonably convinced that all crashers are > real, but I didn't spend the time to come up with actual examples or > patches, beyond the first two items on the list. There are also > non-crasher bugs where the current behavio

[Python-Dev] PyPy progress: list of CPython 3.5 crashers and bugs

2016-12-05 Thread Armin Rigo
Hi all, PyPy 3.5 is progressing. It's still alpha status, but we'll give a progress report on morepypy.blogspot.com at some point. Now the point of this mail is that when exploring the source code of CPython 3.5.2+, we found a large number of crashers and bugs. None of them are essential---othe