On Sun, 1 Nov 2015 12:45 pm, Michiel Overtoom wrote: > >> On 31 Oct 2015, at 06:59, Terry Reedy <tjre...@udel.edu> wrote: >> This is a different issue than IDLE avoiding clashes. I opened >> https://bugs.python.org/issue25522 > > Terry, thanks for recording this into the issue tracker. > > I'd go even a step further. I think IDLE should not only warn, but > completely prevent saving a file which shadows a stdlib module, which will > effectively render Python unusable.
Really? [steve@ando ~]$ touch collections.py [steve@ando ~]$ python -c "import math; print math.sin(1.25)" 0.948984619356 Looks like Python is still usable to me. > I remember from a few weeks back, a > teacher with the same problem posted this on the mailinglist. Eventually > she had a technician coming in to reinstall Windows, just to fix this > problem ;-) What an overkill... If that is true, that's really sad. Were we really unable to tell this teacher to delete the shadowing file? Or was there more to the problem than that? -- Steven -- https://mail.python.org/mailman/listinfo/python-list
