There is a need for a proper design in commencing idle unittest framework, Two suggestions in issue 15392 <http://bugs.python.org/issue15392#> are create test_idle directory in test sub directory (Lib/test/test_idle) or to create test directory inside idlelib. (Lib/idlelib/test)
On that discussion these two approaches were proposed as follows, David Murray said, "best practice would be to have all tests be in the 'test' sub directory. I moved email/test into test/test_email, and I prefer having it there" Terry J. Reedy said, "I strongly prefer idlelib/test since it will make developing **much** easier for me on Windows. Also, it would be part of the optional install of idlelib, as tkinter/test is for tkinter. Adding test/test_idle will not be too much use until issue #10652 <http://bugs.python.org/issue10652> is resolved so it would actually run with -m test." To continue this work with my GSoc work, considering these points , my view is to put tests in test/test_idle directory, like test/test_email would be the best practice in the long run of python development with the hope of the issue #10652 <http://bugs.python.org/issue10652> is on a healthy patch review, so it would actually run with -m test in near future. Expecting your suggestions to come up with a decision on this design issue, so that I can move on. *"Think big, Start Small, Move Fast"* Thanks && Regards.. R. Jayakrishnan <https://www.facebook.com/raajjya> <http://123works.blogspot.com/> <https://plus.google.com/u/0/114501383949013359988/posts> <http://www.linkedin.com/profile/view?id=92231015&trk=tab_pro> <https://twitter.com/#!/raajjya>
_______________________________________________ IDLE-dev mailing list [email protected] http://mail.python.org/mailman/listinfo/idle-dev
