Skip to content

I'm writing a quick cheat-sheet / FAQ for people interested in contributing to Python IDLE development.

Notifications You must be signed in to change notification settings

asweigart/idle-dev-faq

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

8 Commits
 
 
 
 

Repository files navigation

IDLE-dev FAQ

This document came about from a Feb 2014 idle-dev mailing list thread about the need for a dev guide specifically for IDLE development.

###Getting Started

  1. Read the general Python Developer Guide.
  2. Fill out the PSF's Contributor Agreement
  3. Read PEP 434, which explains how IDLE development differs from Python development (re: backporting).
  4. Familiarize yourself with the idle-dev mailing list archive and read the last few years of discussion. (Don't worry, this is a relatively low volume list.)
  5. Check out the open issues on the Python bug tracker, as well as the closed issues for a sense of history.
  6. IDLE uses the Tkinter GUI toolkit in Python's standard library. Check out the following Tkinter tutorial resources:
    1. YouTube tutorials by TheReimber
    2. Book: Modern Tkinter for Busy Python Developers
    3. Demo code of Tkinter widgets: A_tour_of_Tkinter_widgets
  7. Check out the IDLE source code guide

A quick cheat-sheet / FAQ for people interested in contributing to Python IDLE development.

###Q: How do I get the source code of IDLE?

Use Mercurial and clone the repo at https://hg.python.org/cpython.

$ hg clone https://hg.python.org/cpython

###Q: How do I get started contributing to IDLE?

  • Look at the current bugs in the issue tracker.
  • Fix one
  • Submit a patch. Note patches are always tied to issues in the tracker.

###Q: Where can I check-out the current state of IDLE development?

TODO (currently the mailing list)

###Q: Where can I see current issues?

On the issue tracker. Here is a search for IDLE bugs

###Q: Who do I submit patches to?

Submit patches on the https://bugs.python.org/ bug/issue tracker. Terry Reedy is currently responsible for IDLE issues, but anyone who is on the nosy list of followers for the issue will get a notification if a patch is submitted.

###Q: How can I signal that I have a patch for someone to look at?

Upload the patch to the related issue on the issue tracker. All people on the nosy list will get notified.

Mark keyword 'patch' so the issue appears on this search

Trimmed and possibly not correct (I do not understand the %40s, nor how much the order matters): http://bugs.python.org/issue?components=6&keywords=2&status=1&%40columns=id&%40columns=activity&%40columns=title&%40group=priority&%40sort=activity&%40action=search

###Q: Where can I discuss IDLE development?

The idle-dev mailing list. Discussions on the mailing list are friendly and civil, and users are expected to abide by the PSF Code of Conduct.

###Q: Are there other projects based off of IDLE?

IdleX extends the functionality of IDLE with new features. VIDLE for VPython is also derived from the IDLE codebase.

###Q: How do I run the IDLE tests?

TODO

About

I'm writing a quick cheat-sheet / FAQ for people interested in contributing to Python IDLE development.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published