On Monday 30 January 2017 08:47:10 Tim Graham wrote:
> I meant: where does Django call that method that's causing a problem
> for your use case?
It doesn't. But both listdir() and now that I'm looking, also path() are
FileSystemStorage (or better: Hierarchial storage) artifects, that don't belong
I meant: where does Django call that method that's causing a problem for
your use case?
On Monday, January 30, 2017 at 11:43:27 AM UTC-5, Melvyn Sopacua wrote:
>
> On Monday 30 January 2017 08:16:20 Tim Graham wrote:
>
> > Hi, could you point to where the problematic storage.listdir() call is
>
>
On Monday 30 January 2017 08:16:20 Tim Graham wrote:
> Hi, could you point to where the problematic storage.listdir() call is
> in Django?
Sure.
https://docs.djangoproject.com/en/1.10/ref/files/storage/#django.core.files.storage.Sto
rage.listdir
> On Monday, January 30, 2017 at 11:02:32 AM UTC-5,
Hi, could you point to where the problematic storage.listdir() call is in
Django?
On Monday, January 30, 2017 at 11:02:32 AM UTC-5, Melvyn Sopacua wrote:
>
> Hello,
>
>
>
> the current Storage API has some inconsistencies and in short it's
> impossible to write anything that requires a directo
Hello,
the current Storage API has some inconsistencies and in short it's impossible
to write
anything that requires a directory to be made (if storage is FileSystemStorage)
in an
implementation agnostic way.
Aside from that, there's a listdir() method that only makes sense in a
FileSystemSt
