On Thu, Oct 12, 2006, Thomas Bushnell BSG wrote:
> I'm afraid that compliance with the Brand New Python Policy is not on
> the list of release goals for etch
Just for the record, the Good Old Python Policy already forbids
to ship .pyc files.
--
Sam.
--
To UNSUBSCRIBE, email to [EMAIL PROT
severity 392488 important
thanks
You can now stop playing BTS tag; thanks.
Andreas Barth <[EMAIL PROTECTED]> writes:
> severity 392488 serious
>
> * Thomas Bushnell BSG ([EMAIL PROTECTED]) [061012 10:39]:
>> However, .pyc files are machine-independent, so there is no violation
>> in having them
severity 392488 serious
* Thomas Bushnell BSG ([EMAIL PROTECTED]) [061012 10:39]:
> However, .pyc files are machine-independent, so there is no violation
> in having them in an architecture independent package and directory.
pyc-files are machine-dependend in the way that they might be different
severity 392488 important
retitle 392488 lilypond-data: don't ship .pyc files in accord with Python policy
thanks
"Sam Hocevar \(Debian packages\)" <[EMAIL PROTECTED]> writes:
> Package: lilypond-data
> Version: 2.6.5-2
> Severity: serious
> Justification: Policy 9.1.1
>
>/usr/share/lilypond
Package: lilypond-data
Version: 2.6.5-2
Severity: serious
Justification: Policy 9.1.1
/usr/share/lilypond/2.6.5/python/*.pyc should be moved out of /usr/share
and out of the Arch:all package.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'un
5 matches
Mail list logo
