On Tue, Nov 29, 2011 at 6:02 PM, Barry Warsaw wrote:
> On Nov 29, 2011, at 02:19 PM, Matthias Klose wrote:
>
>>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
On Nov 29, 2011, at 02:11 PM, Gustavo Niemeyer wrote:
>> 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.
Right. We could cherrypick
> 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
http://niemeyer.net/t
On Nov 29, 2011, at 02:19 PM, Matthias Klose wrote:
>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
On Nov 29, 2011, at 04:20 PM, Maciej Fijalkowski wrote:
>Bytecode format is an internal detail of a VM. For all I know it might
>completely disappear. CPython likes to change it's bytecode format
>every release and we usually follow changes, but we also have quite a
>few our own bytecodes. The thi
On Tue, Nov 29, 2011 at 4:13 PM, Stefano Rivera wrote:
> Hi Matthias (2011.11.29_14:21:18_+0200)
>> maybe for binary packages, but there is no reason why a pypy extension
>> couldn't
>> be built from the same source packages. Could you summarize why it needs to
>> be
>> a separate stack?
>
> On
Hi Gustavo (2011.11.29_14:43:30_+0200)
> That's great to hear, thanks for stepping up Stefano. PyPy indeed
> seems most ready for having some wider experimentation with, and we'd
> also appreciate having it in Ubuntu.
It'd be my most ambitious package. But that's where the fun is, right? :)
SR
-
Hi Matthias (2011.11.29_14:21:18_+0200)
> maybe for binary packages, but there is no reason why a pypy extension
> couldn't
> be built from the same source packages. Could you summarize why it needs to
> be
> a separate stack?
One question is: How broken we want to allow modules to be.
If it's
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'm interested in this, and happy to help. It's probably time to get
> PyPy back into Debian, I think all of our amd64 and i386 buildds are big
> enough to handle it these days. How do people feel about the other
> concerns raised by lamby (CCed, don't know if he still follows this
> list) when h
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 ther
On Tue, Nov 29, 2011 at 10:44 AM, Piotr Ożarowski 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 instance :
>
[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 :
>
> https://buildd.debian.org/status/f
[Please CC me]
Hi all,
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 :
https://buildd.debian.org/status/fetch.php?pkg=pylibtiff&arch=i386&ver=0.3.0
On Mon, Nov 28, 2011 at 10:25 PM, Stefano Rivera wrote:
> Hi Gustavo (2011.11.28_18:32:52_+0200)
>> Would someone here be able to give a hand to Maciej on pushing that
>> integration forward?
>
> I'm interested in this, and happy to help. It's probably time to get
> PyPy back into Debian, I think
15 matches
Mail list logo
