pypy debian patch causes pip to leave behind pkg dirs

[qwcode]

the debian distribution of pypy that travis uses is unexpectedly compiling with __pycache__ folders.

1. pip's installed-files.txt manifest is reporting inline .pyc files
2. due to No instructions for how to install pip #1, pip fails to remove all the contents of pkg dirs, specifically, the __pycache__ folders

a number of pypy tests are failing.
debug effort is here: #621

full thread from the pypy list is here: http://mail.python.org/pipermail/pypy-dev/2012-July/thread.html#10369

******** explanation from debian packager ********

Stefano Rivera stefano@rivera.za.net via python.org
Jul 31 (4 days ago)

to pypy-dev
Hi Armin (2012.07.31_09:25:08_+0200)

PyPy contains no logic to create or search for pycache. A grep
tells me that neither does CPython 2.7. You are probably confused by
py.test creating them.

A Debian/Ubuntu pypy does, though. And IIRC, that's what travis CI is
using.

It's the pep3147 patches:
http://anonscm.debian.org/gitweb/?p=collab-maint/pypy.git;a=tree;f=debian/patches

I thought it would be a useful feature, to make transition between pypy
versions in Debian easier. Proposed the patches in #pypy, and the
reception was lukewarm, so I never pushed harder.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.