#32452: Simplify storing strings/bytes in a Storage
-------------------------------------+-------------------------------------
     Reporter:  Thomas Güttler       |                    Owner:  nobody
         Type:  New feature          |                   Status:  new
    Component:  File                 |                  Version:  3.1
  uploads/storage                    |
     Severity:  Normal               |               Resolution:
     Keywords:                       |             Triage Stage:
                                     |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Description changed by Thomas Güttler:

Old description:

> Docs: https://docs.djangoproject.com/en/3.1/topics/files/#storage-objects
>
> > path = default_storage.save('path/to/file', ContentFile(b'new
> content'))
>
> Things would be bit easier, if `save()` would support strings/bytes
> directly.
>
> This way a developer needs to type and import less code:
>
> {{{
> path = default_storage.save('path/to/file', b'new content')
> }}}
>
> {{{
> path = default_storage.save('path/to/file', 'new unicode string, encoded
> automatically with utf-8')
> }}}
>
> Would you accept a patch to `Storage.save()`?

New description:

 Docs: https://docs.djangoproject.com/en/3.1/topics/files/#storage-objects

 > path = default_storage.save('path/to/file', ContentFile(b'new content'))

 Things would be bit easier, if `save()` would support strings/bytes
 directly.

 This way a developer needs to type and import less code:

 {{{
 path = default_storage.save('path/to/file', b'new content')
 }}}

 {{{
 path = default_storage.save('path/to/file', 'new unicode string, encoded
 automatically with utf-8')
 }}}

 Would you accept a patch to `Storage.save()`?

 Background: I am writing a unittest which mocked away the storage calls to
 save() will put the data into the mock.

 Then I check if the data is the way I want it.

 Now it gets complicated again: I need to access the data which is inside
 `ContentFile` grrr.

 This would be much easier if you could add strings/bytes to the `save()`
 directly.

--

-- 
Ticket URL: <https://code.djangoproject.com/ticket/32452#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.46e2493619ef5ba5d075f7bc397b8472%40djangoproject.com.

Reply via email to