[issue30422] Add roadmap.txt section to idlelib
18z added the comment: Hi Terry, Louie and Cheryl I would like to work with you guys. :) However, I still need some time to study the codes. Now I am focusing on reading unit tests. By reading the tests, I can know how the code works and further to write tests that are necessary but yet to write. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30422> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue30422] Add roadmap.txt section to idlelib
18z added the comment: I strongly agree with the idea of writing documents that describe a bit of history to help orient new contributors to IDLE as to where the involved contributors see it going. As a new comer, before I started to trace the codes of idlelib. A question bothers me all the time. "Why do we need idlelib since there are so many brilliant IDEs out there?" And I'm not sure whether should I keep reading the codes or not. So, I want to say Thank you to Terry. Your draft helped me. I'm really happy to see this question had been discussed in summer 2010. And the result is to modernize idlelib. However, I have a suggestion :) Although the result of the discussion is to modernize. I suggest to add few lines to describe the reasons why this decision had been made. And references (if possible) are needed to provide since some readers might want to see the original discussion. How do you think? :) -- nosy: +KunYu Chen ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30422> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
