@Haypo @1st1 @asvetlov

While this repo is still in sync with the 3.5 branch of the cpython Hg repo, the default branch (soon to become the 3.6b1 release branch) is deviating more and more, e.g. @Haypo added something to the 3.6 branch only about logging and @1st1 added support there for async generators (PEP 525).

I think it's becoming more and more complex to make changes in this "upstream" repo, then copy them to the 3.5 branch using the update_stdlib.sh script, and from there merge into the 3.6 branch. With the release branch it's going to be even more complicated.

Advantages of this repo are that it has its own issue tracker, which I like more than bugs.python.org, and I like GitHub PRs more than the bugs.python.org patch mechanism; but the merge-back workflow is really tedious.

I propose to do the following once the 3.6b1 release branch exists (or right now):

• keep the issue tracker here for now, until we can decide what to do with it (maybe use it as a kind of help forum?)
• migrate remaining PRs to bugs.python.org, marking them as 3.5, 3.6 or 3.7, or close them as won't fix
• let's not make any more changes here and let's not release any more asyncio versions to PyPI; 3.4.3 will have been the final one

Thoughts?