-
-
Notifications
You must be signed in to change notification settings - Fork 30.9k
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
IDLE - document github project issue topics #95491
Comments
Each GitHub Project has an associated README file that can be edited through the project's settings. I suggest to use this feature to document the Topic meta field, and also update it with more instructions for how to triage IDLE issues. After this is done, we can close this issue as resolved. Suggested list of tasks:
|
Do you have anything to add now to the project settings? Otherwise, I'd like to close this after the PR is merged (after 3.11 is unlocked). |
Not at the moment. The project settings look good to me. If we need to update them futher, we can just do it; there is no need for an issue. |
(cherry picked from commit 63140b4) Co-authored-by: Terry Jan Reedy <tjreedy@udel.edu>
(cherry picked from commit 63140b4) Co-authored-by: Terry Jan Reedy <tjreedy@udel.edu>
The primary field for the IDLE issues project in the github cpython repository is 'Topic'. I will add a listing of topics and explanation of each to idlelib/README.txt, which is accessible from IDLE on the
Help => About IDLE
dialog.This will replace my private 'idle-issues.txt', which has been absolutely essential for me working with IDLE. I once uploaded a snapshot to #74607. I considered adding a periodically updated snapshot to idlelib but never decided that the benefit would justify the extra work. The IDLE issues project should be a net plus for me and be available to anyone else working with IDLE issues.
Many of the topics comprise issues related to groups of menu items indicated by separators on each drop-down menu. #95471 added a separator needed for this purpose.
The text was updated successfully, but these errors were encountered: