Hello, I have recently found an interesting issue, using a project that relies on different storage backends, when switching from a custom one to django's file system storage, I found that existing code that would iterate files with the next() call would start to fail, since although django's File is iterable, it doesn't define the next method.
Now I'm wondering if this is on purpose, or a bug. It's odd that every stream (or almost) from the python library such as everything from the .io module or simply the object returned by open() (python 2) supports the next call but the django File wrapper doesn't. This happened with django 1.10 and I believe it wasn't changed with Django 1.11 -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/09ffad76-e473-4593-ac84-4bca7f76e92c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
