This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author barry
Recipients barry, christian.heimes, doko
Date 2008-12-05.21:17:27
SpamBayes Score 5.828315e-05
Marked as misclassified No
Message-id <1228511848.62.0.252956310955.issue4552@psf.upfronthosting.co.za>
In-reply-to
Content
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 include sphinxext for better or
worse, because this directory is removed by the release.py script. 
However, the removal of it was not added to release.py until after the
3.0 tarballs were made (the 2.6.1 tarballs do not include sphinxext).

Tell me which it should be and I'll fix release.py
History
Date User Action Args
2008-12-05 21:17:28barrysetrecipients: + barry, doko, christian.heimes
2008-12-05 21:17:28barrysetmessageid: <1228511848.62.0.252956310955.issue4552@psf.upfronthosting.co.za>
2008-12-05 21:17:28barrylinkissue4552 messages
2008-12-05 21:17:27barrycreate