list-objects-*: implement allow unordered option

[snosratiershad]

As discussed in this issue

[snosratiershad]

@fviard, if there is anything I can help about it, feel free to contact me.

[fviard]

Sorry for the delay of my reply.
Instead of adding the parameter to all the function prototypes, i think that you can use directly self.config.allow_unordered inside def bucket_list_noparse(...).

Also, it will not be limited to "ls" anymore, but I think that it is ok, as s3cmd sync logic never assumed that file list would be in order for remote or local side.

[snosratiershad]

@fviard, as you requested, I changed it to a config variable.
I couldn't found any of documentation files in the repository, but I think it must be included in somewhere as there is no help message for now.

[fviard]

@snosratiershad You could have kept the "command line switch" in addition with the help, that was good.

What is happening is that the config comes from the config file, but command line switches allow to override the config files.
It has no relation with how you use it inside the code after that.

[snosratiershad]

@fviard, should command line switch literally overide config file, or just ignoring the value comes from self.config.list_objects_allow_unordered when the `--ls-allow-unordered' switch called?

[snosratiershad]

I realized what you mean. also going to change "list-objects-allow-unordered" to "list-allow-onordered".

[snosratiershad]

@fviard Done.
Update: the force push is because my typo in first push.

[fviard]

Merged, thank you!

[visbits]

Delimiter cannot be used with allow-unordered.

The code must not set a limiter if allow-unordered is true:
From line 400 in S3.py
if not self.config.recursive and not recursive:
To
if not self.config.recursive and not recursive and not self.config.list_allow_unordered:

[snosratiershad]

@visbits Thanks for pointing this out. I'll check it out and fix it.