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 orsenthil
Recipients brett.cannon, docs@python, ezio.melotti, orsenthil, r.david.murray, rosslagerwall, stutzbach
Date 2011-08-03.01:15:07
SpamBayes Score 4.425261e-06
Marked as misclassified No
Message-id <1312334109.0.0.127984307373.issue12682@psf.upfronthosting.co.za>
In-reply-to
Content
I thought "fixed" was enough. A kind of binary state where we say, okay we have it and otherwise no, we don't. I know for feature requests the terminology does not make sense, but I believe I have worked with bug trackers where fixed was the ultimate state where a particular change (be a bug-fix or a feature request) was in the code.

Well, as long as it is helpful, I am fine with it, but too many options can confuse (just as 'accepted' did) and it will be helpful to prune down some.
History
Date User Action Args
2011-08-03 01:15:09orsenthilsetrecipients: + orsenthil, brett.cannon, stutzbach, ezio.melotti, r.david.murray, docs@python, rosslagerwall
2011-08-03 01:15:08orsenthilsetmessageid: <1312334109.0.0.127984307373.issue12682@psf.upfronthosting.co.za>
2011-08-03 01:15:08orsenthillinkissue12682 messages
2011-08-03 01:15:07orsenthilcreate