ddve...@ucar.edu added the comment: If no one is able to reproduce it, I guess we can close it.
I am sure I can reproduce it if I run it in the same situation I ran it the first time. However, I initially reported the bug for python 2.7.6 i.e. two versions ago, so it might have been fixed by something that happened meanwhile (or did the ones who tried used the exact version I reported the bug against?) If I experience the bug again while installing v2.7.9, I will report it here again (you all receive updates even if the bug is closed, right? I am asking because I don't thing I have the rights to re-open it). Thanks, Davide On Sat, Oct 4, 2014 at 6:47 PM, Mark Lawrence <rep...@bugs.python.org> wrote: > > Mark Lawrence added the comment: > > As there has been no response can this be closed? > > ---------- > nosy: +BreamoreBoy > status: pending -> open > > _______________________________________ > Python tracker <rep...@bugs.python.org> > <http://bugs.python.org/issue21278> > _______________________________________ ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue21278> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
