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
Update IDLE's credits #83270
Comments
|
The "Credits" document in the "About" dialog could use some updating. It fails to mention Saimadhav Heblikar's important work during GSoC 2014 as well as Terry J. Reedy's tireless work over the past few years which has helped keep IDLE in working order and the codebase in reasonable shape given its age. |
|
I have thought about everything from deleting the file to a detailed update. If we keep it, anything would be an improvement. Perhap something in the middle, starting in 2013. I just decided I don't need be be responsible for anything earlier, even this I actually started in Fall 2010. 2013 Roger Serwy (and perhaps GSOC Phil Webster -- I need to look more at News log.) Can you make a suggested addition? |
|
Looks pretty good to me. I've been working on IDLE since... 2003/2004, beginning with a private fork of IDLE-fork. I began actually contributing to the main CPython version of IDLE in 2005. |
Co-authored-by: Terry Jan Reedy <tjreedy@udel.edu> (cherry picked from commit 698fa8b) Co-authored-by: Erlend Egeberg Aasland <erlend.aasland@protonmail.com>
Co-authored-by: Terry Jan Reedy <tjreedy@udel.edu> (cherry picked from commit 698fa8b) Co-authored-by: Erlend Egeberg Aasland <erlend.aasland@protonmail.com>
Co-authored-by: Terry Jan Reedy <tjreedy@udel.edu>
|
Erlend's PR includes info above and add a generic 'look at logs' comment. If/when I or someone decides someone else should be added, after looking through logs, a no-issue, no-blurb PR should be fine. |
+1 Let's close this when the backport is merged. UPDATE: I linked the backport PR; this issue should close automatically when Pablo unlocks the 3.10 branch and that PR is merged. |
Well, it didn't. I don't know why. |
|
The bots are not perfect. This is why the issue should not be closed when the first PR is merged to main. Anyway, thanks for the PR. |
taleinat commentedDec 18, 2019
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: