Can you try:
pip install -U
https://github.com/GrahamDumpleton/mod_wsgi/archive/develop.zip
<https://github.com/GrahamDumpleton/mod_wsgi/archive/develop.zip>
and verify that it solves the problem.
I used a monumental hack to fix it, but will do until I drop Python 2.6 support.
This has not yet been test with Django <1.10 yet. Will do that shortly.
If you see any problems at all, and not just with this let me know. The develop
branch has also got some changes related to setting up access controls in
Apache. I hope I got those right, but if you start getting forbidden responses
tell me what you were doing. Would be particularly worried about where using
server name, SSL etc.
Graham
> On 19 Aug 2016, at 8:56 AM, Graham Dumpleton <[email protected]>
> wrote:
>
> First I knew about it unfortunately.
>
> Is also a right pain as I need to still support Python 2.6 and it doesn’t
> have the argparse module, so I can’t simply switch to using argparse from
> optparse.
>
> Trying to work out what compromise solution there is.
>
> Graham
>
>> On 19 Aug 2016, at 1:37 AM, 'Danny' via modwsgi <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>> This is probably a known issue, but I wanted to know if a fix was planned,
>> already implemented, or if I should back up to Django 1.9
>>
>> I have a fresh install of Django 1.10 and mod_wsgi 4.5.5.
>>
>> If I do a simple python manage.py runmodwsgi
>> I get:
>>
>> $ ./manage.py runmodwsgi
>> Traceback (most recent call last):
>> File "./manage.py", line 10, in <module>
>> execute_from_command_line(sys.argv)
>> File
>> "/opt/Envs/guidewire/lib/python3.5/site-packages/django/core/management/__init__.py",
>> line 367, in execute_from_command_line
>> utility.execute()
>> File
>> "/opt/Envs/guidewire/lib/python3.5/site-packages/django/core/management/__init__.py",
>> line 359, in execute
>> self.fetch_command(subcommand).run_from_argv(self.argv)
>> File
>> "/opt/Envs/guidewire/lib/python3.5/site-packages/django/core/management/__init__.py",
>> line 208, in fetch_command
>> klass = load_command_class(app_name, subcommand)
>> File
>> "/opt/Envs/guidewire/lib/python3.5/site-packages/django/core/management/__init__.py",
>> line 40, in load_command_class
>> module = import_module('%s.management.commands.%s' % (app_name, name))
>> File "/opt/Envs/guidewire/lib/python3.5/importlib/__init__.py", line 126,
>> in import_module
>> return _bootstrap._gcd_import(name[level:], package, level)
>> File "<frozen importlib._bootstrap>", line 986, in _gcd_import
>> File "<frozen importlib._bootstrap>", line 969, in _find_and_load
>> File "<frozen importlib._bootstrap>", line 958, in _find_and_load_unlocked
>> File "<frozen importlib._bootstrap>", line 673, in _load_unlocked
>> File "<frozen importlib._bootstrap_external>", line 665, in exec_module
>> File "<frozen importlib._bootstrap>", line 222, in
>> _call_with_frames_removed
>> File
>> "/opt/Envs/guidewire/lib/python3.5/site-packages/mod_wsgi/server/management/commands/runmodwsgi.py",
>> line 9, in <module>
>> class Command(BaseCommand):
>> File
>> "/opt/Envs/guidewire/lib/python3.5/site-packages/mod_wsgi/server/management/commands/runmodwsgi.py",
>> line 10, in Command
>> option_list = BaseCommand.option_list + mod_wsgi.server.option_list
>> AttributeError: type object 'BaseCommand' has no attribute 'option_list'
>>
>> I am sure this is related to django changing command argument handling in
>> 1.10:
>> see:
>>
>> http://stackoverflow.com/questions/35181133/python-attribute-error-when-running-script-type-object-basecommand-has-no-att
>>
>> <http://stackoverflow.com/questions/35181133/python-attribute-error-when-running-script-type-object-basecommand-has-no-att>
>> https://github.com/django-nose/django-nose/issues/254
>> https://github.com/celery/django-celery/issues/457
>>
>> etc.
>>
>> Should I just roll back to Django 1.9 for the time being?
>>
>> thanks,
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "modwsgi" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected]
>> <mailto:[email protected]>.
>> To post to this group, send email to [email protected]
>> <mailto:[email protected]>.
>> Visit this group at https://groups.google.com/group/modwsgi
>> <https://groups.google.com/group/modwsgi>.
>> For more options, visit https://groups.google.com/d/optout
>> <https://groups.google.com/d/optout>.
>
--
You received this message because you are subscribed to the Google Groups
"modwsgi" 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/modwsgi.
For more options, visit https://groups.google.com/d/optout.
