Isn't moto needed only for testing? install_requires affects all users… should we restrict them from using newer boto3/botocore, just because of our testing dependency?

Moto needed only for testing, that's true, I understand that this influences to all users, but this is "temporary" only (no big deal if we slightly limit boto version for some time).

As an alternative solution, I can revert this boto* restriction and instead of it, install pinned versions manually (for Travis only), this can be a better solution (because don't affect to users), wdyt @piskvorky @mpenkov?

Up to you; of course not limiting users is preferable, but it's probably no big deal, like you say.

If we can’t run our unit tests with the newest boto3, then can we be sure
things really work with that boto3 version?

If the answer is no, then we should restrict our users to boto3 versions that we know work.

That's a good point. It looks like the guys at moto are trying to resolve this.

But if they fail we'll have to unpin or do testing differently, because pinning a core library (boto3) to an old / obsolete version (a step that affects users), just to appease a testing library that users don't care about (moto) is only a temporary hack, like @menshikh-iv says.

This is breaking things downstream from you, 17 days later.

Please revert this, or move to a development-only dependency, or else it will be necessary for us to stop using this library.

@petergaultney hi, can you please describe, why does it break something? What's a problem with it? Anyway, you still can use the previous version of smart_open without pinning if this very important for you.

Related issue #227, anyway, thanks for report @petergaultney, I'll try my best to fix it ASAP

yeah, #227 is my exact issue! thanks!