Wednesday, August 31, 2016

Re: get_available_name() got an unexpected keyword argument 'max_length'

I thought that I've checked all my dependecies, and effectively I forget to update one of them. Now it's working, thank you very much.

El martes, 30 de agosto de 2016, 18:45:23 (UTC+2), Tim Graham escribió:
You need to update your own code or one of your dependencies as per

If you follow 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:
   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/" in post
  73.           [0], t[1])     File "/home/securekids/Documents/enviroments/dev/local/lib/python2.7/site-packages/django/db/models/fields/" in save    91. =, content, max_length=self.field.max_length)    File "/home/securekids/Documents/enviroments/dev/local/lib/python2.7/site-packages/django/core/files/" 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
To post to this group, send email to
Visit this group at
To view this discussion on the web visit
For more options, visit

No comments:

Post a Comment