From issues-reply at bitbucket.org  Sat Oct  4 18:58:26 2014
From: issues-reply at bitbucket.org (Ran Gutin)
Date: Sat, 04 Oct 2014 16:58:26 -0000
Subject: [pypy-issue] Issue #1878: cPython and PyPy produce different
 results when run on the same code (pypy/pypy)
Message-ID: <20141004165826.7694.73917@app10.ash-private.bitbucket.org>

New issue 1878: cPython and PyPy produce different results when run on the same code
https://bitbucket.org/pypy/pypy/issue/1878/cpython-and-pypy-produce-different-results

Ran Gutin:

This is my solution to Project Euler problem 95.

```
#!python
import time

def euler95():
  def chainLength(i):
    start = i
    sofar = set()
    
    length = 0
    while i not in sofar and i <= 10**6:
      sofar = sofar.union({i})
      #print(sofar)
      i = sums[i]
      length += 1
    
    if i == start:
      return length
    return 0
    
  sums = [sum(factors) for factors in factorsOfEverythingBelow(10**6+1)]
  
  print("found sums")
  return max(range(10**6), key = chainLength)


def factorsOfEverythingBelow(n):
  factors = []
  for i in range(n): factors += [[1]]
  for i in range(2,n):
    for j in range(i+i,n,i):
      factors[j] += [i]
  return factors

def euler(n, f):
  begin = time.time()
  print("Euler",n,":",f(),"in",time.time()-begin,"seconds")
```

Start the program with:


```
#!python

euler(95,euler95)
```

CPython prints out:

found sums
Euler 95 : 14316 in 19.938631057739258 seconds

PyPy prints out:

found sums
Euler 95 : 1 in 6.321170806884766 seconds

CPython gives the right answer to https://projecteuler.net/problem=62 and PyPy gives the wrong answer.

Given another Project Euler problem:


```
#!python

def period_sqrt(n):
  if float(sqrt(n)).is_integer():
    return 0
  m = 0
  d = 1
  a = int(n**0.5)
  a0 = a
  
  mdset = set()
  
  period = 0
  while True:
    m = d*a - m
    d = (n - m**2)/d
    a = int((a0 + m)/d)
    if (m,d) in mdset:
      return period
    mdset = mdset.union({(int(m),int(d))})
    period += 1

def euler64():
  return sum(1 for i in range(1,10**4+1) if period_sqrt(i) % 2 == 1)
```

Both CPython and PyPy give the right result.



From issues-reply at bitbucket.org  Sun Oct  5 09:36:51 2014
From: issues-reply at bitbucket.org (sbehnel)
Date: Sun, 05 Oct 2014 07:36:51 -0000
Subject: [pypy-issue] Issue #1879: cpyext lacks PyBytes_Type in pypy3
	(pypy/pypy)
Message-ID: <20141005073651.23218.82141@app05.ash-private.bitbucket.org>

New issue 1879: cpyext lacks PyBytes_Type in pypy3
https://bitbucket.org/pypy/pypy/issue/1879/cpyext-lacks-pybytes_type-in-pypy3

sbehnel:

cpyext doesn't expose PyBytes_Type in pypy3. My guess is that the fix is to simply replace

        "PyString_Type": "space.w_str",

with

        "PyBytes_Type": "space.w_bytes",

in pypy/module/cpyext/api.py.




From issues-reply at bitbucket.org  Sun Oct  5 20:51:00 2014
From: issues-reply at bitbucket.org (Dan Stromberg)
Date: Sun, 05 Oct 2014 18:51:00 -0000
Subject: [pypy-issue] Issue #1880: setsocket SO_RCVBUF with 64 bit int works,
 probably shouldn't (pypy/pypy)
Message-ID: <20141005185100.17044.40710@app01.ash-private.bitbucket.org>

New issue 1880: setsocket SO_RCVBUF with 64 bit int works, probably shouldn't
https://bitbucket.org/pypy/pypy/issue/1880/setsocket-so_rcvbuf-with-64-bit-int-works

Dan Stromberg:


Pypy appears to allow an oversized tcp_window when doing a setsockopt SO_RCVBUF.  CPython, when running the same code, allows only a 2^31-1 size, while Pypy allows a 2^63-1 size.  Both runs were on a 64 bit system Linux Mint system.  The C code's type system seems to only allow a 32 bit value.

Test code demonstrating the issue in Python and C, is at http://stromberg.dnsalias.org/~strombrg/max-tcp-window.html




From issues-reply at bitbucket.org  Mon Oct  6 09:26:13 2014
From: issues-reply at bitbucket.org (Markus Ullmann)
Date: Mon, 06 Oct 2014 07:26:13 -0000
Subject: [pypy-issue] Issue #1881: build error 'no_release_gil' function can
 release the GIL on cygwin (pypy/pypy)
Message-ID: <20141006072613.32367.34793@app04.ash-private.bitbucket.org>

New issue 1881: build error 'no_release_gil' function can release the GIL on cygwin
https://bitbucket.org/pypy/pypy/issue/1881/build-error-no_release_gil-function-can

Markus Ullmann:

During build of pypy-2.4.0 on recent cygwin, I get the attached traceback.

>From issue #1603 I have learned that one of the functions does something fancy, though I'm not an expert on how to track, where exactly the issue originates.




