List view

• PEP 484 finalization

  For issues that must be resolved before we can consider [PEP 484](https://www.python.org/dev/peps/pep-0484/) final (i.e. no longer provisional). This doesn't mean that we can't add more features, but they'll be 3.6 only.

  No due date

  •7/7 issues closed
  100% complete0 open7 closed

• 3.5.3

  Whatever we want to make it into Python 3.5.3. (These things should also go into 3.6.0.) There's no due date since [PEP 478](https://www.python.org/dev/peps/pep-0478/) doesn't have a date for 3.5.3 (most likely it's going to be December 2016).

  No due date

  •5/5 issues closed
  100% complete0 open5 closed

• 3.5.2 stretch

  Stretch goals for 3.5.2.

  No due date

  •1/1 issues closed
  100% complete0 open1 closed

• 3.5.2

  Things I want to address before CPython 3.5.2 is released. The schedule is published here: https://www.python.org/dev/peps/pep-0478/ RC1 goes out Sunday, June 12 (2016) so I want this done by Friday June 10 (on the heels of PyCon!)

  Due by June 10, 2016

  •16/16 issues closed
  100% complete0 open16 closed