In April 2013 we challenged students to not spend their summer idle around the swimming pool but rather spend their time on IDLE and make a difference. IDLE is Python’s Integrated Development Environment (IDE) that is shipped with each Python release (http://en.wikipedia.org/wiki/IDLE_(Python)). Since IDLE ships with Python it is often the first IDE a new Python programmer uses. The Python development community wants to make IDLE an awesome experience especially for people that are learning Python. Despite the fact that IDLE originally shipped in 1998 it had no unit test cases, making it difficult to confidently update the code and ship new versions. For this Google Summer of Code project our students Jayakrishnan Rajagopalasarma (http://123works.blogspot.com/search/label/GSoC%202013) and Phil Webster (http://weblog.philwebster.net/tag/gsoc/) had to not only create the unit tests but assist with design of the unit test framework (http://bugs.python.org/issue15392). By the end of the summer of 2013 Phil and Jayakrishnan have worked on five patches that have been committed to the CPython open source project. In addition the team has started work on an additional five issues (at bugs.python.org) but have not completed them yet. Jayakrishnan explored an idea to add automatic PEP8 checking to IDLE http://bugs.python.org/issue18704. Our hope is that both JayKrish and Phil continue to contribute to Python even now that GSoC is complete. The team wishes to thank Google and the Python Software Foundation for this opportunity to contribute to Python. Thanks to all the Python Core Developers that helped review and commit issues for the students. Special thanks goes to Terry Reedy who provided outstanding feedback on issues and performed all of the student’s commits. Finally thanks to Terri Oda for being a great GSoC administrator for the Python Software Foundation and helping by assigning an awesome co-mentor J.H. Hawley. The complete list of closed issues is below: http://bugs.python.org/issue18279 http://bugs.python.org/issue18189 http://bugs.python.org/issue18425 http://bugs.python.org/issue18226 http://bugs.python.org/issue18489 The complete list of started issues is below: http://bugs.python.org/issue18292 http://bugs.python.org/issue18910 http://bugs.python.org/issue18409 http://bugs.python.org/issue18410 http://bugs.python.org/issue18592