[issue4519] .pyc files included in 2.6 and 3.0 release tarballs

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: Actually, it turns out that the doc build process leaves a few more pyc turds now. I've updated release.py to remove them, though the script really should complain loudly if it ever finds pycs in the distribution. That's for next time. For

[issue4519] .pyc files included in 2.6 and 3.0 release tarballs

Christian Heimes <[EMAIL PROTECTED]> added the comment: Ups ... I didn't noticed it, too. -- nosy: +christian.heimes stage: -> needs patch type: -> resource usage ___ Python tracker <[EMAIL PROTECTED]>

[issue4519] .pyc files included in 2.6 and 3.0 release tarballs

STINNER Victor <[EMAIL PROTECTED]> added the comment: Write a clean script (or fix the existing script) and reuse the script for each release ;-) -- nosy: +haypo ___ Python tracker <[EMAIL PROTECTED]> __

[issue4519] .pyc files included in 2.6 and 3.0 release tarballs

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: I thought we had fixed that :( -- priority: -> release blocker ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue4519] .pyc files included in 2.6 and 3.0 release tarballs

New submission from Matthias Klose <[EMAIL PROTECTED]>: Python-2.6/Doc/tools/sphinxext/patchlevel.pyc Python-2.6/Doc/tools/sphinxext/pyspecific.pyc Python-2.6/Doc/tools/roman.pyc same for 3.0 -- assignee: barry components: Build messages: 76875 nosy: barry, doko severity: normal status: