New submission from Sam Adams:
Hello,
I believe that I found a bug in ftplib.py in version 3.3.6.
Whenever a user opens a file for writing in nonbinary mode and then proceeds to
call the retrbinary function, or opens the file in binary mode and proceeds to
call the retrlines fuction, then
Changes by Sam Adams :
--
type: -> behavior
___
Python tracker
<http://bugs.python.org/issue25933>
___
___
Python-bugs-list mailing list
Unsubscrib
Sam Adams added the comment:
I don't have access to 3.5 where I am now. I can try later on, but it appears
after a quick glance that the code for this function between 3.3 and 3.5 is the
same for calling the callback function.
--
___
Python tr
Sam Adams added the comment:
Silent: The issue that i see is how the error is handled. I can trap the
TypeError easily, however, if I keep the socket open, the behavior of ftplib
will not be as intended. For example:
fileTest = open('filename1', 'wb')
ftp.retrlin
