Change by Rich rauenzahn :
--
nosy: +rrauenza
___
Python tracker
<https://bugs.python.org/issue43833>
___
___
Python-bugs-list mailing list
Unsubscribe:
Rich Rauenzahn added the comment:
Thank you, lukasz. That's the answer I anticipated -- I can appreciate the
backwards compatibility aspect very much.
Regarding the docs, the docs say:
"Attempt to read and parse a list of filenames, returning a list of filenames
which were success
Rich Rauenzahn added the comment:
Given that write() accepts a fileobject, but read() accepts a list of strings
or a string (and readfp() is the one that accepts a fileobject instead), this
seems like it could be a common enough error that just iterating over the
fileobject could
New submission from Rich Rauenzahn:
This came up on StackOverflow: http://stackoverflow.com/a/37903779/2077386
I wanted to bring it to your attention in case it hasn't been notice before.
It turns out that if you pass a fileobject (i.e.,
ConfigParser().read(open("foo"))) ConfigP
Rich Rauenzahn rraue...@gmail.com added the comment:
Yes, the source box was checkmarked.
Not the first one to encounter this as well:
http://python.6.n6.nabble.com/IDLE-not-highlighting-current-line-while-debugging-on-Win-td2113345.html
New submission from Rich Rauenzahn rraue...@gmail.com:
Using 64bit python for windows downloaded from python.org on 64bit windows 7.
Python Version 3.2.2
Tk version 8.5
IDLE version 3.2.2
When stepping through code the corresponding line in the editor does not
highlight with the code steps
