Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #101115
| From | Chris Angelico <rosuav@gmail.com> |
|---|---|
| Newsgroups | comp.lang.python |
| Subject | Re: We will be moving to GitHub |
| Date | 2016-01-02 07:09 +1100 |
| Message-ID | <mailman.146.1451678991.11925.python-list@python.org> (permalink) |
| References | <n66kmg$ig$1@ger.gmane.org> <CAPTjJmq1Qevy7h4pqrQPobLRO-_ooLrXsZhK9Z9YCKPyFnxKsQ@mail.gmail.com> <CAKJDb-MFM6i+MMZXcPkV6x-rFnKr9Yxt4f3ne1dF3dk_SkoFpw@mail.gmail.com> |
On Sat, Jan 2, 2016 at 6:58 AM, Zachary Ware <zachary.ware+pylist@gmail.com> wrote: >> It's not entirely clear whether that message is an acceptance of PEP 481 > or not. > > I've lost track of the pep numbers, but Brett's decision is final; the > canonical CPython repository will be moving to GitHub in the near future. > Note that we will *not* be using the GitHub issue tracker or wiki, just the > hosting and review/pull request system. There are still several details to > be worked out, though. Okay, so that means it broadly is an acceptance of PEP 481. Hopefully someone who's been involved in the discussions can check over the PEP text and adjust as necessary to make it accurate to what's going to happen. On Sat, Jan 2, 2016 at 7:03 AM, <paul.hermeneutic@gmail.com> wrote: > Mark, it is good to know that a decision has been made so that we can move > forward. > > Is there a summary document that discusses the options examined and why > others did not meet the requirements? I am -NOT- trying to dredge up > arguments about the choice. I am guessing that there have been some. > > If this fact-based decision was based solely on the fact that the BDFL > prefers GitHub, please just say so. It is clear that git is a capable tool. That's what the PEP is for. Here's the link: https://www.python.org/dev/peps/pep-0481/ Yes, git is a capable tool. But so is Mercurial, and the arguments weren't primarily based on differences in functionality (which are pretty minor). It's mainly about the network effect. ChrisA
Back to comp.lang.python | Previous | Next — Next in thread | Find similar | Unroll thread
Re: We will be moving to GitHub Chris Angelico <rosuav@gmail.com> - 2016-01-02 07:09 +1100
Re: We will be moving to GitHub Steven D'Aprano <steve@pearwood.info> - 2016-01-02 17:43 +1100
Re: We will be moving to GitHub Chris Angelico <rosuav@gmail.com> - 2016-01-02 18:12 +1100
Re: We will be moving to GitHub Marko Rauhamaa <marko@pacujo.net> - 2016-01-02 11:48 +0200
Re: We will be moving to GitHub Chris Angelico <rosuav@gmail.com> - 2016-01-02 21:29 +1100
Re: We will be moving to GitHub Marko Rauhamaa <marko@pacujo.net> - 2016-01-02 13:22 +0200
Re: We will be moving to GitHub Chris Angelico <rosuav@gmail.com> - 2016-01-02 22:40 +1100
Re: We will be moving to GitHub Marko Rauhamaa <marko@pacujo.net> - 2016-01-02 16:26 +0200
Re: We will be moving to GitHub Chris Angelico <rosuav@gmail.com> - 2016-01-03 01:38 +1100
Re: We will be moving to GitHub Marko Rauhamaa <marko@pacujo.net> - 2016-01-02 16:52 +0200
Re: We will be moving to GitHub Chris Angelico <rosuav@gmail.com> - 2016-01-03 02:12 +1100
Re: We will be moving to GitHub Marko Rauhamaa <marko@pacujo.net> - 2016-01-03 02:33 +0200
Re: We will be moving to GitHub Chris Angelico <rosuav@gmail.com> - 2016-01-03 11:42 +1100
Re: We will be moving to GitHub Marko Rauhamaa <marko@pacujo.net> - 2016-01-03 03:14 +0200
Re: We will be moving to GitHub m <mvoicem@gmail.com> - 2016-01-04 11:13 +0100
Re: We will be moving to GitHub Marko Rauhamaa <marko@pacujo.net> - 2016-01-04 13:28 +0200
Re: We will be moving to GitHub Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2016-01-04 23:53 +0100
Re: We will be moving to GitHub Tim Chase <python.list@tim.thechases.com> - 2016-01-02 06:58 -0600
Re: We will be moving to GitHub Michael Torrie <torriem@gmail.com> - 2016-01-02 20:24 -0700
csiph-web