-
-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
About IDLE: direct discussion to DPO #122482
Labels
Comments
terryjreedy
added a commit
that referenced
this issue
Jul 30, 2024
Currently, idle-dev@python.org and idle-dev mailing list serve to collect spam (90+%). Change About IDLE to direct discussions to discuss.python.org. Users are already doing so.
This was referenced Jul 30, 2024
terryjreedy
added a commit
that referenced
this issue
Jul 30, 2024
#122486) GH-122482: Make About IDLE direct discussion to DPO (GH-122483) Currently, idle-dev@python.org and idle-dev mailing list serve to collect spam (90+%). Change About IDLE to direct discussions to discuss.python.org. Users are already doing so. (cherry picked from commit 29c04df) Co-authored-by: Terry Jan Reedy <tjreedy@udel.edu>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

Change About IDLE to direct discussions to discuss.python.org. Users are already doing so.
Currently, idle-dev@python.org and idle-dev mailing list serve, 90+%, to collect spam. The few user messages per year are off topic requests for help, mostly not about IDLE. The email should be disabled and the mailing list archived, but these actions are not part of this tracker.
Linked PRs
The text was updated successfully, but these errors were encountered: