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 techtonik
Recipients flox, loewis, techtonik
Date 2012-07-22.18:35:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1342982154.76.0.700038356538.issue15420@psf.upfronthosting.co.za>
In-reply-to
Content
> Please don't reopen issues.

"Please don't ask for such silly stuff". You can understand the reason why this issue was opened, so why do you keep closing it if the "issue is not resolved"? 


The scope of this issue never changed, Martin. If you follow the user story, it is still the same original "user issue" or bad user experience with 2to3 tool.

It is fine if you're not going to work on a fix, but that's NOT the reason to close the issue. The proper fix would be to explain why you think there is nobody except yourself who can fix that, or provide the guarantees that the fix won't be accepted.
History
Date User Action Args
2012-07-22 18:35:54techtoniksetrecipients: + techtonik, loewis, flox
2012-07-22 18:35:54techtoniksetmessageid: <1342982154.76.0.700038356538.issue15420@psf.upfronthosting.co.za>
2012-07-22 18:35:54techtoniklinkissue15420 messages
2012-07-22 18:35:54techtonikcreate