New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
3.4 cherry-pick: multiple changesets for asyncio #64847
Comments
I consider that it's not too late to include these changes to Python 3.4 final because asyncio module is new in Python 3.4. Very few people outside asyncio developers are testing asyncio, so it's not surprising to see these changes only recently. asyncio received a lot of love recently, and it was even more improved. Most recent to oldest. changeset: 89179:95de14f53cf5 changeset: 89176:6e04027ed53e changeset: 89175:920304e1f36b changeset: 89157:2ba583191550 changeset: 89147:15a6be05e970 changeset: 89146:f729e9ee5dfc changeset: 89145:3ba4742a6fde Changesets related to debug can be ignored (03cb6ddc7040, 9c1840e8d643, a631b01d1715, 360976a6d8b9). |
I think we should just ask Larry to merge all commits for asyncio in 3.4. |
Right, that has been my understanding. Larry has said he'd give asyncio a On Sunday, February 16, 2014, Yury Selivanov <report@bugs.python.org> wrote:
|
Then again Larry might appreciate a full list of what to cherrypick. On Sunday, February 16, 2014, Guido van Rossum <report@bugs.python.org>
|
changeset: 89231:ea4c74cc4da5 |
Yeah, I considered getting fussy about "you didn't follow instructions". But this actually is better for me, as it means I can apply the patches in chronological order. Like Guido said, I intend to be permissive when it comes to asyncio for 3.4.0. I'm assuming that these patches don't touch anything outside asyncio (implementation and doc). If that's all they touch, then yeah I'll accept them. If any of them touch other files then we may need to discuss it. |
changeset: 89237:b3987d758e49 |
You may also cherry-pick d548829765cd and b2498889ad8d, skip tests on OpenBSD. And: changeset: 89246:6b09a2cf1744 |
New changeset 79e5bb0d9b8e by Victor Stinner in branch 'default': |
Two new cherry-picks: changeset: 89253:d6c7d1f18915 changeset: 89252:c27728212fcd |
This one needs to be CP'ed together with Yuri's UNIX sockets one. changeset: 89257:f81106f36656 |
changeset: 89262:7c1de1ebb894 |
http://hg.python.org/cpython/rev/72dba0d11235 |
changeset: 89264:2406566d2c04 Mention if the error was caused by a read or a write, and be more specific on |
changeset: 89265:089ce5ddc147 |
Minor stuff: changeset: 89267:2b0e65df8821 Thanks to Vajrasky Kok for discovering some of them. |
changeset: 89268:2e8a142dbccc |
2e8a142dbccc just missed today's cherry-picking session. I'll add it tomorrow. |
TBH I don't think typos or PEP-8 cleanups ought to be CP'ed... On Tuesday, February 18, 2014, Larry Hastings <report@bugs.python.org>
|
Perhaps, but if they request cherry-picking for revisions after 2e8a142dbccc, skipping 2e8a142dbccc will make the cherry-picking a lot harder. And I bet I haven't seen the last request for cherry-picking asyncio changes for 3.4.0. |
Actually I am trying to quell the tide. :-). But nobody sent me a review On Tuesday, February 18, 2014, Larry Hastings <report@bugs.python.org>
|
Yes, it may make it harder, it's probably better to merge it (no functional changes in it). I now think that PEP-8 commit was a bit too much, I clearly could do that after 3.4. Sorry, Larry, no more non-urgent commits/requests here. |
For what it's worth, Lib/asyncio/* are all exactly the same between default and the tarball I published this evening. (Minus Yury's cleanup patch of course.) |
Thanks for checking! On Tuesday, February 18, 2014, Larry Hastings <report@bugs.python.org>
|
changeset: 89269:9cfb3d1cf0d1 |
changeset: 89270:186f6f56f4bc |
changeset: 89288:dbf13a7d3987 |
changeset: 89283:07cdce316b1d changeset: 89282:e6016fffc894 On Mac OS X Tiger (and older), getsockname() returns a zero-length address for |
changeset: 89290:549f451aa4c3 |
Some documentation. changeset: 89291:58fd64e55b29 |
*sigh* okay. Including 2e8a142dbccc from last night, that's eight new revisions to cherry-pick in one day. I really hope this is slowing down. |
It is slowing down. I think we now only have some documentation updates left. |
What about this one? http://bugs.python.org/issue20668 (Remove dependency on tests.txt when running test_asyncio suite) It has been lgtm-ed by Guido and asked by him to be added to this issue. |
That one is not critical. It can go in sfter 3.4 is released. On Wednesday, February 19, 2014, Vajrasky Kok <report@bugs.python.org>
|
There are a few diffs on the asyncio files right now. I went back and looked and discovered a whole bunch of asyncio revisions post-rc1 that you haven't asked to be cherry-picked yet: 20dc8d6430eb Should these be cherry-picked too? (I wonder why there were no diffs on the files yesterday. Maybe I screwed up the diff itself?) |
Also 6b850722849e |
We discuss with Guido and Yury to only include "critical" changes, so in short: yes, all commits related to asyncio should be cherrry-picked into RC2. It should also be easier for you to include all changes, to avoid conflicts. And the code should be the same in default and RC2 for asyncio. |
changeset: 89300:c3abdf016b18 Use self._loop instead of self._transport._loop, because transport._loop is set |
changeset: 89302:3e19634b396f changeset: 89301:c412243b9d61 The "exc" variable was not defined, pass a BrokenPipeError exception instead. |
Sorry, I found new bugs /o\ You may skip 3e19634b396f if the last commit to cherry-pick, it's just cleanup. |
(Ooops, "if *it is* the last commit") |
changeset: 89303:d1f0ec5a9317 |
changeset: 89304:03b14690a9be |
NEWS updates: changeset: 89305:db749f0c6567 |
Again, documentation update. changeset: 89306:1c35d3114ea1 |
changeset: 89307:96e078663083 |
I finished the second preview of rc2 just before you posted 96e078663083. That'll go in the third preview. Also, I found another revision you forgot about (something about improving debug info). With that, and the other revisions I mentioned, asyncio in the rc2 preview now has no diffs against the equivalent default revision. rc2 cherry-picks 58 revisions. Thank god I spent a couple days automating the process. |
Hopefully, the last one from me ;) Again, some documentation updates. Thank you, Larry, for accepting these last minute fixes. changeset: 89308:cd23d0c3f850 |
Last bit of documentation from me. I, personally, don't have any more changes in mind, so this one is probably the last from me on the asyncio front in this thread. changeset: 89312:ec3a70ef759d |
I just put the third preview up. There are no diffs between that asyncio and the one in default. Is this torrent coming to a close? We really should keep the changes from rc2 to final to a bare minimum. |
I agree. We may improve the documentation, but such commits doesn't need to be cherry-picked. Many people read the documentation online (docs.python.org). |
Can I close this issue now? |
Yes. If something really critical appears, a new issue can be opened. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: