[issue4552] Doc/tools/sphinxext not included in the 2.6.1 tarball

Georg Brandl <[EMAIL PROTECTED]> added the comment: Well, those which "make checkout" checks out :) I set this up so that nobody needs to care about any additional packages or dependencies, as long as svn is installed and working. -- nosy: +georg.brandl

[issue4552] Doc/tools/sphinxext not included in the 2.6.1 tarball

Christian Heimes <[EMAIL PROTECTED]> added the comment: I don't want to *include* sphinx, jinja and docutils but *document* which versions of sphinx, jinja and docutils are required to build the docs. ___ Python tracker <[EMAIL PROTECTED]>

[issue4552] Doc/tools/sphinxext not included in the 2.6.1 tarball

Matthias Klose <[EMAIL PROTECTED]> added the comment: > In my opinion the tar balls should contain all necessary bits and pieces > to build the docs yourself. It makes no sense to include the Doc/ folder > w/o any means to use them. + 1 > Let's include sphinxext and document the required versio

[issue4552] Doc/tools/sphinxext not included in the 2.6.1 tarball

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: This is a duplicate of issue 4551 I do *not* think that Doc/tools should include a complete sphinx checkout; doing "make checkout" is completely acceptable for anybody who wants to build the doc. However, sphinxext is different; this was fix

[issue4552] Doc/tools/sphinxext not included in the 2.6.1 tarball

Christian Heimes <[EMAIL PROTECTED]> added the comment: In my opinion the tar balls should contain all necessary bits and pieces to build the docs yourself. It makes no sense to include the Doc/ folder w/o any means to use them. Let's include sphinxext and document the required versions of sphin

[issue4552] Doc/tools/sphinxext not included in the 2.6.1 tarball

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: Wait, should Doc/tools/sphinxext be included in the source tarball or not? I thought it was a documentation build artifact. If so, then we need to clean out the pycs it contains in a different way. In any case, the 3.0 tarballs should incl

[issue4552] Doc/tools/sphinxext not included in the 2.6.1 tarball

Christian Heimes <[EMAIL PROTECTED]> added the comment: Does it also affect Python 3.0? -- assignee: -> barry nosy: +barry, christian.heimes stage: -> test needed type: -> resource usage ___ Python tracker <[EMAIL PROTECTED]>

[issue4552] Doc/tools/sphinxext not included in the 2.6.1 tarball

New submission from Matthias Klose <[EMAIL PROTECTED]>: Doc/tools/sphinxext not included in the 2.6.1 tarball, but it is checked in. -- components: Build messages: 77067 nosy: doko priority: deferred blocker severity: normal status: open title: Doc/tools/sphinxext not included in the 2.6