Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #8207

Re: Python Policy: Things to consider for Stretch

Show all headers | View raw

On Tuesday, February 02, 2016 06:44:57 AM Ben Finney wrote:
> Ben Finney <ben+debian@benfinney.id.au> writes:
> > * 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.
> > 
> > I'm maintaining a Bazaar branch for this, feel free to get it::
> >     $ mkdir python.benfinney/ && cd python.benfinney/
> >     $ bzr branch --bind
> >     http://vcs.whitetree.org/bzr/public/debian/python/python-defaults-deb
> >     ian/devel/
> Ben Finney <ben+debian@benfinney.id.au> writes:
> > Thank you, Scott! I'll proceed with the semantic changes that promote
> > Python 3 to the primary position.
> 
> Those changes are now in the above branch. The summary of changes from
> the commit messages:
> 
>     $ bzr log --log-format line --revision ancestor:..
>     430: Ben Finney 2016-02-02 Re-phrase version distinctions to make Python
> 3 primary. 429: Ben Finney 2016-02-01 When only Python 2 is specified, just
> use literal “2” major version. 428: Ben Finney 2016-02-01 Use Python 3
> examples where appropriate. 427: Ben Finney 2016-01-31 Refine some grammar
> and punctuation. 426: Ben Finney 2016-01-31 Distinguish “Python” the
> unversioned system versus “Python 2”. 425: Ben Finney 2016-01-30 [merge]
> Merge from ‘python-defaults-debian’ mainline.
> 
> Also attached to this message as a Bazaar patch bundle.

I've merged these changes.  I have a little bit of adjustment I want to do on 
top of it, but this helps a lot.  Thanks,

Scott K

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Python Policy: Things to consider for Stretch Scott Kitterman <debian@kitterman.com> - 2016-01-21 16:50 +0100
  Re: Python Policy: Things to consider for Stretch Barry Warsaw <barry@debian.org> - 2016-01-23 00:00 +0100
    Re: Python Policy: Things to consider for Stretch Scott Kitterman <debian@kitterman.com> - 2016-01-23 09:40 +0100
      Re: Python Policy: Things to consider for Stretch Barry Warsaw <barry@debian.org> - 2016-01-24 03:00 +0100
        Re: Python Policy: Things to consider for Stretch Scott Kitterman <debian@kitterman.com> - 2016-01-24 04:10 +0100
          Re: Python Policy: Things to consider for Stretch Ben Finney <ben+debian@benfinney.id.au> - 2016-01-24 06:40 +0100
            Re: Python Policy: Things to consider for Stretch Scott Kitterman <debian@kitterman.com> - 2016-01-24 07:10 +0100
            Re: Python Policy: Things to consider for Stretch Barry Warsaw <barry@debian.org> - 2016-01-24 19:10 +0100
            Re: Python Policy: Things to consider for Stretch Ben Finney <ben+debian@benfinney.id.au> - 2016-01-26 07:00 +0100
            Re: Python Policy: Things to consider for Stretch Dmitry Shachnev <mitya57@debian.org> - 2016-01-26 18:00 +0100
              Re: Python Policy: Things to consider for Stretch Ben Finney <ben+debian@benfinney.id.au> - 2016-01-27 04:40 +0100
                Re: Python Policy: Things to consider for Stretch Scott Kitterman <debian@kitterman.com> - 2016-01-27 05:20 +0100
                Re: Python Policy: Things to consider for Stretch Ben Finney <ben+debian@benfinney.id.au> - 2016-01-27 10:50 +0100
            Re: Python Policy: Things to consider for Stretch Scott Kitterman <debian@kitterman.com> - 2016-01-29 23:30 +0100
              Re: Python Policy: Things to consider for Stretch Ben Finney <ben+debian@benfinney.id.au> - 2016-01-30 00:10 +0100
    Re: Python Policy: Things to consider for Stretch Paul Wise <pabs@debian.org> - 2016-02-16 01:10 +0100
      Re: Python Policy: Things to consider for Stretch Barry Warsaw <barry@debian.org> - 2016-02-16 01:50 +0100
        Re: Python Policy: Things to consider for Stretch Barry Warsaw <barry@debian.org> - 2016-02-16 02:00 +0100
        Re: Python Policy: Things to consider for Stretch Paul Wise <pabs@debian.org> - 2016-02-16 02:00 +0100
          Re: Python Policy: Things to consider for Stretch Barry Warsaw <barry@debian.org> - 2016-02-16 02:20 +0100
  Re: Python Policy: Things to consider for Stretch Ben Finney <ben+debian@benfinney.id.au> - 2016-01-24 06:50 +0100
    Re: Python Policy: Things to consider for Stretch Ben Finney <ben+debian@benfinney.id.au> - 2016-01-24 07:00 +0100
      Re: Python Policy: Things to consider for Stretch Scott Kitterman <debian@kitterman.com> - 2016-01-24 07:20 +0100
        Re: Python Policy: Things to consider for Stretch Ben Finney <ben+debian@benfinney.id.au> - 2016-01-25 06:00 +0100
          Re: Python Policy: Things to consider for Stretch Scott Kitterman <debian@kitterman.com> - 2016-01-25 06:30 +0100
    Re: Python Policy: Things to consider for Stretch Scott Kitterman <debian@kitterman.com> - 2016-01-24 07:10 +0100
  Re: Python Policy: Things to consider for Stretch Scott Kitterman <debian@kitterman.com> - 2016-02-15 23:30 +0100
    Re: Python Policy: Things to consider for Stretch Ben Finney <ben+debian@benfinney.id.au> - 2016-02-16 03:50 +0100

csiph-web