Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
BaseCommand.option_list deprecated in django 1.10
See original GitHub issueAttributeError: type object 'BaseCommand' has no attribute 'option_list'
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (2 by maintainers)
Top Results From Across the Web
Django 1.10 dropped the basecommand.option_list; can I fix ...
Django 1.8 deprecated BaseCommand.option_list: see here; since Django 1.10 the option_list is gone! Can I update the run_gunicorn.py file to ...
Read more >Django 1.10 release notes
We've dropped some features that have reached the end of their deprecation cycle, and we've begun the deprecation process for some features.
Read more >type object 'BaseCommand' has no attribute 'option_list ...
BaseCommand.option_list is deprecated in Django 1.8 and removed ... Django 1.10 has not been released yet, and is still under development.
Read more >Django 1.8 release notes
The class NoArgsCommand is now deprecated and will be removed in Django 1.10. Use BaseCommand instead, which takes no arguments by default.
Read more >Django 1.9 Release Notes and Stories
Django 1.9 requires Python 2.7, 3.4, or 3.5. ... All GeoQuerySet methods have been deprecated and replaced by equivalent database functions.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Seems like they are keeping #447 fixed in master branch (3.2.a1 version).
For whom, who are in rush like me, I solved this issue with updating my requirements.txt:
ahh, shame it is not fixed