Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod From: Ben Finney Newsgroups: linux.debian.maint.python Subject: Re: Python Policy: Things to consider for Stretch Date: Tue, 26 Jan 2016 07:00:02 +0100 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Tue Jan 26 05:56:20 2016 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.68 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, HEADER_FROM_DIFFERENT_DOMAINS=0.001, LDO_WHITELIST=-5, MURPHY_DRUGS_REL8=0.02, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate:hard: -6.1 X-Injected-Via-Gmane: http://gmane.org/ Lines: 31 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Gmane-NNTP-Posting-Host: jigong.madmonks.org X-Public-Key-ID: 0xAC128405 X-Public-Key-Fingerprint: 517C F14B B2F3 98B0 CB35 4855 B8B2 4C06 AC12 8405 X-Public-Key-URL: http://www.benfinney.id.au/contact/bfinney-pubkey.asc X-Post-From: Ben Finney User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) Cancel-Lock: sha1:IJlX2l8CTd8BZ6uxb/CVHgn4ats= X-Mailing-List: archive/latest/13487 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/85zivsj34h.fsf@benfinney.id.au Approved: robomod@news.nic.it Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Tue, 26 Jan 2016 16:55:58 +1100 X-Original-Message-ID: <85zivsj34h.fsf@benfinney.id.au> X-Original-References: <1705132.RfqMtW1P2v@kitterma-e6430> <1788942.Gcc8N3eft8@kitterma-e6430> <20160123205049.09efb0d9@subdivisions.wooz.org> <1597133.3JM6ycrHqJ@kitterma-e6430> <85r3h7k0cc.fsf@benfinney.id.au> <854me0ki50.fsf@benfinney.id.au> X-Original-X-Complaints-To: usenet@ger.gmane.org Xref: csiph.com linux.debian.maint.python:8163 Ben Finney writes: > I'm planning to provide changes in two bundles: > > * Go through the whole document and tidy it up for consistency, source > style, markup, and language style. This should not change the meaning > of anything, but will change the wording of numerous passages. > > My proposal for that is attached here as a Bazaar change bundle. > > * Address all the language around Python 2 versus Python 3 versus Python > general, and re-order or re-word to focus *primarily* on Python 3, > with Python 2 treated as the still-supported legacy system. > > Once these non-semantic changes are accepted I will begin work on the > second stage of semantic changes. That last sentence isn't very clear. What I intended to imply is: The first stage is done and all its changes are in the branch, the second stage I haven't yet started. The set of revision in the “r411–r424” patch bundle is all intended to be non-semantic changes, and once they're accepted I'll begin on the second, semantic-changing, stage of work. -- \ “I don't accept the currently fashionable assertion that any | `\ view is automatically as worthy of respect as any equal and | _o__) opposite view.” —Douglas Adams | Ben Finney