You are not using the length param in Minio.put_object, why not make it optional?

See: https://github.com/minio/minio-py/blob/master/minio/api.py#L797

    def put_object(self, bucket_name, object_name, data, length,
                   content_type='application/octet-stream',
                   metadata=None):
        # ...
        return self._do_put_object(bucket_name, object_name,
                                   current_data, len(current_data),
                                   metadata=metadata)

And getting the length of when doing put_object is tedious and make no much sense.

For example:

buf = io.BytesIO(b'Hello, World!')
length = buf.getbuffer().nbytes
ossc.put_object('default', 'test-blob', buf, length)

Which makes too much noise to my code, I probably should care whether the buf object is an BytesIO or other file-like object.

Thanks!

[balamurugana]

@gerritsangel The support is added in the master https://github.com/minio/minio-py/blob/master/minio/api.py#L1252

We will make new release soon.

[gerritsangel]

Hello,

I was wondering on how to upload a stream of unknown size with the Minio Python SDK.

The Java SDK supports uploading of unknown size streams, so I’m a bit surprised that the Python SDK doesn’t seem to support it.

(See https://minio-java.min.io/io/minio/MinioClient.html#putObject-io.minio.PutObjectArgs-):

 // Upload unknown sized input stream.
 minioClient.putObject(
     PutObjectArgs.builder().bucket("my-bucketname").object("my-objectname").stream(
             inputStream, -1, 10485760)
         .contentType("video/mp4")
         .build());

Here, the file part size must be manually specified, but the stream length can be set as -1.

is there any protocol issue that would prevent the Python SDK to support unknown streams? Reading the entire stream into memory is difficult if it is a large file, especially on devices with few memory 😦