You need to update your own code or one of your dependencies as per https://docs.djangoproject.com/en/stable/releases/1.8/#support-for-the-max-length-argument-on-custom-storage-classes.
If you follow https://docs.djangoproject.com/en/stable/howto/upgrade-version/ with an older version of Django (1.8 or 1.9), you should see a helpful deprecation warning. On Tuesday, August 30, 2016 at 9:39:46 AM UTC-4, manolo gomez wrote: > > Hi, > > I've updated from django 1.8 to 1.10, and now when save a ImageFile I'm > getting the next error: > > get_available_name() got an unexpected keyword argument 'max_length' > > > This is the end of the Traceback: > File "/home/dev/Documents/web/children/views/views.py" in post > > 73. ob.avatar.save(t[0], t[1]) > > File > "/home/securekids/Documents/enviroments/dev/local/lib/python2.7/site-packages/django/db/models/fields/files.py" > in save > 91. self.name = self.storage.save(name, content, > max_length=self.field.max_length) > > File > "/home/securekids/Documents/enviroments/dev/local/lib/python2.7/site-packages/django/core/files/storage.py" > in save > 53. name = self.get_available_name(name, max_length=max_length) > > > I've tried to remove "max_length=max_length", and then it's working > fine, but I don't like so much to touch the django core :) > > Anyone can help me? > -- You received this message because you are subscribed to the Google Groups "Django users" 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-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/dbc53072-d883-445f-a82a-37a4033cf0cc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