From issues-reply at bitbucket.org  Tue Oct  7 12:09:44 2014
From: issues-reply at bitbucket.org (Cat's Eye Technologies)
Date: Tue, 07 Oct 2014 10:09:44 -0000
Subject: [pypy-issue] Issue #1882: License of files in 'py' directory is not
 specified (pypy/pypy)
Message-ID: <20141007100944.20200.40652@app04.ash-private.bitbucket.org>

New issue 1882: License of files in 'py' directory is not specified
https://bitbucket.org/pypy/pypy/issue/1882/license-of-files-in-py-directory-is-not

Cat's Eye Technologies:

The file LICENSE gives licensing information for the contents of the directories 'rpython', 'pypy', 'ctype_configure', 'dotviewer', 'demo', and 'lib_pypy', but does not mention the 'py' directory.

I do not see a LICENSE file anywhere under the 'py' directory tree.

Some of the files under 'py' (e.g. _iniconfig.py) do say "MIT licensed" in them, but many of them (e.g. _builtin.py) say nothing at all about their license terms.

If the project maintainers can confirm that the contents of the 'py' directory can be distributed under an MIT license (or can inform me of the terms under which they can be used and distributed), I can open a pull request to add that info to the main LICENSE file (but it would seem presumptuous for me to do that before knowing what their licensing terms actually are...)



From issues-reply at bitbucket.org  Wed Oct  8 21:32:59 2014
From: issues-reply at bitbucket.org (sbehnel)
Date: Wed, 08 Oct 2014 19:32:59 -0000
Subject: [pypy-issue] Issue #1883: cpyext lacks PyUnicode_InternFromString()
 in pypy3 (pypy/pypy)
Message-ID: <20141008193259.1019.7083@app07.ash-private.bitbucket.org>

New issue 1883: cpyext lacks PyUnicode_InternFromString() in pypy3
https://bitbucket.org/pypy/pypy/issue/1883/cpyext-lacks-pyunicode_internfromstring-in

sbehnel:

see subject



From issues-reply at bitbucket.org  Wed Oct  8 21:36:38 2014
From: issues-reply at bitbucket.org (sbehnel)
Date: Wed, 08 Oct 2014 19:36:38 -0000
Subject: [pypy-issue] Issue #1884: cpyext defines several legacy names in
	pypy3 (pypy/pypy)
Message-ID: <20141008193638.26836.55417@app02.ash-private.bitbucket.org>

New issue 1884: cpyext defines several legacy names in pypy3
https://bitbucket.org/pypy/pypy/issue/1884/cpyext-defines-several-legacy-names-in

sbehnel:

These need to be removed from the header files:

PyString*
PyInt*
PyNumber_Int
PyBoolObject




From issues-reply at bitbucket.org  Sun Oct 12 14:14:53 2014
From: issues-reply at bitbucket.org (Ned Batchelder)
Date: Sun, 12 Oct 2014 12:14:53 -0000
Subject: [pypy-issue] Issue #1885: RPython modules no longer have __file__,
 but their functions have func_code.co_filename (pypy/pypy)
Message-ID: <20141012121453.23699.70921@app12.ash-private.bitbucket.org>

New issue 1885: RPython modules no longer have __file__, but their functions have func_code.co_filename
https://bitbucket.org/pypy/pypy/issue/1885/rpython-modules-no-longer-have-__file__

Ned Batchelder:

In PyPy 2.3, modules like _structseq had a .__file__ attribute with build-system file paths in them, like `/Users/kostia/programming/pypy/lib_pypy/_structseq.pyc`.  This was weird:
```
$ pypy2.3
Python 2.7.6 (32f35069a16d, Jun 06 2014, 20:12:47)
[PyPy 2.3.1 with GCC 4.2.1 Compatible Apple LLVM 5.0 (clang-500.2.79)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>>> import _structseq
>>>> _structseq.__file__
'/Users/kostia/programming/pypy/lib_pypy/_structseq.pyc'
```

In PyPy 2.4, that attribute is gone, but you can still find paths like that in func_code.co_filename:
```
$ pypy2.4
Python 2.7.8 (f5dcc2477b97, Sep 19 2014, 18:09:54)
[PyPy 2.4.0 with GCC 4.2.1 Compatible Apple LLVM 5.1 (clang-503.0.38)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>>> import _structseq
>>>> _structseq.structseq_new.func_code.co_filename
'/Users/kostia/programming/pypy/lib_pypy/_structseq.py'
```

This mattered to coverage.py, because it was excluding the PyPy stdlib modules based on where _structseq was from.  Without a __file__ attribute, coverage wasn't excluding the stdlib modules, and _structseq would be measured, but would then fail during reporting when coverage.py couldn't read the co_filename path to produce the report.

Coverage.py is now fixed with this: https://bitbucket.org/ned/coveragepy/commits/789cc15f04ccb46b53e96e5ffd3debbfbc1defaa , but Alex asked that I write a bug, and I do what Alex asks me to! :)



From issues-reply at bitbucket.org  Sun Oct 12 18:01:32 2014
From: issues-reply at bitbucket.org (mario_)
Date: Sun, 12 Oct 2014 16:01:32 -0000
Subject: [pypy-issue] Issue #1886: PyPy doesn't do basic loop-invariant
 optimizations (pypy/pypy)
Message-ID: <20141012160132.7161.57577@app03.ash-private.bitbucket.org>

New issue 1886: PyPy doesn't do basic loop-invariant optimizations
https://bitbucket.org/pypy/pypy/issue/1886/pypy-doesnt-do-basic-loop-invariant

mario_:

This code can be sped up about 25% by realizing that a[i] is constant in the inner loop.
I know threading potentially invalidates such optimizations but there are some options to work around that.

n = 10**4
a = [list(range(n))]*n

s = 0
for i in range(n):
  #ai = a[i]
  for j in range(n):
    s += a[i][j]

print(s)



From issues-reply at bitbucket.org  Mon Oct 13 00:04:53 2014
From: issues-reply at bitbucket.org (eric s)
Date: Sun, 12 Oct 2014 22:04:53 -0000
Subject: [pypy-issue] Issue #1887: Regression in 2.4.0, streamio. (pypy/pypy)
Message-ID: <20141012220453.30158.38413@app14.ash-private.bitbucket.org>

New issue 1887: Regression in 2.4.0, streamio.
https://bitbucket.org/pypy/pypy/issue/1887/regression-in-240-streamio

eric s:

In Pillow, when dealing with multipage tiffs using libtiff, we have some code that is essentially:

```
#!python
fd = open(file)
stuff = fd.read()
libtiff_fd = os.dup(fd.fileno())
""" lib tiff does stuff with the file descriptor, then closes it"""

fd.tell()  # resyncs the file descriptor in py3, essentially a noop in py2
fd.seek(next_frame)  #  seek to the next frame to read metadata
stuff = fd.read()
```

The test that's failing is here: https://github.com/python-pillow/Pillow/blob/9634e437efeeda906ad6bfcc275b17732d64f32a/Tests/test_file_libtiff.py#L315

This worked in Pypy 2.3, Pypy2.4 fails at both the tell and the seek with an assertion error. 
Tell:
```
RPython traceback:
  File "implement_7.c", line 12162, in W_File_file_tell
  File "rpython_rlib_streamio.c", line 6936, in BufferingInputStream_tell
Fatal RPython error: AssertionError
```
Seek:
```
RPython traceback:
  File "implement_7.c", line 10766, in W_File_file_seek
  File "rpython_rlib_streamio.c", line 5743, in BufferingInputStream_seek
Fatal RPython error: AssertionError
```




From issues-reply at bitbucket.org  Mon Oct 13 15:46:13 2014
From: issues-reply at bitbucket.org (agriff)
Date: Mon, 13 Oct 2014 13:46:13 -0000
Subject: [pypy-issue] Issue #1888: Error parsing string literal with binary
	data (pypy/pypy)
Message-ID: <20141013134613.19410.22097@app12.ash-private.bitbucket.org>

New issue 1888: Error parsing string literal with binary data
https://bitbucket.org/pypy/pypy/issue/1888/error-parsing-string-literal-with-binary

agriff:

The attached program comes from code golfing and uses a string literal with binary data to pass to zlib.decompress (a trick to reduce "source code" size).

It works with standard Python 2.7, but fails with a syntax error on pypy



From issues-reply at bitbucket.org  Tue Oct 14 23:00:27 2014
From: issues-reply at bitbucket.org (Anthony Sottile)
Date: Tue, 14 Oct 2014 21:00:27 -0000
Subject: [pypy-issue] Issue #1889: AttributeError importing module
	(pypy/pypy)
Message-ID: <20141014210027.15399.37439@app03.ash-private.bitbucket.org>

New issue 1889: AttributeError importing module
https://bitbucket.org/pypy/pypy/issue/1889/attributeerror-importing-module

Anthony Sottile:

```
$ virtualenv venv -p pypy3
Running virtualenv with interpreter /home/asottile/bin/pypy3
New pypy executable in venv/bin/pypy3
Also creating executable in venv/bin/pypy
Installing setuptools, pip...done.
$ source venv/bin/activate
(venv)$ pip install jsonschema
Downloading/unpacking jsonschema
  Using download cache from /home/asottile/.pip/cache/https%3A%2F%2Fpypi.python.org%2Fpackages%2F2.7%2Fj%2Fjsonschema%2Fjsonschema-2.4.0-py2.py3-none-any.whl
Installing collected packages: jsonschema
Successfully installed jsonschema
Cleaning up...
(venv)asottile at work:~/workspace/pre-commit$ pypy -c 'import jsonschema'
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/asottile/workspace/pre-commit/venv/site-packages/jsonschema/__init__.py", line 18, in <module>
    from jsonschema.validators import (
  File "/home/asottile/workspace/pre-commit/venv/site-packages/jsonschema/validators.py", line 157, in <module>
    meta_schema=_utils.load_schema("draft3"),
  File "/home/asottile/workspace/pre-commit/venv/site-packages/jsonschema/_utils.py", line 57, in load_schema
    data = pkgutil.get_data(__package__, "schemas/{0}.json".format(name))
  File "/home/asottile/packages/pypy3-2.3.1-linux64/lib-python/3/pkgutil.py", line 573, in get_data
    loader = get_loader(package)
  File "/home/asottile/packages/pypy3-2.3.1-linux64/lib-python/3/pkgutil.py", line 461, in get_loader
    return find_loader(fullname)
  File "/home/asottile/packages/pypy3-2.3.1-linux64/lib-python/3/pkgutil.py", line 471, in find_loader
    for importer in iter_importers(fullname):
  File "/home/asottile/packages/pypy3-2.3.1-linux64/lib-python/3/pkgutil.py", line 421, in iter_importers
    if fullname.startswith('.'):
AttributeError: 'NoneType' object has no attribute 'startswith'
(venv)$ pypy --version
Python 3.2.5 (986752d005bb, Jun 19 2014, 16:18:53)
[PyPy 2.3.1 with GCC 4.6.3]
(venv)$ pip freeze -l
jsonschema==2.4.0
(venv)$ pip freeze
cffi==0.8
greenlet==0.4.0
jsonschema==2.4.0
readline==6.2.4.1
wsgiref==0.1.2
```



From issues-reply at bitbucket.org  Wed Oct 15 00:15:05 2014
From: issues-reply at bitbucket.org (halgari)
Date: Tue, 14 Oct 2014 22:15:05 -0000
Subject: [pypy-issue] Issue #1890: Translation fails on OSX now. (pypy/pypy)
Message-ID: <20141014221505.5484.26969@app02.ash-private.bitbucket.org>

New issue 1890: Translation fails on OSX now.
https://bitbucket.org/pypy/pypy/issue/1890/translation-fails-on-osx-now

halgari:

The change made to posix.py in this commit: https://bitbucket.org/pypy/pypy/diff/rpython/translator/platform/posix.py?diff2=2ae639f5628f&at=default

Causes the following error on OSX:



```
#!bash

clang -arch x86_64 -mmacosx-version-min=10.5 main.o -L. -ltarget-c -o target-c -Wl,-rpath="RIGIN/"
ld: unknown option: -rpath=RIGIN/
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [target-c] Error 1
```

Responsible: arigo

From issues-reply at bitbucket.org  Wed Oct 15 10:08:33 2014
From: issues-reply at bitbucket.org (Campbell Barton)
Date: Wed, 15 Oct 2014 08:08:33 -0000
Subject: [pypy-issue] Issue #1891: pypy3: ``struct.Struct('i').format``
 should be bytes, not string (pypy/pypy)
Message-ID: <20141015080833.32535.43027@app09.ash-private.bitbucket.org>

New issue 1891: pypy3: ``struct.Struct('i').format`` should be bytes, not string
https://bitbucket.org/pypy/pypy/issue/1891/pypy3-structstruct-i-format-should-be

Campbell Barton:

In CPython 3.4x:

    >>> import struct
    >>> struct.Struct('i').format
    b'i'

In Pypy3 Python 3.2.5 (986752d005bb6c65ce418113e4c3cd115f61a9b4, Jul 08 2014, 12:36:44)

    >>>> import struct
    >>>> struct.Struct('i').format
    'i'

This caused one of my scripts to fail running in pypy3.



From issues-reply at bitbucket.org  Thu Oct 16 10:14:31 2014
From: issues-reply at bitbucket.org (bitranox bitranox)
Date: Thu, 16 Oct 2014 08:14:31 -0000
Subject: [pypy-issue] Issue #1892: rpyc ThreadedServer vs ForkingServer -
 different behaviour on pypy3 V2.3.1 and python3.4.1 (pypy/pypy)
Message-ID: <20141016081431.30869.70540@app06.ash-private.bitbucket.org>

New issue 1892: rpyc ThreadedServer vs ForkingServer - different behaviour on pypy3 V2.3.1 and python3.4.1
https://bitbucket.org/pypy/pypy/issue/1892/rpyc-threadedserver-vs-forkingserver

bitranox bitranox:

ThreadedServer vs ForkingServer - different behaviour on pypy3 V2.3.1 and python3.4.1

I use rpyc 3.3 on Linux Mint Mate, either with python3 (Version 3.4.1) or pypy3 (Version 2.3.1)

on python3 - ThreadedServer and ForkingServer working as expected so far.
on pypy3 - ThreadedServer Works, But ForkingServer terminates when a client is closing the connection

rpyc team answer was : 
well, it's clearly a pypy bug. i'd suggest you added prints() around the server's code (rpyc/utils/server.py) to see what's going on there. perhaps it's an issue with signals, or what not. donno.




From issues-reply at bitbucket.org  Thu Oct 16 19:21:30 2014
From: issues-reply at bitbucket.org (mattip)
Date: Thu, 16 Oct 2014 17:21:30 -0000
Subject: [pypy-issue] Issue #1893: numpypy's iterator is slower than pypy's
	(pypy/pypy)
Message-ID: <20141016172130.19645.36972@app09.ash-private.bitbucket.org>

New issue 1893: numpypy's iterator is slower than pypy's
https://bitbucket.org/pypy/pypy/issue/1893/numpypys-iterator-is-slower-than-pypys

mattip:

This test compares three ways to iterate over numpy ndarrays: a pure python loop, an implicit numpy loop, and an nditer.
numpypy's iterator is ~2x slower than a pure python loop
The nditer's performance is ~100 times worse than a pure python loop:

    $pypy test.py  
    add10_numpy: 0.0288829803467
    True
    add10_nditer: 0.963934183121
    True
    add10_py: 0.013454914093
    True




From issues-reply at bitbucket.org  Thu Oct 16 22:24:45 2014
From: issues-reply at bitbucket.org (Anthony Sottile)
Date: Thu, 16 Oct 2014 20:24:45 -0000
Subject: [pypy-issue] Issue #1894: KeyError (core dumped) on unicode triple
 quoted double quote literal (pypy/pypy)
Message-ID: <20141016202445.20058.78238@app14.ash-private.bitbucket.org>

New issue 1894: KeyError (core dumped) on unicode triple quoted double quote literal
https://bitbucket.org/pypy/pypy/issue/1894/keyerror-core-dumped-on-unicode-triple

Anthony Sottile:

```
$ pypy3 -m compileall test.py
Compiling 'test.py'...
RPython traceback:
  File "pypy_goal_targetpypystandalone.c", line 2059, in entry_point
  File "pypy_interpreter_pyframe.c", line 3779, in PyFrame_execute_frame
  File "rpython_jit_metainterp_warmspot.c", line 1487, in ll_portal_runner__Unsigned_Bool_pypy_interpreter
  File "pypy_module_pypyjit_interp_jit.c", line 289, in portal_4
  File "pypy_interpreter_pyopcode.c", line 6902, in handle_bytecode__AccessDirect_None
  File "pypy_interpreter_pyopcode.c", line 9984, in dispatch_bytecode__AccessDirect_None
  File "pypy_interpreter_pyopcode.c", line 17466, in call_function__AccessDirect_None
  File "pypy_interpreter_pyframe.c", line 3779, in PyFrame_execute_frame
  File "rpython_jit_metainterp_warmspot.c", line 1487, in ll_portal_runner__Unsigned_Bool_pypy_interpreter
  File "pypy_module_pypyjit_interp_jit.c", line 289, in portal_4
  File "pypy_interpreter_pyopcode.c", line 6902, in handle_bytecode__AccessDirect_None
  ...
Fatal RPython error: KeyError
Aborted (core dumped)
$ cat test.py
u""""""
$ pypy3 --version
Python 3.2.5 (986752d005bb, Jun 19 2014, 16:18:53)
[PyPy 2.3.1 with GCC 4.6.3]
```

Interestingly the following files are fine:
```
u''''''
```

```
u""
```

```
u''
```




From issues-reply at bitbucket.org  Fri Oct 17 01:14:33 2014
From: issues-reply at bitbucket.org (Ionel Maries Cristian)
Date: Thu, 16 Oct 2014 23:14:33 -0000
Subject: [pypy-issue] Issue #1895: Writing to stderr from multiple threads
 produces deadlock (pypy/pypy)
Message-ID: <20141016231433.14668.71215@app06.ash-private.bitbucket.org>

New issue 1895: Writing to stderr from multiple threads produces deadlock
https://bitbucket.org/pypy/pypy/issue/1895/writing-to-stderr-from-multiple-threads

Ionel Maries Cristian:

Minimal testcase:
```
import os
import sys
import threading


class Thread(threading.Thread):
    def run(self):
        print >> sys.stderr, "BLAM!"

t = Thread()
t.daemon = True
t.start()

pid = os.fork()
if pid:
    print('waiting for process', pid)
    os.waitpid(pid, 0)
else:
    print >> sys.stderr, "BOOM!"
    os.execvp('true', ['true'])
print('process ended')
```

To run: `while pypy deadlock.py; do true; done`

Reproduces on PyPy 2.3.0 and 2.4.0



From issues-reply at bitbucket.org  Sat Oct 18 19:47:30 2014
From: issues-reply at bitbucket.org (Campbell Barton)
Date: Sat, 18 Oct 2014 17:47:30 -0000
Subject: [pypy-issue] Issue #1896: pkg-config Needed to Build pypy,
 no useful error given (pypy/pypy)
Message-ID: <20141018174730.14901.73118@app05.ash-private.bitbucket.org>

New issue 1896: pkg-config Needed to Build pypy, no useful error given
https://bitbucket.org/pypy/pypy/issue/1896/pkg-config-needed-to-build-pypy-no-useful

Campbell Barton:

Running `python2 rpython/bin/rpython --opt=jit pypy/goal/targetpypystandalone.py`

Just gives a message that `libffi.h` is missing, through investigation I found that this happens because pkg-config wasn't included on my system.

This should really give an error such as **pkg-config command not found**



From issues-reply at bitbucket.org  Mon Oct 20 06:14:40 2014
From: issues-reply at bitbucket.org (Xavier de Rauville)
Date: Mon, 20 Oct 2014 04:14:40 -0000
Subject: [pypy-issue] Issue #1897: Regression in 2.3 that causes Pypy.exe to
 crash when PyFFI is run (pypy/pypy)
Message-ID: <20141020041440.28286.82945@app12.ash-private.bitbucket.org>

New issue 1897: Regression in 2.3 that causes Pypy.exe to crash when PyFFI is run
https://bitbucket.org/pypy/pypy/issue/1897/regression-in-23-that-causes-pypyexe-to

Xavier de Rauville:

At some point between Pypy v2.2.1 and v2.3, a change was made to Pypy which is causing a program I use called PyFFI to crash when it is run. The problem is still present in Pypy v2.4
I am using Windows 8.1 if my OS is relevant to the problem.

Here are the steps to reproduce the problem:
1. Extract the contents of *PyFFI Toaster.7z* to anywhere on your PC.
2. Extract the contents of *Pypy root.7z* into the root directory of a Pypy 2.2.1 installation.
3. Open the *PyFFI Toaster* folder you extracted.
4. Edit *oblivion_optimize - pypy.bat* to point to the correct  location of **Pypy.exe** and the **Scripts** folder that you extracted.
5. Run *oblivion_optimize - pypy.bat* (if you're using Windows. If you are using a different platform, you will need to create an equivalent script for your platform). Let it run for a few seconds to make sure it works then force close or wait for the process to finish.
6. Repeat the above for a Pypy v2.3 or later installation (you may need to delete the contents of *PyFFI Toaster/Out*).

What should happen:
Your PC's CPU becomes fully loaded, a log file appears in the *PyFFI Toaster* folder with a lot of text and files get placed in the Out folder.

What happens with Pypy v2.3 - 2.4:
Pypy.exe crashes, a log file appears in the *PyFFI Toaster* folder with an error and maybe a bit more text and you may see the message box shown in **PyFFI error.png** if you're using Windows.




From issues-reply at bitbucket.org  Tue Oct 21 05:04:29 2014
From: issues-reply at bitbucket.org (halgari)
Date: Tue, 21 Oct 2014 03:04:29 -0000
Subject: [pypy-issue] Issue #1898: isinstance with unicode fails to
	translate (pypy/pypy)
Message-ID: <20141021030429.24280.31619@app02.ash-private.bitbucket.org>

New issue 1898: isinstance with unicode fails to translate
https://bitbucket.org/pypy/pypy/issue/1898/isinstance-with-unicode-fails-to-translate

halgari:

My interpreter blows up during translation with the following error: 



[translation:info]    File "/home/travis/build/pixie-lang/externals/pypy/rpython/rtyper/rbuiltin.py", line 701, in rtype_builtin_isinstance
[translation:info]     assert isinstance(hop.args_r[0], rclass.InstanceRepr)

I took a look at the code in rbuiltin.py and noticed that the function is special cased for str and list, but not unicode. So as I test I added unicode to the tuple of special cases, and the code translates correctly. So I assume this is a bug?

You can give this a try by downloading http://github.com/pixie-lang/pixie , running ./checkout-externals, and then ./make-with-jit








From issues-reply at bitbucket.org  Thu Oct 23 21:47:18 2014
From: issues-reply at bitbucket.org (mario_)
Date: Thu, 23 Oct 2014 19:47:18 -0000
Subject: [pypy-issue] Issue #1899: Regression in tkinter in PyPy3 2.4
	(pypy/pypy)
Message-ID: <20141023194718.16948.28913@app06.ash-private.bitbucket.org>

New issue 1899: Regression in tkinter in PyPy3 2.4
https://bitbucket.org/pypy/pypy/issue/1899/regression-in-tkinter-in-pypy3-24

mario_:

Pressing return causes an exception in PyPy3 2.4 but not in CPython or an older PyPy3.

```

#!python

from tkinter import *
root = Tk()
text = Text(root)
text.pack()
text.bind('<Return>', lambda event: print('hello'))
mainloop()
```




From issues-reply at bitbucket.org  Fri Oct 24 00:45:19 2014
From: issues-reply at bitbucket.org (squeaky)
Date: Thu, 23 Oct 2014 22:45:19 -0000
Subject: [pypy-issue] Issue #1900: [PyPy3] idle (tkinter),
 cannot open preferences (pypy/pypy)
Message-ID: <20141023224519.24483.96422@app08.ash-private.bitbucket.org>

New issue 1900: [PyPy3] idle (tkinter), cannot open preferences
https://bitbucket.org/pypy/pypy/issue/1900/pypy3-idle-tkinter-cannot-open-preferences

squeaky:

I tried running idle:

```
pypy3-2.4-linux_i686-portable/bin/pypy -m idlelib.idle
```

Then i navigated to Options > Configure IDLE

and saw this stacktrace instead of configuration window

```
#!python

Exception in Tkinter callback
Traceback (most recent call last):
  File "/home/squeaky/workspace/portable-pypy/pypy3-2.4-linux_i686-portable/lib-python/3/tkinter/__init__.py", line 1455, in __call__
    args = self.subst(*args)
  File "/home/squeaky/workspace/portable-pypy/pypy3-2.4-linux_i686-portable/lib-python/3/tkinter/__init__.py", line 1193, in _substitute
    try: e.focus = getboolean(f)
  File "/home/squeaky/workspace/portable-pypy/pypy3-2.4-linux_i686-portable/lib_pypy/_tkinter/app.py", line 449, in getboolean
    if '\x00' in s:
TypeError: 'str' does not support the buffer interface

```


Responsible: pjenvey

From issues-reply at bitbucket.org  Fri Oct 24 13:30:47 2014
From: issues-reply at bitbucket.org (Maciej Fijalkowski)
Date: Fri, 24 Oct 2014 11:30:47 -0000
Subject: [pypy-issue] Issue #1901: Try using a different implementation of
 mersenne twister (pypy/pypy)
Message-ID: <20141024113047.6292.73280@app08.ash-private.bitbucket.org>

New issue 1901: Try using a different implementation of mersenne twister
https://bitbucket.org/pypy/pypy/issue/1901/try-using-a-different-implementation-of

Maciej Fijalkowski:

The idea is to try using an external C library for random() to make it faster, e.g. http://www.math.sci.hiroshima-u.ac.jp/~%20m-mat/MT/SFMT/index.html



From issues-reply at bitbucket.org  Fri Oct 24 15:42:27 2014
From: issues-reply at bitbucket.org (Christoph Reiter)
Date: Fri, 24 Oct 2014 13:42:27 -0000
Subject: [pypy-issue] Issue #1902: PyPy3: "IOError: [Errno 22] Invalid
 argument" with buffered rw file IO (pypy/pypy)
Message-ID: <20141024134227.6406.39446@app07.ash-private.bitbucket.org>

New issue 1902: PyPy3: "IOError: [Errno 22] Invalid argument" with buffered rw file IO
https://bitbucket.org/pypy/pypy/issue/1902/pypy3-ioerror-errno-22-invalid-argument

Christoph Reiter:

With PyPy 2.4.0:

```
#!python

with open("foo.data", "w+b", 4096) as f:
    f.write(b"\xff" * 13569)
    f.flush()
    f.seek(0, 0)
    f.read(1)
    f.seek(-1, 1)
    f.write(b"")  # pypy3: IOError: [Errno 22] Invalid argument
```

```
#!python

with open("foo.data", "w+b", 4096) as f:
    f.write(b"\xff" * 13569)
    f.flush()
    f.seek(0, 0)

    f.read(1)
    f.seek(-1, 1)
    f.write(b"\xff")
    f.seek(1, 0)
    f.read(4123)
    f.seek(-4123, 1) # IOError: [Errno 22] Invalid argument
```




From issues-reply at bitbucket.org  Sun Oct 26 22:04:13 2014
From: issues-reply at bitbucket.org (Ned Batchelder)
Date: Sun, 26 Oct 2014 21:04:13 -0000
Subject: [pypy-issue] Issue #1903: Chained exception in pypy3 working
 differently than CPython 3.x (pypy/pypy)
Message-ID: <20141026210413.18616.34750@app02.ash-private.bitbucket.org>

New issue 1903: Chained exception in pypy3 working differently than CPython 3.x
https://bitbucket.org/pypy/pypy/issue/1903/chained-exception-in-pypy3-working

Ned Batchelder:

The coverage.py test suite fails in one test for pypy3.

PyPy3 testing was added in e303eb19c993 (https://bitbucket.org/ned/coveragepy/commits/e303eb19c993376b91ffb68da368a3482b4a608a)

To run the test suite:

```
pip install -r requirements.txt
tox
```

The failure:

```
======================================================================
FAIL: test_code_throws (tests.test_process.ProcessTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/ned/coverage/trunk/tests/test_process.py", line 274, in test_code_throws
    self.assertMultiLineEqual(out, out2)
nose.proxy.AssertionError: 'Traceback (most recent call last):\n  File "/Users/ned/coverage/trunk/coverage/ [truncated]... != 'Traceback (most recent call last):\n  File "throw.py", line 7, in <module>\n    [truncated]...
- Traceback (most recent call last):
-   File "/Users/ned/coverage/trunk/coverage/cmdline.py", line 671, in main
-     status = CoverageScript().command_line(argv)
-   File "/Users/ned/coverage/trunk/coverage/cmdline.py", line 416, in command_line
-     self.do_execute(options, args)
-   File "/Users/ned/coverage/trunk/coverage/cmdline.py", line 560, in do_execute
-     self.run_python_file(filename, args)
-   File "/Users/ned/coverage/trunk/coverage/execfile.py", line 141, in run_python_file
-     raise ExceptionDuringRun(typ, err, tb.tb_next)
- coverage.misc.ExceptionDuringRun: (<class 'Exception'>, Exception('hey!',), <traceback object at 0x0000000103ffa740>)
-
- During handling of the above exception, another exception occurred:
-
  Traceback (most recent call last):
    File "throw.py", line 7, in <module>
      f2()
    File "throw.py", line 5, in f2
      f1()
    File "throw.py", line 2, in f1
      raise Exception("hey!")
  Exception: hey!

-------------------- >> begin captured stdout << ---------------------
Traceback (most recent call last):
  File "/Users/ned/coverage/trunk/coverage/cmdline.py", line 671, in main
    status = CoverageScript().command_line(argv)
  File "/Users/ned/coverage/trunk/coverage/cmdline.py", line 416, in command_line
    self.do_execute(options, args)
  File "/Users/ned/coverage/trunk/coverage/cmdline.py", line 560, in do_execute
    self.run_python_file(filename, args)
  File "/Users/ned/coverage/trunk/coverage/execfile.py", line 141, in run_python_file
    raise ExceptionDuringRun(typ, err, tb.tb_next)
coverage.misc.ExceptionDuringRun: (<class 'Exception'>, Exception('hey!',), <traceback object at 0x0000000103ffa740>)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "throw.py", line 7, in <module>
    f2()
  File "throw.py", line 5, in f2
    f1()
  File "throw.py", line 2, in f1
    raise Exception("hey!")
Exception: hey!

Traceback (most recent call last):
  File "throw.py", line 7, in <module>
    f2()
  File "throw.py", line 5, in f2
    f1()
  File "throw.py", line 2, in f1
    raise Exception("hey!")
Exception: hey!


--------------------- >> end captured stdout << ----------------------
```

This test checks that running a program under coverage produces the same output as running it not under coverage. The program raises an exception.  Under pypy3, it gets this output:
```
Traceback (most recent call last):
  File "throw.py", line 7, in <module>
    f2()
  File "throw.py", line 5, in f2
    f1()
  File "throw.py", line 2, in f1
    raise Exception("hey!")
Exception: hey!
```

Under coverage, it gets this:
```
Traceback (most recent call last):
  File "/Users/ned/coverage/trunk/coverage/cmdline.py", line 671, in main
    status = CoverageScript().command_line(argv)
  File "/Users/ned/coverage/trunk/coverage/cmdline.py", line 416, in command_line
    self.do_execute(options, args)
  File "/Users/ned/coverage/trunk/coverage/cmdline.py", line 560, in do_execute
    self.run_python_file(filename, args)
  File "/Users/ned/coverage/trunk/coverage/execfile.py", line 141, in run_python_file
    raise ExceptionDuringRun(typ, err, tb.tb_next)
coverage.misc.ExceptionDuringRun: (<class 'Exception'>, Exception('hey!',), <traceback object at 0x0000000103ffa740>)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "throw.py", line 7, in <module>
    f2()
  File "throw.py", line 5, in f2
    f1()
  File "throw.py", line 2, in f1
    raise Exception("hey!")
Exception: hey!
```

This test passes on CPython 2.6, 2.7, 3.2, 3.3, 3.4, and on PyPy2



From issues-reply at bitbucket.org  Mon Oct 27 03:22:57 2014
From: issues-reply at bitbucket.org (Yichao Yu)
Date: Mon, 27 Oct 2014 02:22:57 -0000
Subject: [pypy-issue] Issue #1904: py3k branch compile_c failure on x86_64
 and i686 linux. (pypy/pypy)
Message-ID: <20141027022257.10167.99049@app11.ash-private.bitbucket.org>

New issue 1904: py3k branch compile_c failure on x86_64 and i686 linux.
https://bitbucket.org/pypy/pypy/issue/1904/py3k-branch-compile_c-failure-on-x86_64

Yichao Yu:

I've just got the following error (end of this report) when compiling the py3k branch on linux (the error is at the very end, about undeclared functions), both for i686 and x86_64. I am compiling with `--shared` and you can find the build script [here](https://github.com/archlinuxcn/repo/blob/master/pypy3-hg/PKGBUILD) and make is run with `-j7 -l8`.

I grep'ed in the `testing_1` directory and it seems that the definition of those functions are indeed not in any header files.
```
% grep -R pypy_wchar2char
pypy_module__codecs_locale.c:   l_v571613 = pypy_wchar2char(l_v571639, l_v571610);
pypy_module__codecs_locale.c:   pypy_asm_gc_nocollect(pypy_wchar2char);
pypy_module__codecs_locale.c:   pypy_wchar2char_free(l_v571613);
pypy_module__codecs_locale.c:   pypy_asm_gc_nocollect(pypy_wchar2char_free);
pypy_module__codecs_locale.c:   pypy_wchar2char_free(l_v571613);
pypy_module__codecs_locale.c:   pypy_asm_gc_nocollect(pypy_wchar2char_free);
make.errors:data_rpython_jit_metainterp_pyjitpl.c:4463:2: error: 'pypy_wchar2char' undeclared here (not in a function)
make.errors:  pypy_wchar2char, /* 184 */
make.errors:data_rpython_jit_metainterp_pyjitpl.c:4464:2: error: 'pypy_wchar2char_free' undeclared here (not in a function)
make.errors:  pypy_wchar2char_free, /* 185 */
locale.c:pypy_wchar2char(const wchar_t *text, size_t *error_pos)
locale.c:pypy_wchar2char_free(char *bytes)
data_rpython_jit_metainterp_pyjitpl.c:  pypy_wchar2char,        /* 184 */
data_rpython_jit_metainterp_pyjitpl.c:  pypy_wchar2char_free,   /* 185 */
nonfuncnodes_17.c:      ((Signed)pypy_wchar2char),      /* 2 */
nonfuncnodes_17.c:      ((Signed)pypy_wchar2char_free), /* 5 */
nonfuncnodes_17.c:      ((Signed)pypy_wchar2char_free), /* 7 */
```


content of `make.errors`

```
data_pypy_module_cpyext_pyobject.c:133:3: warning: initialization from incompatible pointer type
   (&_PyExc_EOFError), /* 5.value */
   ^
data_pypy_module_cpyext_pyobject.c:133:3: warning: (near initialization for 'pypy_g_array_718.a.items[5].d_value')
data_pypy_module_cpyext_pyobject.c:253:3: warning: initialization from incompatible pointer type
   (&_PyExc_SystemExit), /* 29.value */
   ^
data_pypy_module_cpyext_pyobject.c:253:3: warning: (near initialization for 'pypy_g_array_718.a.items[29].d_value')
data_pypy_module_cpyext_pyobject.c:263:3: warning: initialization from incompatible pointer type
   (&_PyExc_ValueError), /* 31.value */
   ^
data_pypy_module_cpyext_pyobject.c:263:3: warning: (near initialization for 'pypy_g_array_718.a.items[31].d_value')
data_pypy_module_cpyext_pyobject.c:313:3: warning: initialization from incompatible pointer type
   (&PyUnicode_Type), /* 41.value */
   ^
data_pypy_module_cpyext_pyobject.c:313:3: warning: (near initialization for 'pypy_g_array_718.a.items[41].d_value')
data_pypy_module_cpyext_pyobject.c:348:3: warning: initialization from incompatible pointer type
   (&_PyExc_ImportError), /* 48.value */
   ^
data_pypy_module_cpyext_pyobject.c:348:3: warning: (near initialization for 'pypy_g_array_718.a.items[48].d_value')
data_pypy_module_cpyext_pyobject.c:408:3: warning: initialization from incompatible pointer type
   (&_PyExc_TypeError), /* 60.value */
   ^
data_pypy_module_cpyext_pyobject.c:408:3: warning: (near initialization for 'pypy_g_array_718.a.items[60].d_value')
data_pypy_module_cpyext_pyobject.c:418:3: warning: initialization from incompatible pointer type
   (&_PyExc_ReferenceError), /* 62.value */
   ^
data_pypy_module_cpyext_pyobject.c:418:3: warning: (near initialization for 'pypy_g_array_718.a.items[62].d_value')
data_pypy_module_cpyext_pyobject.c:428:3: warning: initialization from incompatible pointer type
   (&PyModule_Type), /* 64.value */
   ^
data_pypy_module_cpyext_pyobject.c:428:3: warning: (near initialization for 'pypy_g_array_718.a.items[64].d_value')
data_pypy_module_cpyext_pyobject.c:503:3: warning: initialization from incompatible pointer type
   (&_PyExc_UnicodeError), /* 79.value */
   ^
data_pypy_module_cpyext_pyobject.c:503:3: warning: (near initialization for 'pypy_g_array_718.a.items[79].d_value')
data_pypy_module_cpyext_pyobject.c:598:3: warning: initialization from incompatible pointer type
   (&_PyExc_BaseException), /* 98.value */
   ^
data_pypy_module_cpyext_pyobject.c:598:3: warning: (near initialization for 'pypy_g_array_718.a.items[98].d_value')
data_pypy_module_cpyext_pyobject.c:613:3: warning: initialization from incompatible pointer type
   (&PyProperty_Type), /* 101.value */
   ^
data_pypy_module_cpyext_pyobject.c:613:3: warning: (near initialization for 'pypy_g_array_718.a.items[101].d_value')
data_pypy_module_cpyext_pyobject.c:648:3: warning: initialization from incompatible pointer type
   (&PyType_Type), /* 108.value */
   ^
data_pypy_module_cpyext_pyobject.c:648:3: warning: (near initialization for 'pypy_g_array_718.a.items[108].d_value')
data_pypy_module_cpyext_pyobject.c:713:3: warning: initialization from incompatible pointer type
   (&PyStaticMethod_Type), /* 121.value */
   ^
data_pypy_module_cpyext_pyobject.c:713:3: warning: (near initialization for 'pypy_g_array_718.a.items[121].d_value')
data_pypy_module_cpyext_pyobject.c:738:3: warning: initialization from incompatible pointer type
   (&_PyExc_OverflowError), /* 126.value */
   ^
data_pypy_module_cpyext_pyobject.c:738:3: warning: (near initialization for 'pypy_g_array_718.a.items[126].d_value')
data_pypy_module_cpyext_pyobject.c:778:3: warning: initialization from incompatible pointer type
   (&PyMemoryView_Type), /* 134.value */
   ^
data_pypy_module_cpyext_pyobject.c:778:3: warning: (near initialization for 'pypy_g_array_718.a.items[134].d_value')
data_pypy_module_cpyext_pyobject.c:783:3: warning: initialization from incompatible pointer type
   (&_PyExc_AssertionError), /* 135.value */
   ^
data_pypy_module_cpyext_pyobject.c:783:3: warning: (near initialization for 'pypy_g_array_718.a.items[135].d_value')
data_pypy_module_cpyext_pyobject.c:853:3: warning: initialization from incompatible pointer type
   (&PyDict_Type), /* 149.value */
   ^
data_pypy_module_cpyext_pyobject.c:853:3: warning: (near initialization for 'pypy_g_array_718.a.items[149].d_value')
data_pypy_module_cpyext_pyobject.c:918:3: warning: initialization from incompatible pointer type
   (&_PyExc_UnicodeWarning), /* 162.value */
   ^
data_pypy_module_cpyext_pyobject.c:918:3: warning: (near initialization for 'pypy_g_array_718.a.items[162].d_value')
data_pypy_module_cpyext_pyobject.c:988:3: warning: initialization from incompatible pointer type
   (&_PyExc_FloatingPointError), /* 176.value */
   ^
data_pypy_module_cpyext_pyobject.c:988:3: warning: (near initialization for 'pypy_g_array_718.a.items[176].d_value')
data_pypy_module_cpyext_pyobject.c:1008:3: warning: initialization from incompatible pointer type
   (&_PyExc_PendingDeprecationWarning), /* 180.value */
   ^
data_pypy_module_cpyext_pyobject.c:1008:3: warning: (near initialization for 'pypy_g_array_718.a.items[180].d_value')
data_pypy_module_cpyext_pyobject.c:1038:3: warning: initialization from incompatible pointer type
   (&_PyExc_NotImplementedError), /* 186.value */
   ^
data_pypy_module_cpyext_pyobject.c:1038:3: warning: (near initialization for 'pypy_g_array_718.a.items[186].d_value')
data_pypy_module_cpyext_pyobject.c:1058:3: warning: initialization from incompatible pointer type
   (&_PyExc_Exception), /* 190.value */
   ^
data_pypy_module_cpyext_pyobject.c:1058:3: warning: (near initialization for 'pypy_g_array_718.a.items[190].d_value')
data_pypy_module_cpyext_pyobject.c:1063:3: warning: initialization from incompatible pointer type
   (&_PyExc_RuntimeWarning), /* 191.value */
   ^
data_pypy_module_cpyext_pyobject.c:1063:3: warning: (near initialization for 'pypy_g_array_718.a.items[191].d_value')
data_pypy_module_cpyext_pyobject.c:1088:3: warning: initialization from incompatible pointer type
   (&_PyExc_KeyError), /* 196.value */
   ^
data_pypy_module_cpyext_pyobject.c:1088:3: warning: (near initialization for 'pypy_g_array_718.a.items[196].d_value')
data_pypy_module_cpyext_pyobject.c:1098:3: warning: initialization from incompatible pointer type
   (&PySlice_Type), /* 198.value */
   ^
data_pypy_module_cpyext_pyobject.c:1098:3: warning: (near initialization for 'pypy_g_array_718.a.items[198].d_value')
data_pypy_module_cpyext_pyobject.c:1113:3: warning: initialization from incompatible pointer type
   (&pypy_g_PyTypeObject), /* 201.value */
   ^
data_pypy_module_cpyext_pyobject.c:1113:3: warning: (near initialization for 'pypy_g_array_718.a.items[201].d_value')
data_pypy_module_cpyext_pyobject.c:1143:3: warning: initialization from incompatible pointer type
   (&_PyExc_SystemError), /* 207.value */
   ^
data_pypy_module_cpyext_pyobject.c:1143:3: warning: (near initialization for 'pypy_g_array_718.a.items[207].d_value')
data_pypy_module_cpyext_pyobject.c:1148:3: warning: initialization from incompatible pointer type
   (&PyTuple_Type), /* 208.value */
   ^
data_pypy_module_cpyext_pyobject.c:1148:3: warning: (near initialization for 'pypy_g_array_718.a.items[208].d_value')
data_pypy_module_cpyext_pyobject.c:1163:3: warning: initialization from incompatible pointer type
   (&_PyExc_AttributeError), /* 211.value */
   ^
data_pypy_module_cpyext_pyobject.c:1163:3: warning: (near initialization for 'pypy_g_array_718.a.items[211].d_value')
data_pypy_module_cpyext_pyobject.c:1213:3: warning: initialization from incompatible pointer type
   (&_PyExc_KeyboardInterrupt), /* 221.value */
   ^
data_pypy_module_cpyext_pyobject.c:1213:3: warning: (near initialization for 'pypy_g_array_718.a.items[221].d_value')
data_pypy_module_cpyext_pyobject.c:1248:3: warning: initialization from incompatible pointer type
   (&_PyExc_GeneratorExit), /* 228.value */
   ^
data_pypy_module_cpyext_pyobject.c:1248:3: warning: (near initialization for 'pypy_g_array_718.a.items[228].d_value')
data_pypy_module_cpyext_pyobject.c:1283:3: warning: initialization from incompatible pointer type
   (&PyList_Type), /* 235.value */
   ^
data_pypy_module_cpyext_pyobject.c:1283:3: warning: (near initialization for 'pypy_g_array_718.a.items[235].d_value')
data_pypy_module_cpyext_pyobject.c:1313:3: warning: initialization from incompatible pointer type
   (&_PyExc_ResourceWarning), /* 241.value */
   ^
data_pypy_module_cpyext_pyobject.c:1313:3: warning: (near initialization for 'pypy_g_array_718.a.items[241].d_value')
data_pypy_module_cpyext_pyobject.c:1323:3: warning: initialization from incompatible pointer type
   (&_PyExc_IndexError), /* 243.value */
   ^
data_pypy_module_cpyext_pyobject.c:1323:3: warning: (near initialization for 'pypy_g_array_718.a.items[243].d_value')
data_pypy_module_cpyext_pyobject.c:1328:3: warning: initialization from incompatible pointer type
   (&_PyExc_Warning), /* 244.value */
   ^
data_pypy_module_cpyext_pyobject.c:1328:3: warning: (near initialization for 'pypy_g_array_718.a.items[244].d_value')
data_pypy_module_cpyext_pyobject.c:1458:3: warning: initialization from incompatible pointer type
   (&_PyExc_RuntimeError), /* 270.value */
   ^
data_pypy_module_cpyext_pyobject.c:1458:3: warning: (near initialization for 'pypy_g_array_718.a.items[270].d_value')
data_pypy_module_cpyext_pyobject.c:1468:3: warning: initialization from incompatible pointer type
   (&_PyExc_StopIteration), /* 272.value */
   ^
data_pypy_module_cpyext_pyobject.c:1468:3: warning: (near initialization for 'pypy_g_array_718.a.items[272].d_value')
data_pypy_module_cpyext_pyobject.c:1493:3: warning: initialization from incompatible pointer type
   (&PyByteArray_Type), /* 277.value */
   ^
data_pypy_module_cpyext_pyobject.c:1493:3: warning: (near initialization for 'pypy_g_array_718.a.items[277].d_value')
data_pypy_module_cpyext_pyobject.c:1553:3: warning: initialization from incompatible pointer type
   (&PyInstanceMethod_Type), /* 289.value */
   ^
data_pypy_module_cpyext_pyobject.c:1553:3: warning: (near initialization for 'pypy_g_array_718.a.items[289].d_value')
data_pypy_module_cpyext_pyobject.c:1573:3: warning: initialization from incompatible pointer type
   (&PyFloat_Type), /* 293.value */
   ^
data_pypy_module_cpyext_pyobject.c:1573:3: warning: (near initialization for 'pypy_g_array_718.a.items[293].d_value')
data_pypy_module_cpyext_pyobject.c:1583:3: warning: initialization from incompatible pointer type
   (&_PyExc_IndentationError), /* 295.value */
   ^
data_pypy_module_cpyext_pyobject.c:1583:3: warning: (near initialization for 'pypy_g_array_718.a.items[295].d_value')
data_pypy_module_cpyext_pyobject.c:1608:3: warning: initialization from incompatible pointer type
   (&_PyExc_UnboundLocalError), /* 300.value */
   ^
data_pypy_module_cpyext_pyobject.c:1608:3: warning: (near initialization for 'pypy_g_array_718.a.items[300].d_value')
data_pypy_module_cpyext_pyobject.c:1618:3: warning: initialization from incompatible pointer type
   (&_PyExc_UnicodeDecodeError), /* 302.value */
   ^
data_pypy_module_cpyext_pyobject.c:1618:3: warning: (near initialization for 'pypy_g_array_718.a.items[302].d_value')
data_pypy_module_cpyext_pyobject.c:1653:3: warning: initialization from incompatible pointer type
   (&PyWrapperDescr_Type), /* 309.value */
   ^
data_pypy_module_cpyext_pyobject.c:1653:3: warning: (near initialization for 'pypy_g_array_718.a.items[309].d_value')
data_pypy_module_cpyext_pyobject.c:1668:3: warning: initialization from incompatible pointer type
   (&PyBaseObject_Type), /* 312.value */
   ^
data_pypy_module_cpyext_pyobject.c:1668:3: warning: (near initialization for 'pypy_g_array_718.a.items[312].d_value')
data_pypy_module_cpyext_pyobject.c:1718:3: warning: initialization from incompatible pointer type
   (&PyArray_Type), /* 322.value */
   ^
data_pypy_module_cpyext_pyobject.c:1718:3: warning: (near initialization for 'pypy_g_array_718.a.items[322].d_value')
data_pypy_module_cpyext_pyobject.c:1728:3: warning: initialization from incompatible pointer type
   (&PyCell_Type), /* 324.value */
   ^
data_pypy_module_cpyext_pyobject.c:1728:3: warning: (near initialization for 'pypy_g_array_718.a.items[324].d_value')
data_pypy_module_cpyext_pyobject.c:1738:3: warning: initialization from incompatible pointer type
   (&_PyExc_NameError), /* 326.value */
   ^
data_pypy_module_cpyext_pyobject.c:1738:3: warning: (near initialization for 'pypy_g_array_718.a.items[326].d_value')
data_pypy_module_cpyext_pyobject.c:1823:3: warning: initialization from incompatible pointer type
   (&_PyExc_ArithmeticError), /* 343.value */
   ^
data_pypy_module_cpyext_pyobject.c:1823:3: warning: (near initialization for 'pypy_g_array_718.a.items[343].d_value')
data_pypy_module_cpyext_pyobject.c:1828:3: warning: initialization from incompatible pointer type
   (&_PyExc_EnvironmentError), /* 344.value */
   ^
data_pypy_module_cpyext_pyobject.c:1828:3: warning: (near initialization for 'pypy_g_array_718.a.items[344].d_value')
data_pypy_module_cpyext_pyobject.c:1893:3: warning: initialization from incompatible pointer type
   (&_PyExc_UserWarning), /* 357.value */
   ^
data_pypy_module_cpyext_pyobject.c:1893:3: warning: (near initialization for 'pypy_g_array_718.a.items[357].d_value')
data_pypy_module_cpyext_pyobject.c:1968:3: warning: initialization from incompatible pointer type
   (&_PyExc_FutureWarning), /* 372.value */
   ^
data_pypy_module_cpyext_pyobject.c:1968:3: warning: (near initialization for 'pypy_g_array_718.a.items[372].d_value')
data_pypy_module_cpyext_pyobject.c:1973:3: warning: initialization from incompatible pointer type
   (&PyFrozenSet_Type), /* 373.value */
   ^
data_pypy_module_cpyext_pyobject.c:1973:3: warning: (near initialization for 'pypy_g_array_718.a.items[373].d_value')
data_pypy_module_cpyext_pyobject.c:2003:3: warning: initialization from incompatible pointer type
   (&_PyExc_IOError), /* 379.value */
   ^
data_pypy_module_cpyext_pyobject.c:2003:3: warning: (near initialization for 'pypy_g_array_718.a.items[379].d_value')
data_pypy_module_cpyext_pyobject.c:2043:3: warning: initialization from incompatible pointer type
   (&_PyExc_DeprecationWarning), /* 387.value */
   ^
data_pypy_module_cpyext_pyobject.c:2043:3: warning: (near initialization for 'pypy_g_array_718.a.items[387].d_value')
data_pypy_module_cpyext_pyobject.c:2068:3: warning: initialization from incompatible pointer type
   (&PyLong_Type), /* 392.value */
   ^
data_pypy_module_cpyext_pyobject.c:2068:3: warning: (near initialization for 'pypy_g_array_718.a.items[392].d_value')
data_pypy_module_cpyext_pyobject.c:2083:3: warning: initialization from incompatible pointer type
   (&_PyExc_UnicodeEncodeError), /* 395.value */
   ^
data_pypy_module_cpyext_pyobject.c:2083:3: warning: (near initialization for 'pypy_g_array_718.a.items[395].d_value')
data_pypy_module_cpyext_pyobject.c:2103:3: warning: initialization from incompatible pointer type
   (&PyBytes_Type), /* 399.value */
   ^
data_pypy_module_cpyext_pyobject.c:2103:3: warning: (near initialization for 'pypy_g_array_718.a.items[399].d_value')
data_pypy_module_cpyext_pyobject.c:2133:3: warning: initialization from incompatible pointer type
   (&_PyExc_BytesWarning), /* 405.value */
   ^
data_pypy_module_cpyext_pyobject.c:2133:3: warning: (near initialization for 'pypy_g_array_718.a.items[405].d_value')
data_pypy_module_cpyext_pyobject.c:2138:3: warning: initialization from incompatible pointer type
   (&PyBool_Type), /* 406.value */
   ^
data_pypy_module_cpyext_pyobject.c:2138:3: warning: (near initialization for 'pypy_g_array_718.a.items[406].d_value')
data_pypy_module_cpyext_pyobject.c:2143:3: warning: initialization from incompatible pointer type
   (&_PyExc_UnicodeTranslateError), /* 407.value */
   ^
data_pypy_module_cpyext_pyobject.c:2143:3: warning: (near initialization for 'pypy_g_array_718.a.items[407].d_value')
data_pypy_module_cpyext_pyobject.c:2158:3: warning: initialization from incompatible pointer type
   (&_PyExc_LookupError), /* 410.value */
   ^
data_pypy_module_cpyext_pyobject.c:2158:3: warning: (near initialization for 'pypy_g_array_718.a.items[410].d_value')
data_pypy_module_cpyext_pyobject.c:2168:3: warning: initialization from incompatible pointer type
   (&_PyExc_ImportWarning), /* 412.value */
   ^
data_pypy_module_cpyext_pyobject.c:2168:3: warning: (near initialization for 'pypy_g_array_718.a.items[412].d_value')
data_pypy_module_cpyext_pyobject.c:2208:3: warning: initialization from incompatible pointer type
   (&_PyExc_MemoryError), /* 420.value */
   ^
data_pypy_module_cpyext_pyobject.c:2208:3: warning: (near initialization for 'pypy_g_array_718.a.items[420].d_value')
data_pypy_module_cpyext_pyobject.c:2233:3: warning: initialization from incompatible pointer type
   (&PyNotImplemented_Type), /* 425.value */
   ^
data_pypy_module_cpyext_pyobject.c:2233:3: warning: (near initialization for 'pypy_g_array_718.a.items[425].d_value')
data_pypy_module_cpyext_pyobject.c:2298:3: warning: initialization from incompatible pointer type
   (&PySet_Type), /* 438.value */
   ^
data_pypy_module_cpyext_pyobject.c:2298:3: warning: (near initialization for 'pypy_g_array_718.a.items[438].d_value')
data_pypy_module_cpyext_pyobject.c:2313:3: warning: initialization from incompatible pointer type
   (&_PyExc_ZeroDivisionError), /* 441.value */
   ^
data_pypy_module_cpyext_pyobject.c:2313:3: warning: (near initialization for 'pypy_g_array_718.a.items[441].d_value')
data_pypy_module_cpyext_pyobject.c:2348:3: warning: initialization from incompatible pointer type
   (&_PyExc_TabError), /* 448.value */
   ^
data_pypy_module_cpyext_pyobject.c:2348:3: warning: (near initialization for 'pypy_g_array_718.a.items[448].d_value')
data_pypy_module_cpyext_pyobject.c:2353:3: warning: initialization from incompatible pointer type
   (&_PyExc_SyntaxWarning), /* 449.value */
   ^
data_pypy_module_cpyext_pyobject.c:2353:3: warning: (near initialization for 'pypy_g_array_718.a.items[449].d_value')
data_pypy_module_cpyext_pyobject.c:2443:3: warning: initialization from incompatible pointer type
   (&_PyExc_OSError), /* 467.value */
   ^
data_pypy_module_cpyext_pyobject.c:2443:3: warning: (near initialization for 'pypy_g_array_718.a.items[467].d_value')
data_pypy_module_cpyext_pyobject.c:2463:3: warning: initialization from incompatible pointer type
   (&PyNone_Type), /* 471.value */
   ^
data_pypy_module_cpyext_pyobject.c:2463:3: warning: (near initialization for 'pypy_g_array_718.a.items[471].d_value')
data_pypy_module_cpyext_pyobject.c:2573:3: warning: initialization from incompatible pointer type
   (&PyCFunction_Type), /* 493.value */
   ^
data_pypy_module_cpyext_pyobject.c:2573:3: warning: (near initialization for 'pypy_g_array_718.a.items[493].d_value')
data_pypy_module_cpyext_pyobject.c:2603:3: warning: initialization from incompatible pointer type
   (&_PyExc_SyntaxError), /* 499.value */
   ^
data_pypy_module_cpyext_pyobject.c:2603:3: warning: (near initialization for 'pypy_g_array_718.a.items[499].d_value')
data_pypy_module_cpyext_pyobject.c:2633:3: warning: initialization from incompatible pointer type
   (&_PyExc_BufferError), /* 505.value */
   ^
data_pypy_module_cpyext_pyobject.c:2633:3: warning: (near initialization for 'pypy_g_array_718.a.items[505].d_value')
data_pypy_module_cpyext_pyobject.c:2648:3: warning: initialization from incompatible pointer type
   (&PyComplex_Type), /* 508.value */
   ^
data_pypy_module_cpyext_pyobject.c:2648:3: warning: (near initialization for 'pypy_g_array_718.a.items[508].d_value')
data_rpython_jit_metainterp_pyjitpl.c:4398:2: error: 'pypy_char2wchar' undeclared here (not in a function)
  pypy_char2wchar, /* 119 */
  ^
data_rpython_jit_metainterp_pyjitpl.c:4401:2: error: 'pypy_char2wchar_free' undeclared here (not in a function)
  pypy_char2wchar_free, /* 122 */
  ^
data_rpython_jit_metainterp_pyjitpl.c:4463:2: error: 'pypy_wchar2char' undeclared here (not in a function)
  pypy_wchar2char, /* 184 */
  ^
data_rpython_jit_metainterp_pyjitpl.c:4464:2: error: 'pypy_wchar2char_free' undeclared here (not in a function)
  pypy_wchar2char_free, /* 185 */
  ^
make: *** [data_rpython_jit_metainterp_pyjitpl.gcmap] Error 1
make: *** Waiting for unfinished jobs....
```



From issues-reply at bitbucket.org  Mon Oct 27 14:42:24 2014
From: issues-reply at bitbucket.org (Felix Schwarz)
Date: Mon, 27 Oct 2014 13:42:24 -0000
Subject: [pypy-issue] Issue #1905: pypy does not add system-wide headers to
 CFLAGS if installed in a virtualenv (pypy/pypy)
Message-ID: <20141027134224.7630.61504@app12.ash-private.bitbucket.org>

New issue 1905: pypy does not add system-wide headers to CFLAGS if installed in a virtualenv
https://bitbucket.org/pypy/pypy/issue/1905/pypy-does-not-add-system-wide-headers-to

Felix Schwarz:

I created a virtualenv with pypy as documented in the [docs](http://pypy.readthedocs.org/en/latest/install.html#installing-using-virtualenv).

However afterwards I was unable to compile lxml 3.4.0 (tar.gz from pypi) because pypy didn't find pyconfig.h. pyconfig.h is installed through pypy-devel in /usr/lib64/pypy-2.2.1

    building 'lxml.etree' extension
    cc -O2 -fPIC -Wimplicit -I/usr/include/libxml2
    -I<?>/lxml-3.4.0/src/lxml/includes
    -I<?>/venv.pypy/include -c src/lxml/lxml.etree.c -o
    build/temp.linux-x86_64-2.7/src/lxml/lxml.etree.o -w
    src/lxml/lxml.etree.c:8:22: fatal error: pyconfig.h: No such file or directory
     #include "pyconfig.h"
                          ^
    compilation terminated.
    error: command 'cc' failed with exit status 1

As you can see only "venv.pypy/include" is added via the cflags but not my system-wide directory. This works if I used the system-wide pypy.

I think pypy should match cpython's behavior and include the system-wide headers even when installed in a virtualenv.



From issues-reply at bitbucket.org  Mon Oct 27 14:51:06 2014
From: issues-reply at bitbucket.org (Stian Andreassen)
Date: Mon, 27 Oct 2014 13:51:06 -0000
Subject: [pypy-issue] Issue #1906: py3.3 branch - LZMA fail to build.
	(pypy/pypy)
Message-ID: <20141027135106.25429.55822@app11.ash-private.bitbucket.org>

New issue 1906: py3.3 branch - LZMA fail to build.
https://bitbucket.org/pypy/pypy/issue/1906/py33-branch-lzma-fail-to-build

Stian Andreassen:

Output: http://pastebin.com/CdeYWP1j

Ronan:
*it means that OutBuffer.current_size is never set to anything*

Prevents building of py3.3.



From issues-reply at bitbucket.org  Mon Oct 27 20:17:51 2014
From: issues-reply at bitbucket.org (Stian Andreassen)
Date: Mon, 27 Oct 2014 19:17:51 -0000
Subject: [pypy-issue] Issue #1907: py3.3 - pypy_char2char_free undecleared.
	(pypy/pypy)
Message-ID: <20141027191751.26750.67676@app07.ash-private.bitbucket.org>

New issue 1907: py3.3 - pypy_char2char_free undecleared.
https://bitbucket.org/pypy/pypy/issue/1907/py33-pypy_char2char_free-undecleared

Stian Andreassen:

Another build issue:
 ?pypy_wchar2char_free? undeclared here (not in a function)


```
#!python

translation:info] Error:
[translation:info]    File "/home/stian/pypy/rpython/translator/goal/translate.py", line 316, in main
[translation:info]     drv.proceed(goals)
[translation:info]    File "/home/stian/pypy/rpython/translator/driver.py", line 532, in proceed
[translation:info]     return self._execute(goals, task_skip = self._maybe_skip())
[translation:info]    File "/home/stian/pypy/rpython/translator/tool/taskengine.py", line 114, in _execute
[translation:info]     res = self._do(goal, taskcallable, *args, **kwds)
[translation:info]    File "/home/stian/pypy/rpython/translator/driver.py", line 276, in _do
[translation:info]     res = func()
[translation:info]    File "/home/stian/pypy/rpython/translator/driver.py", line 498, in task_compile_c
[translation:info]     cbuilder.compile(**kwds)
[translation:info]    File "/home/stian/pypy/rpython/translator/c/genc.py", line 394, in compile
[translation:info]     extra_opts)
[translation:info]    File "/home/stian/pypy/rpython/translator/platform/posix.py", line 196, in execute_makefile
[translation:info]     self._handle_error(returncode, stdout, stderr, path.join('make'))
[translation:info]    File "/home/stian/pypy/rpython/translator/platform/__init__.py", line 151, in _handle_error
[translation:info]     raise CompilationError(stdout, stderr)
[translation:ERROR] CompilationError: CompilationError(err="""
[translation:ERROR]     data_rpython_jit_metainterp_pyjitpl.c:4164:2: error: ?pypy_char2wchar? undeclared here (not in a function)
[translation:ERROR]       pypy_char2wchar, /* 178 */
[translation:ERROR]       ^
[translation:ERROR]     data_rpython_jit_metainterp_pyjitpl.c:4166:2: error: ?pypy_char2wchar_free? undeclared here (not in a function)
[translation:ERROR]       pypy_char2wchar_free, /* 180 */
[translation:ERROR]       ^
[translation:ERROR]     data_rpython_jit_metainterp_pyjitpl.c:4223:2: error: ?pypy_wchar2char? undeclared here (not in a function)
[translation:ERROR]       pypy_wchar2char, /* 237 */
[translation:ERROR]       ^
[translation:ERROR]     data_rpython_jit_metainterp_pyjitpl.c:4224:2: error: ?pypy_wchar2char_free? undeclared here (not in a function)
[translation:ERROR]       pypy_wchar2char_free, /* 238 */
[translation:ERROR]       ^
[translation:ERROR]     make: *** [data_rpython_jit_metainterp_pyjitpl.gcmap] Error 1
[translation:ERROR]     make: *** Waiting for unfinished jobs....
[translation:ERROR]     """)

```




From issues-reply at bitbucket.org  Tue Oct 28 13:56:32 2014
From: issues-reply at bitbucket.org (Stian Andreassen)
Date: Tue, 28 Oct 2014 12:56:32 -0000
Subject: [pypy-issue] Issue #1908: py3.3 - sys.{base_prefix, base_exec_prefix,
 thread_info} unimplemented. (pypy/pypy)
Message-ID: <20141028125632.10046.50157@app02.ash-private.bitbucket.org>

New issue 1908: py3.3 - sys.{base_prefix, base_exec_prefix, thread_info} unimplemented.
https://bitbucket.org/pypy/pypy/issue/1908/py33-sys-base_prefix-base_exec_prefix

Stian Andreassen:

This prevents the installation of setuptools.





From issues-reply at bitbucket.org  Tue Oct 28 21:36:41 2014
From: issues-reply at bitbucket.org (Philip Jenvey)
Date: Tue, 28 Oct 2014 20:36:41 -0000
Subject: [pypy-issue] Issue #1909: JIT crash on pypy3 (pypy/pypy)
Message-ID: <20141028203641.5235.15986@app11.ash-private.bitbucket.org>

New issue 1909: JIT crash on pypy3
https://bitbucket.org/pypy/pypy/issue/1909/jit-crash-on-pypy3

Philip Jenvey:

Python 3's test_dict test_literal_constructor recently began crashing in the JIT:

http://buildbot.pypy.org/summary/longrepr?testname=unmodified&builder=pypy-c-jit-linux-x86-64&build=2319&mod=lib-python.3.test.test_dict

Here's the isolated case:


```
#!python

Python 3.2.5 (a245775c1e36, Oct 28 2014, 17:33:50)
[PyPy 2.5.0-alpha0 with GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.54)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
And now for something completely different: ``it's nonsense all the way down,
and also all the way up''
>>>> import random, string
>>>> [''.join(random.sample(string.ascii_letters, 8)) for i in range(159)]
RPython traceback:
  File "rpython_jit_metainterp_compile.c", line 21897, in send_loop_to_backend
  File "rpython_jit_backend_x86_assembler.c", line 2157, in Assembler386_assemble_loop
  File "rpython_jit_backend_x86_assembler.c", line 5148, in Assembler386__assemble
  File "rpython_jit_backend_x86_regalloc.c", line 1988, in RegAlloc_walk_operations
  File "rpython_jit_backend_llsupport_regalloc.c", line 8479, in BaseRegalloc_can_merge_with_next_guard
Fatal RPython error: NotImplementedError
Abort trap: 6

```

Related to the pinning changes maybe?



From issues-reply at bitbucket.org  Wed Oct 29 19:11:13 2014
From: issues-reply at bitbucket.org (Buck Evan)
Date: Wed, 29 Oct 2014 18:11:13 -0000
Subject: [pypy-issue] Issue #1910: fdopen of pty doesn't match cpython
	behavior (pypy/pypy)
Message-ID: <20141029181113.3653.93950@app06.ash-private.bitbucket.org>

New issue 1910: fdopen of pty doesn't match cpython behavior
https://bitbucket.org/pypy/pypy/issue/1910/fdopen-of-pty-doesnt-match-cpython

Buck Evan:

This is quite similar issue to issue #956, but my script doesn't fail on cpython:

```
$ python2.6 scratch.py
pipe works
pty works

$ python3.4 scratch.py                                                            
pipe works
pty works

$ pypy scratch.py                                                                 
pipe works
Traceback (most recent call last):
  File "app_main.py", line 51, in run_toplevel
  File "scratch.py", line 55, in <module>
    exit(main())
  File "scratch.py", line 51, in main
    print(test_pty())
  File "scratch.py", line 31, in test_pty
    out = pipe_output(read, write)
  File "scratch.py", line 23, in pipe_output
    return fdopen(read).read().replace('\r\n', '\n')
IOError: [Errno 5] Input/output error: '<fdopen>'

$ pypy3 scratch.py
pipe works
Traceback (most recent call last):
  File "scratch.py", line 55, in <module>
    exit(main())
  File "scratch.py", line 51, in main
    print(test_pty())
  File "scratch.py", line 31, in test_pty
    out = pipe_output(read, write)
  File "scratch.py", line 23, in pipe_output
    return fdopen(read).read().replace('\r\n', '\n')
IOError: [Errno 5] Input/output error
```

Reproduction script:
```
#!python

from __future__ import print_function
from __future__ import unicode_literals


def pipe_output(read, write):
    from os import fork, close
    from subprocess import Popen
    if fork(): #parent
        close(write)
    else:
        close(read)
        Popen(
            ('echo', 'hi', 'there!'),
            stdout=write,
            close_fds=True,
            universal_newlines=True,
        )
        close(write)
        exit()

    from os import fdopen

    return fdopen(read).read().replace('\r\n', '\n')



def test_pty():
    from os import openpty
    read, write = openpty()

    out = pipe_output(read, write)

    assert out == 'hi there!\n', repr(out)

    return 'pty works'


def test_pipe():
    from os import pipe
    read, write = pipe()

    out = pipe_output(read, write)

    assert out == 'hi there!\n', repr(out)

    return 'pipe works'


def main():
    print(test_pipe())
    print(test_pty())


if __name__ == '__main__':
    exit(main())
```

If I create my own read-loop, I can force pypy behavior to match, but it's error prone and a huge pain. Replacing `fdopen().read()` with:

```
    from os import read as fread

    result = []
    lastread = None
    while lastread != '':
        try:
            lastread = fread(read, 1025)
        except OSError as err:
            if err.errno == 5:
                break  # slave closed
            else:
                raise
        result.append(lastread)

    close(read)
    return ''.join(result)
```



From issues-reply at bitbucket.org  Wed Oct 29 21:32:28 2014
From: issues-reply at bitbucket.org (Stian Andreassen)
Date: Wed, 29 Oct 2014 20:32:28 -0000
Subject: [pypy-issue] Issue #1911: py3.3 - datetime (pypy/pypy)
Message-ID: <20141029203228.26533.6735@app14.ash-private.bitbucket.org>

New issue 1911: py3.3 - datetime
https://bitbucket.org/pypy/pypy/issue/1911/py33-datetime

Stian Andreassen:

Trying to import datetime fails. Not sure what to make of this,

works fine in CPython3.4, but not in pypy:

```
#!python

Python 3.3.5 (2c4e59799687, Oct 28 2014, 11:07:24)
[PyPy 2.5.0-alpha0 with GCC 4.9.1] on linux
Type "help", "copyright", "credits" or "license" for more information.
And now for something completely different: ``I might, but nobody respects me''
>>>> import datetime
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "<frozen importlib._bootstrap>", line 1669, in __import__
  File "<frozen importlib._bootstrap>", line 1587, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1568, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1535, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 1092, in load_module
  File "<frozen importlib._bootstrap>", line 563, in module_for_loader_wrapper
  File "<frozen importlib._bootstrap>", line 856, in _load_module
  File "<frozen importlib._bootstrap>", line 1097, in get_code
  File "<frozen importlib._bootstrap>", line 818, in _bytes_from_bytecode
ImportError: bad magic number in 'datetime': b'\x0b\xf3\r\n'

```



From issues-reply at bitbucket.org  Thu Oct 30 19:32:17 2014
From: issues-reply at bitbucket.org (Buck Evan)
Date: Thu, 30 Oct 2014 18:32:17 -0000
Subject: [pypy-issue] Issue #1912: subprocess deadlock in pypy3 (pypy/pypy)
Message-ID: <20141030183217.16639.31895@app13.ash-private.bitbucket.org>

New issue 1912: subprocess deadlock in pypy3
https://bitbucket.org/pypy/pypy/issue/1912/subprocess-deadlock-in-pypy3

Buck Evan:

I've put all the details in a pytest ticket. I can't tell whose bug it is at this point, so I'm cross-referencing it here as well:


https://bitbucket.org/hpk42/pytest/issue/625/xdist-deadlock-under-pypy



From issues-reply at bitbucket.org  Fri Oct 31 08:47:06 2014
From: issues-reply at bitbucket.org (Robert Collins)
Date: Fri, 31 Oct 2014 07:47:06 -0000
Subject: [pypy-issue] Issue #1913: compileall tries to compile non python
	files (pypy/pypy)
Message-ID: <20141031074706.7274.51490@app10.ash-private.bitbucket.org>

New issue 1913: compileall tries to compile non python files
https://bitbucket.org/pypy/pypy/issue/1913/compileall-tries-to-compile-non-python

Robert Collins:

I filed this:
https://github.com/pypa/pip/issues/2111

And the helpful folk there pointed out that this was unique to pypy. 





From issues-reply at bitbucket.org  Fri Oct 31 22:12:55 2014
From: issues-reply at bitbucket.org (Ronan Lamy)
Date: Fri, 31 Oct 2014 21:12:55 -0000
Subject: [pypy-issue] Issue #1914: Translation failure in hippy master
	(pypy/pypy)
Message-ID: <20141031211255.26362.32223@app02.ash-private.bitbucket.org>

New issue 1914: Translation failure in hippy master
https://bitbucket.org/pypy/pypy/issue/1914/translation-failure-in-hippy-master

Ronan Lamy:

8e1098ac3210 broke hippy translation with -Ojit  http://pastebin.com/3fBJbFeH