Re: Packaging pypy

To: Kay Hayen <kayhayen@gmx.de>
Cc: debian-python@lists.debian.org
Subject: Re: Packaging pypy
From: Thomas Kluyver <thomas@kluyver.me.uk>
Date: Thu, 1 Dec 2011 00:05:29 +0000
Message-id: <[🔎] CAOvn4qgjhd5-ZVkJs5FJZvXH8OktS3NH6A_pKuMhWEbSJGwUzQ@mail.gmail.com>
In-reply-to: <4ED6C131.3080909@gmx.de>
References: <CANySw1mZ0qdVT7RDcGAkLJqu_XS7Wb-QwbBd=wnn9EDrLELD4Q@mail.gmail.com> <20111128202518.GI6680@bach.rivera.co.za> <4ED4CE3E.1070907@debian.org> <20111130165448.GF29939@bach.rivera.co.za> <4ED67D6D.7000507@gmx.de> <20111130195946.GH29939@bach.rivera.co.za> <4ED6AC94.6050004@gmx.de> <CAOvn4qicbt4bF0cmbPa_p3i7LC0Qy5+mqMEtQb1MCb2A6Ak9Ew@mail.gmail.com> <4ED6C131.3080909@gmx.de>

On 30 November 2011 23:50, Kay Hayen <kayhayen@gmx.de> 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 that is your concern.

Neat! I'll try to get round to having a look at Nuitka at some point (in terms of using it, not packaging it - sorry, I can't help there).

Thomas

Reply to:

Next by Date: RFS: etm
Next by thread: Re: Packaging pypy
Index(es):
- Date
- Thread