What is the point of pre-compiling C code before packaging it into
.debs? If you can answer that, apply that answer to Python code.
Subverting the Debian package management system seems a bit odd for
a Debian package to do, yet this is the impression I get from each
Python package I install
On Sat, Feb 23, 2002 at 02:19:49PM +, Lazarus Long wrote:
What is the point of pre-compiling C code before packaging it into
.debs? If you can answer that, apply that answer to Python code.
First off, in python the source IS the program. Like perl, it
byte-compiles as an optimization at
Adam Olsen (2002-02-23 15:11:41 +) :
So on one side you have plain source,
[...]
On the other side you could do it like C,
[...]
And in the middle you have the current method, which only suffers from
the minor issues of the .py[co] files not being known to dpkg, and
taking slightly
On 23-Feb-2002 Roland Mas wrote:
Adam Olsen (2002-02-23 15:11:41 +) :
So on one side you have plain source,
[...]
On the other side you could do it like C,
[...]
And in the middle you have the current method, which only suffers from
the minor issues of the .py[co] files not being
On Sat, Feb 23, 2002 at 02:19:49PM +, Lazarus Long wrote:
What is the point of pre-compiling C code before packaging it into
.debs? If you can answer that, apply that answer to Python code.
The C ABI is rather more stable than that for Python (or Emacs).
Taking away the precompiled
On Sat, 23 Feb 2002 15:11:41 + Adam Olsen [EMAIL PROTECTED] wrote:
On Sat, Feb 23, 2002 at 02:19:49PM +, Lazarus Long wrote:
What is the point of pre-compiling C code before packaging it into
.debs? If you can answer that, apply that answer to Python code.
First off, in python
6 matches
Mail list logo
