Installation is currently scoped as boto >= 2.6.0 only, which meanwhile yields boto 2.15.0 eventually and support for region us-gov-west-1 therein, causing tests to fail.
:question: Just listing all regions is a questionable default I think, but the use case at hand might be a bit special in this regard - it's worth noting though that e.g. the AWS Tools for Windows PowerShell are excluding that region by default and offering a -IncludeGovCloud parameter, which supposedly serves much more real world use cases out of the box; OTOH, boto is a library and not a CLI tool, which might tick the argument the other way.
Fixing the test as such would be trivial, but this needs to be done transparently for the entirely library to avoid further regressions - the outlined approach via an opt-in parameter seems to be reasonable and simple though.
Installation is currently scoped as
boto >= 2.6.0only, which meanwhile yields boto 2.15.0 eventually and support for regionus-gov-west-1therein, causing tests to fail.boto.<service>.regions()suddenly returns a usually non accessible region too (see https://github.com/boto/boto/commit/e31d72697f7ddbdec92026565438394ed32d4df4#diff-0189bf06708b977e3e67cff826d9d524).-IncludeGovCloudparameter, which supposedly serves much more real world use cases out of the box; OTOH, boto is a library and not a CLI tool, which might tick the argument the other way.Fixing the test as such would be trivial, but this needs to be done transparently for the entirely library to avoid further regressions - the outlined approach via an opt-in parameter seems to be reasonable and simple though.