➜

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, brett.cannon, doko, ncoghlan, petr.viktorin
Date 2017-02-10.17:53:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <20170210125252.2b27cfa5@presto.wooz.org>
In-reply-to <1486748774.45.0.579083173514.issue29514@psf.upfronthosting.co.za>
Content 
On Feb 10, 2017, at 05:46 PM, Nick Coghlan wrote:

>Note that Fedora doesn't even rebuild all the extension modules when bumping
>CPython to a new maintenance release, let alone rebuilding and re-releasing
>all the pure Python ones. (RPM supports doing that just fine, but it would
>mean shipping thousands of updated binary artifacts instead of just one - the
>new CPython maintenance release)

Debian/Ubuntu doesn't rebuild extension modules either.  We don't ship .pyc
files in binary packages, but instead build them at install time on the user's
machine.
History
Date User Action Args
2017-02-10 17:53:00barrysetrecipients: + barry, brett.cannon, doko, ncoghlan, petr.viktorin
2017-02-10 17:53:00barrylinkissue29514 messages
2017-02-10 17:53:00barrycreate