[Python-Dev] quick GitHub transition update (was: File system path PEP, 3rd draft) (original) (raw)
Brett Cannon brett at python.org
Fri May 13 16:31:33 EDT 2016
- Previous message (by thread): [Python-Dev] File system path PEP, 3rd draft
- Next message (by thread): [Python-Dev] File system path PEP, 3rd draft
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, 13 May 2016 at 12:56 Guido van Rossum <guido at python.org> wrote:
Can't wait until the peps repo is on GitHub!
With devinabox now moved over to GitHub, the peps repo is next on the list to move (and the devguide after that). I don't know if I'm going to be able to make the migration happen before PyCon US, but my goal is to have it either done before the language summit or have every little step lined up by the end of the sprints and then finished up the week following.
I got one of the coveted 20 minute timeslots at the language summit to give an update on everything and soliciting feedback on what needs to be in place to migrate the cpython repo so I can have a clear idea of what work is left to do.
If people want to prep for this discussion (which will be reported back here so everyone can participate in the end), think about what you absolutely must have in place to make working with GitHub for the cpython repo work for you. I don't want any emails on this now (I've got 3 PEPs at various stages plus travel between now and PyCon at this point so I'm busy enough as it is, so any emails discussing this now will be ignored as I don't have the mental bandwidth for that discussion prior to PyCon US). Please just reflect on the required parts of your workflow over the next 2 weeks to know how much work you are going to ask of me as minimum requirements to make the GitHub migration of the cpython repo happen (i.e. I don't care about "nice to have", only about "without this I flat-out won't contribute to Python on GitHub").
On Fri, May 13, 2016 at 12:24 PM, Brett Cannon <brett at python.org> wrote:
On Fri, 13 May 2016 at 12:08 Barry Warsaw <barry at python.org> wrote: On May 13, 2016, at 06:37 PM, Brett Cannon wrote: >PEP: NNN >Title: Adding a file system path protocol >Version: RevisionRevisionRevision >Last-Modified: DateDateDate >Author: Brett Cannon <brett at python.org>, > Koos Zevenhoven <k7hoven at gmail.com> >Status: Draft >Type: Standards Track >Content-Type: text/x-rst >Created: 11-May-2016 >Post-History: 11-May-2016, > 12-May-2016, > 13-May-2016 I think this is far enough along that you should self-assign a PEP number and check it into the official repo. Paraphrasing someone from Twitter yesterday, I'm just going to work on GitHub until I absolutely have to check into hg, m'kay? ;) -Brett
Python-Dev mailing list Python-Dev at python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/guido%40python.org
-- --Guido van Rossum (python.org/~guido) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20160513/621daf52/attachment.html>
- Previous message (by thread): [Python-Dev] File system path PEP, 3rd draft
- Next message (by thread): [Python-Dev] File system path PEP, 3rd draft
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]