On Mon, Dec 22, 2008 at 3:10 AM, Pauli Virtanen wrote:
> Mon, 22 Dec 2008 00:30:55 +0900, David Cournapeau wrote:
>
>> On Sun, Dec 21, 2008 at 11:42 PM, Pauli Virtanen wrote:
>>> Sun, 21 Dec 2008 22:48:41 +0900, David Cournapeau wrote: [clip]
Is everything under trunk/doc necessary to bu
Mon, 22 Dec 2008 00:30:55 +0900, David Cournapeau wrote:
> On Sun, Dec 21, 2008 at 11:42 PM, Pauli Virtanen wrote:
>> Sun, 21 Dec 2008 22:48:41 +0900, David Cournapeau wrote: [clip]
>>> Is everything under trunk/doc necessary to build the doc ? Or only
>>> a
>>> subset of it ?
>>
>> Only
On Fri, Dec 19, 2008 at 4:30 PM, Ondrej Certik wrote:
> while packaging the new version of numpy, I realized that it is
> missing a documentation. I just checked with Stefan on Jabber and he
> thinks
> it should be rather a trivial fix. Do you Jarrod think you could
> please release a new tarball
On Sun, Dec 21, 2008 at 11:42 PM, Pauli Virtanen wrote:
> Sun, 21 Dec 2008 22:48:41 +0900, David Cournapeau wrote:
> [clip]
>> Is everything under trunk/doc necessary to build the doc ? Or only a
>> subset of it ?
>
> Only a subset: Makefile, postprocess.py, release/*, source/*, and
> sphinxex
Sun, 21 Dec 2008 22:48:41 +0900, David Cournapeau wrote:
[clip]
> Is everything under trunk/doc necessary to build the doc ? Or only a
> subset of it ?
Only a subset: Makefile, postprocess.py, release/*, source/*, and
sphinxext/*.
The rest is some older material (eg. numpybook/*), stuff targ
Pauli Virtanen wrote:
> Sun, 21 Dec 2008 13:05:57 +0100, Ondrej Certik wrote:
>
>
>> On Sat, Dec 20, 2008 at 3:02 PM, Pauli Virtanen wrote:
>>
>>> Sat, 20 Dec 2008 20:15:43 +0900, David Cournapeau wrote:
>>>
On Sat, Dec 20, 2008 at 7:43 PM, Ondrej Certik
wrote:
On Sun, Dec 21, 2008 at 1:49 PM, Pauli Virtanen wrote:
> Sun, 21 Dec 2008 13:05:57 +0100, Ondrej Certik wrote:
>
>> On Sat, Dec 20, 2008 at 3:02 PM, Pauli Virtanen wrote:
>>> Sat, 20 Dec 2008 20:15:43 +0900, David Cournapeau wrote:
On Sat, Dec 20, 2008 at 7:43 PM, Ondrej Certik
wrote:
Sun, 21 Dec 2008 13:05:57 +0100, Ondrej Certik wrote:
> On Sat, Dec 20, 2008 at 3:02 PM, Pauli Virtanen wrote:
>> Sat, 20 Dec 2008 20:15:43 +0900, David Cournapeau wrote:
>>> On Sat, Dec 20, 2008 at 7:43 PM, Ondrej Certik
>>> wrote:
Just to make it clear -- I think the docs should not be ge
Ondrej Certik wrote:
>
> Why not to just include the *sources* together with numpy, and
> possibly include html+whatever in a separate documentation package?
>
I don't think having separate built doc and built package is a good
idea. It is confusing for the user, and I am afraid we won't alway
On Sat, Dec 20, 2008 at 3:02 PM, Pauli Virtanen wrote:
> Sat, 20 Dec 2008 20:15:43 +0900, David Cournapeau wrote:
>> On Sat, Dec 20, 2008 at 7:43 PM, Ondrej Certik wrote:
>>> Just to make it clear -- I think the docs should not be generated in
>>> the tarball -- only the sources should be there.
Sat, 20 Dec 2008 20:15:43 +0900, David Cournapeau wrote:
> On Sat, Dec 20, 2008 at 7:43 PM, Ondrej Certik wrote:
>> Just to make it clear -- I think the docs should not be generated in
>> the tarball -- only the sources should be there.
>
> I agree this makes more sense for you, as a packager, bu
Gael Varoquaux wrote:
>
> For Mayavi/ETS we put both. Docs are very important, and we feared people
> having difficulties building them, as the doc build tools and build chain
> isn't as mature as the rest of the build chain.
>
Yes, I don't think anyone is arguing for users to build the doc. Wh
On Sat, Dec 20, 2008 at 08:15:43PM +0900, David Cournapeau wrote:
> For audiolab, I put the generated doc, thinking if people want to mess
> with the doc, they are knowledgeable enough to deal with svn - but I
> did not think about the packagers :) I am not sure what's the best
> solution: maybe pu
On Sat, Dec 20, 2008 at 7:43 PM, Ondrej Certik wrote:
>
> Just to make it clear -- I think the docs should not be generated in
> the tarball -- only the sources should be there.
I agree this makes more sense for you, as a packager, but I am not
sure it makes much sense to put the doc sources in
On Sat, Dec 20, 2008 at 3:35 AM, David Cournapeau wrote:
> On Sat, Dec 20, 2008 at 7:43 AM, Stéfan van der Walt wrote:
>> 2008/12/20 Ondrej Certik :
>>> So we thought with Stefan that maybe a simpler solution is just to fix
>>> the ./setup sdist (or how you create the tarball in numpy) to include
On Sat, Dec 20, 2008 at 7:43 AM, Stéfan van der Walt wrote:
> 2008/12/20 Ondrej Certik :
>> So we thought with Stefan that maybe a simpler solution is just to fix
>> the ./setup sdist (or how you create the tarball in numpy) to include
>> documentation and be done with it.
>
> I think releases sho
2008/12/20 Ondrej Certik :
> So we thought with Stefan that maybe a simpler solution is just to fix
> the ./setup sdist (or how you create the tarball in numpy) to include
> documentation and be done with it.
I think releases should either include the Sphinx documentation or,
alternatively, we sho
Hi,
while packaging the new version of numpy, I realized that it is
missing a documentation. I just checked with Stefan on Jabber and he
thinks
it should be rather a trivial fix. Do you Jarrod think you could
please release a new tarball with the doc directory?
The problem is that debian (and I g
18 matches
Mail list logo
