[Python-modules-team] Bug#559916: Bug#559916: Bug#559916: Lots of code duplication because this is still unresolved

[Sandro Tosi]

Hello,

On Fri, Oct 1, 2010 at 02:30, Ondrej Certik <ondrej at certik.cz> wrote:
> On Thu, Sep 30, 2010 at 3:46 PM, Michael Hanke <michael.hanke at gmail.com> wrote:
>> On Thu, Sep 30, 2010 at 11:56:03PM +0200, Sandro Tosi wrote:
>>> Thanks for your interest in this bug; are you also going a bit further
>>> and propose a patch to fix it (this would actually help to resolve
>>> this bug)?
>>
>> I might. However, proposing a patch is probably not an adequate first
>> action.
>>
>> What is your general attitude towards the problem? Should there be a
>> separate package as suggested in the initial report? Or should it simply
>> be installed along the rest of numpy (I guess all packages using
>> numpydoc also imploy/depend on numpy)? Was this bug ever discussed with
>> upstream?

The reply to this question (the same thing I wondered some time ago)
is: how other packages do? is there some other packages that ship
third party sphinx extensions? how do they install them?

What would you want to discuss with upstream about that? it seems a
distribution problem not an upstream one.

> Or try to get this accepted into sphinx upstream? I think that's the
> best solution.

I don't think so, for upstream it's an additional level of complexity:
what if numpy wants to release a new version (also containing changes
in numpydoc), should they have to wait for sphinx to release or
coordinate? it seems unpractical.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi