Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork33.7k
Change__future__ docs description to avoid confusion with concurrency futures#92760
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
carljm left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Looks like an improvement to me.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Co-authored-by: Carl Meyer <carl@oddbird.net>
carljm left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
LGTM!
arhadthedev commentedJul 18, 2022
JelleZijlstra commentedJul 23, 2022
I don't find the current wording unclear, and the proposed new wording is so long that it will make the page title spill into multiple lines on many screens. If another core dev has a different opinion, I won't object to merging this though. |
arhadthedev commentedJul 24, 2022 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
@JelleZijlstra Will Edit: for comparison: |
arhadthedev commentedJul 30, 2022
Applied the shorter wording described above. |
__future__ docs description from concurrency futures__future__ docs description to avoid confusion with concurrency futuresarhadthedev commentedOct 6, 2022
Ping. |
JelleZijlstra commentedOct 6, 2022
Sorry, I still don't see a reason for change here. I'm leaving this open in case another core dev thinks there's room for improvement, but I'm not planning to merge anything. |
Uh oh!
There was an error while loading.Please reload this page.
Currently,the library index page describes
__future__as:However, it creates confusion with futures from the concurrency domain. So this PR changes the description to:
Edit: replaced with a shorter wording: