Peter Pan added the comment:
Here is a small test for the new version.
(To see the original ftplib.py version failing copy+paste the code from my
initial post into a python file and run)
--
Added file: http://bugs.python.org/file42100/test_ftp.py
Peter Pan added the comment:
I've updated "ftplib.py" from the 3.5.1 source code release.
This should fix issues:
http://bugs.python.org/issue25458
http://bugs.python.org/issue25491
--
Added file: http://bugs.python.org/file42099
Peter Pan added the comment:
The problem in my example is ftplib reports a "226" response to command "NOOP"
which is nonsense. ftplib received "226" before "ftp.sendcmd('NOOP')" was
called.
Since "transfercmd()" returns a socket, ftpli
New submission from Peter Pan:
When handling the transfer socket manually the asynchronous status message "226
transfer complete" on the control socket is falsely taken as response for the
last sent command.
ftplib reads the response too late and the command/response order becomes
i
