Hi debian-python (2011.12.23_13:44:44_+0200)
> ... so, I've spent some time on this, and have an incomplete package to
> show for it: http://anonscm.debian.org/gitweb/?p=users/stefanor/pypy.git
Spent a morning on it, and it seems to be working nicely now.
Test failures are almost all dealt with (
Hi Maciej (2011.12.24_12:25:28_+0200)
> Wouldn't looking always at /usr first break checkout overriding system
> version? That would be very unfortunate unless this is only for the
> debian-modified version.
Yes, I meant that as a debian-specific workaround. But it would break
virtualenv. Grumble,
On Fri, Dec 23, 2011 at 1:44 PM, Stefano Rivera wrote:
> Hi debian-python (2011.11.28_22:25:18_+0200)
>> I'm interested in this, and happy to help.
>
> ... so, I've spent some time on this, and have an incomplete package to
> show for it: http://anonscm.debian.org/gitweb/?p=users/stefanor/pypy.git
Hi debian-python (2011.11.28_22:25:18_+0200)
> I'm interested in this, and happy to help.
... so, I've spent some time on this, and have an incomplete package to
show for it: http://anonscm.debian.org/gitweb/?p=users/stefanor/pypy.git
Got lots of family things happening atm, so haven't done anythi
On 30 November 2011 23:50, Kay Hayen wrote:
> That is only if the ".py" file doesn't exist, right? Why wouldn't it. To
> me, compilation is not about removing the source code. Not at all, it's
> only about acceleration.
>
> Nuitka's "compiled_function" is way more compatible that "PyCFunction" if
Hello Thomas,
It could turn every "module.py" into a "module.so" with more or less
dubious benefits.
Note that there are a few differences between compiled and pure Python
modules. E.g.
- Tracebacks to errors won't show code from compiled files.
That is only if the ".py" file doe
On 30 November 2011 22:22, Kay Hayen wrote:
> It could turn every "module.py" into a "module.so" with more or less
> dubious benefits.
Note that there are a few differences between compiled and pure Python
modules. E.g.
- Tracebacks to errors won't show code from compiled files.
- Functions ass
Hello Stefano,
Am 30.11.2011 20:59, schrieb Stefano Rivera:
Hi Kay (2011.11.30_21:01:01_+0200)
The logical follow up is, how about X-Alternate-Python-Stacks ?
I was contemplating that long term, once Nuitka is really a useful
accelerator, it should be allowed to compile modules, whole
packag
Hi Kay (2011.11.30_21:01:01_+0200)
> >The logical follow up is, how about X-Alternate-Python-Stacks ?
>
> I was contemplating that long term, once Nuitka is really a useful
> accelerator, it should be allowed to compile modules, whole
> packages, or programs at install time.
>
> Will that fit int
Hello,
Am 30.11.2011 17:54, schrieb Stefano Rivera:
We'd probably want something like X-PyPy-Version to state PyPy support.
The logical follow up is, how about X-Alternate-Python-Stacks ?
I was contemplating that long term, once Nuitka is really a useful
accelerator, it should be allowed to
Hi Barry (2011.11.29_18:00:07_+0200)
> While chatting about this in irc (#debian-python on oftc), I mistakenly
> thought that PyPy supported PEP 3147, but I think it's only PEP 3149. 3147
> shouldn't be that difficult to support - what is your thought on adding that
> to PyPy? It would mean one l
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?
Sorry, discussion on IRC yesterday, made me realise that I was uncle
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 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
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 all of our amd64 and i386 buildds are big
enough to handle it thes
Sorry, _actually_ CCd now.
On Mon, Nov 28, 2011 at 14:54, Gustavo Niemeyer
wrote:
> Hello Ubuntu/Debian Pythoneers,
>
> Maciej (CCd) contacted me last week to figure how to get pypy
> officially onto Ubuntu. Being the newbie Debian/Ubuntu developer that
> I am, I have no idea either, so I contact
Hello Ubuntu/Debian Pythoneers,
Maciej (CCd) contacted me last week to figure how to get pypy
officially onto Ubuntu. Being the newbie Debian/Ubuntu developer that
I am, I have no idea either, so I contacted the internal company
mailing list, that finally guided me towards this forum as the right
Hello Ubuntu/Debian Pythoneers,
Maciej (CCd) contacted me last week to figure how to get pypy
officially onto Ubuntu. Being the newbie Debian/Ubuntu developer that
I am, I have no idea either, so I contacted the internal company
mailing list, that finally guided me towards this forum as the right
28 matches
Mail list logo
