[Mathieu Malaterre, 2011-11-29]
[Please CC me]
done
I am trying to fix bug #649904. I have been talking with upstream,
and apparently the install process on debian is doing something weird
after the line running install_data, see for instance :
On Tue, Nov 29, 2011 at 10:44 AM, Piotr Ożarowski pi...@debian.org wrote:
[Mathieu Malaterre, 2011-11-29]
I am trying to fix bug #649904. I have been talking with upstream,
and apparently the install process on debian is doing something weird
after the line running install_data, see for
On 11/28/2011 09:25 PM, Stefano Rivera wrote:
Of course, it would have to be packaged as a separate Python stack,
again. Although it would be interesting to allow modules to be built for
alternate Python implementations, but that's not a trivial project...
maybe for binary packages, but there
On 11/29/2011 09:56 AM, Maciej Fijalkowski wrote:
For what is worth, the .py files (but not the .pyc files) can be
shared among pypy and cpython.
IMO, patching pypy to lookup e.g. .pycp files before .pyc files would be
appropriate for Debian (already doing something like this for .so files in
I suppose it's not really that much work, but that would mean waiting
for another pypy release (which is probably 2-3 months away)
The package may include a patch to enable that specifically, if necessary.
--
Gustavo Niemeyer
http://niemeyer.net
http://niemeyer.net/plus
5 matches
Mail list logo