Hello.
I've read the draft python policy, and my packages follow it. There is,
however, something that I think is missing. What's the policy on
byte-compilation? Should there be both .pyc and .pyo files? Should the
files be compiled in the postinst script or can they be distributed with
the packag
On Thu, Jul 25, 2002 at 01:05:27PM +0200, Martin Sjögren wrote:
> Hello.
>
> I've read the draft python policy, and my packages follow it. There is,
> however, something that I think is missing. What's the policy on
> byte-compilation? Should there be both .pyc and .pyo files? Should the
> files b
On Thu, Jul 25, 2002 at 01:05:27PM +0200, Martin Sjögren wrote:
> I've read the draft python policy, and my packages follow it. There is,
> however, something that I think is missing. What's the policy on
> byte-compilation? Should there be both .pyc and .pyo files? Should the
> files be compiled i
On Thu, Jul 25, 2002 at 01:54:24PM +0200, Bastian Kleineidam wrote:
> On Thu, Jul 25, 2002 at 01:05:27PM +0200, Martin Sjögren wrote:
> > I've read the draft python policy, and my packages follow it. There is,
> > however, something that I think is missing. What's the policy on
> > byte-compilation
Dave Swegen <[EMAIL PROTECTED]> wrote:
> Surely the right way to handle this is using debconf in the main python
> packages, and subsequently any packages check this to see if python
> scripts should be compiled or not. Or have I missed anything?
You are talking about (compiling the .py in postin
On Thu, Jul 25, 2002 at 02:41:09PM +0200, Florent Rougon wrote:
> Dave Swegen <[EMAIL PROTECTED]> wrote:
>
> > Surely the right way to handle this is using debconf in the main python
> > packages, and subsequently any packages check this to see if python
> > scripts should be compiled or not. Or h
Sorry, I've not checked for existing threads on this topic... will Sarge
use Python2.2 by any chance? Once this is decided, the sooner it is made
official, the sooner packages will start updating, and the faster we
will get a stable Sarge...
Specifically, I am wondering if I should go to the troub
Il gio, 2002-07-25 alle 16:04, Hugo van der Merwe ha scritto:
> Sorry, I've not checked for existing threads on this topic... will Sarge
> use Python2.2 by any chance? Once this is decided, the sooner it is made
> official, the sooner packages will start updating, and the faster we
> will get a sta
Federico Di Gregorio <[EMAIL PROTECTED]>:
> Il gio, 2002-07-25 alle 16:04, Hugo van der Merwe ha scritto:
> > Sorry, I've not checked for existing threads on this topic... will Sarge
> > use Python2.2 by any chance? Once this is decided, the sooner it is made
> > official, the sooner packages will
Dave Swegen <[EMAIL PROTECTED]> wrote:
> Not having really followed the discussion, and being faaar too bone-idle
> to actually look it up in the archives, this is my view on it: Shipping
> pre-compiled really isn't an option, as the size increase would be
> unacceptable - not only from a debian a
On Jul 25, Matthias Klose wrote:
> My current plan is:
>
> - upload python2.3 packages soon (when 2.3alpha1 is released)
>
> - remove python1.5 from unstable
>
> - adopt python-central for 2.1, 2.2 and 2.3, hopefully with the
> help of the author, hint, hint
>
> - upload python2.3 beta to uns
On Thu, Jul 25, 2002 at 03:28:59PM -0500, Chris Lawrence wrote:
> On Jul 25, Matthias Klose wrote:
> > My current plan is:
> >
> > - upload python2.3 packages soon (when 2.3alpha1 is released)
> >
> > - remove python1.5 from unstable
> >
> > - adopt python-central for 2.1, 2.2 and 2.3, hopefully
12 matches
Mail list logo
