Hi Andy, I think it would be nice for the Storage class to at least have the most common file system operations. Each implementation would then choose which of them it wants to implement.
You could even write your own extension, but at least you would know that what you are coding is based on a common API. Regards, Alex On Wednesday, April 10, 2013 5:08:25 PM UTC+3, Andrew Ingram wrote: > > On 10 April 2013 14:56, Javier Guerra Giraldez > <jav...@guerrag.com<javascript:>> > wrote: > > check django-storages > > http://django-storages.readthedocs.org/en/latest/ it includes several > > storage backends, S3 among them. > > > > -- > > Javier > > I think he was asking whether the storage API should be extended to > support additional operations, namely "move" and "copy". I imagine he > already has an s3 storage backend. > > I can see how such methods would be useful, but I'd also be a little > wary of going too far down the road of building an entire filesystem > abstraction API. > > Andy > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
