Calling Format gone?

I can’t find any reference to S3 “calling format” in boto3. At first I thought it was just a documentation oversight, but I can’t find anything like that in the source code, either (though the source code is completely different from boto2, so maybe I just don’t know what to look for).

Is this feature gone? Without OrdinaryCallingFormat, is it now impossible to use this with fake-s3?

I found this page which suggests this will help:

from botocore.utils import fix_s3_host
resource.meta.client.meta.events.unregister('before-sign.s3', fix_s3_host)

but it doesn’t seem to make a difference.

Here’s the simplified test case I’m working with:

import boto3
from StringIO import StringIO
session = boto3.session.Session(aws_access_key_id='1',
                                aws_secret_access_key='2',
                                region_name='3')
s3 = session.resource('s3', endpoint_url='http://localhost:5353', use_ssl=False)
bucket = s3.Bucket('my-local-bucket')

obj = bucket.Object(key='my-test-key')
obj.put(StringIO("abc"))

obj = bucket.Object(key='my-test-key')
obj.get()['Body'].read()  # returns the empty string

The documentation doesn’t say, but empirically, it seems the keys passed to Session can’t be None, but they can be any string.

[jamesls]

It might help to turn on debug logging to see what endpoints it’s trying to connect to. At the top of your script you can add:

import boto3
boto3.set_stream_logger(name='')

And it will print out debug logs to stderr.

[jamesls]

#325 is merged, closing out issue. Also @kengruven that latest issue you’re running into is the same as boto/botocore#601. Let’s track that issue over there.