On Mon, 2 Nov 2009 16:50:00 +0300 anatoly techtonik wrote:
>On Mon, Nov 2, 2009 at 2:27 PM, Scott Kitterman wrote:
>>
>> I'm not aware of any ongoing work. I would be willing to help work on such
>> a thing, but we currently lack a good mechanism for developing/approving
>> such a policy.
>
>Wit
On Mon, Nov 2, 2009 at 2:27 PM, Scott Kitterman wrote:
>
> I'm not aware of any ongoing work. I would be willing to help work on such
> a thing, but we currently lack a good mechanism for developing/approving
> such a policy.
With clear policy and precise goal you won't need approving mechanism
On Mon, 02 Nov 2009 21:22:47 +1100 Ben Finney
wrote:
>Luca Falavigna writes:
>
>> Scott Kitterman ha scritto:
>> > Since we currently lack anything like a maintained Python policy, I
>> > think this is putting the cart before the horse. [ &]
>
>> [ &] we could wait for the new policy to be draft
Jakub Wilk ha scritto:
>> * E: Don't hard-code {site,dist}-packages
>
> Uhm, what do you mean?
That's what we are trying to fix with
http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-pyt...@lists.debian.org;tag=dist-packages
In case we missed some packages, or some NEW ones were included
Steve Langasek ha scritto:
>> * E: Don't hard-code {site,dist}-packages
>
> hard-coded where, and how will you detect this?
debian/rules and other control files such as debian/install and
debian/links.
>> * W: Build extension for every supported Python version
>
> how will you detect this?
Pa
Luca Falavigna writes:
> Scott Kitterman ha scritto:
> > Since we currently lack anything like a maintained Python policy, I
> > think this is putting the cart before the horse. […]
> […] we could wait for the new policy to be drafted, I'm not sure when
> this will happen, though.
I don't know
Scott Kitterman ha scritto:
>> * E: Don't hard-code {site,dist}-packages
>> * E: Python files in incorrect python2.?/{site,dist}-packages directory
>
> Since we currently lack anything like a maintained Python policy, I think
> this is putting the cart before the horse. Particularly any Error le
Ben Finney ha scritto:
>> * I: Place Python applications in private directory
>
> What would be the test for these cases? That is, what would Lintian
> actually check in the package to determine whether these should be
> emitted?
This is quite complex to say, I initially thought of checking for f
8 matches
Mail list logo
