This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Tomoki.Imai
Recipients JayKrish, Todd.Rovito, Tomoki.Imai, ezio.melotti, francismb, ncoghlan, ned.deily, r.david.murray, roger.serwy, terry.reedy, tshepang
Date 2013-04-22.13:30:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1366637424.58.0.865835276419.issue15392@psf.upfronthosting.co.za>
In-reply-to
Content
Oh, no support for Python2?
I think, it is too old, but still needs bug-fix supports.
IDLE for Python2 is really buggy.
For example, unicode problems in my environment. http://bugs.python.org/issue17348
It might be GUI related problem.

By the way, your proposal seemed good to me.
My proposal is almost same.
Using unittest module, make directory such as idlelib/test and write unittest there.

But I want to include Python2 and GUI support.
(So, there are unittset.mock problem)

Of cource, it is very import to concentrate on one thing (i.e Python3).
I cannot deside whether to drop Python2 support now.

I considered PEP 434 premit me writing unittest for Python2.
http://www.python.org/dev/peps/pep-0434/

How do you think?
History
Date User Action Args
2013-04-22 13:30:24Tomoki.Imaisetrecipients: + Tomoki.Imai, terry.reedy, ncoghlan, ned.deily, ezio.melotti, roger.serwy, r.david.murray, Todd.Rovito, tshepang, francismb, JayKrish
2013-04-22 13:30:24Tomoki.Imaisetmessageid: <1366637424.58.0.865835276419.issue15392@psf.upfronthosting.co.za>
2013-04-22 13:30:24Tomoki.Imailinkissue15392 messages
2013-04-22 13:30:24Tomoki.Imaicreate