Nikita Melentev

It's not «unfair» it's just caching. That benchmark good side is that it written by pyftpdlib guys, so no code from my side. Client side have no benchmarks.

@martindurant if you have any ideas to improve "benchmark" part of readme, then feel free to make a PR. Speed is not the main goal of `aioftp`. I agreed that...

First of all, this server do not support `MLSx` commands. You can ensure this with `logging.basicConfig(level=logging.DEBUG)` before your code. ``` DEBUG:asyncio:Using selector: EpollSelector INFO:aioftp.client:220 INFO:aioftp.client:USER anonymous INFO:aioftp.client:331 Anonymous access allowed,...

I've just released version 0.14.0 so you have an option to force your own parsing routine. https://aioftp.readthedocs.io/client_api.html#aioftp.Client

> may I suggest few other corrections to the project Feel free to make pull request. I fix the typo about double "type". > please use time.time standard utc float...

## Transmit: ### client: ``` 1: Cmd: PASV 1: Cannot parse PASV response: listen socket created 1: 227: listen socket created 1: (0,0,0,0,137,217) 1: Passive mode refused. 1: Connection falling...

Yes, the problem with filezilla is that it looks like it does not respect `0.0.0.0` answer, which means «same address as command connection».

`127.0.0.1` will work only on same machine. If you have virtual machines, `127.0.0.1` for them is itself, not your `127.0.0.1`. It is same as for docker networking. You can bind...

But, as I said before, `0.0.0.0` is legal and this is a client issue.

I don't get the problem, you can recognize version via `python -m pip list | grep aioftp`.