paul rubin <p...@users.sourceforge.net> added the comment: ajaksu2, I don't understand why you want to close this bug if it isn't fixed. I can accept that it's not the highest priority issue in the world, but it's something that trips up users from time to time, and it ix obviously fixable. Closing bugs like this is demoralizing to those of us who take the trouble to submit them in the hope of helping improve Python. I've noticed that any number of times over the years, and recently saw a post about Ubuntu bug triage that expressed the sentiment better than I could:
http://www.chiark.greenend.org.uk/ucgi/~cjwatson/blosxom/2009/03/02 (And while trying to locate that several week old post through web searches, I came across several more like it...). Anyway, the best thing to do with bugs like this is fix them. If there is other work with higher priority, the obvious thing is to just leave the bug open so someone gets around to it sooner or later. Closing the bug without a fix comes across as destructive. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue1560032> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
