You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 10, 2017. It is now read-only.
----------
ID: assets-standard-collaborator
Function: cmd.run
Name: source .ve/bin/activate; python manage.py assets build
Result: False
Comment: Command "source .ve/bin/activate; python manage.py assets build" run
Started: 16:14:36.512559
Duration: 387.64 ms
Changes:
----------
pid:
24438
retcode:
1
stderr:
Traceback (most recent call last):
File "manage.py", line 58, in <module>
execute_from_command_line(sys.argv)
File "/home/opencontracting/standard-collaborator/django/website/.ve/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 338, in execute_from_command_line
utility.execute()
File "/home/opencontracting/standard-collaborator/django/website/.ve/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 330, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/home/opencontracting/standard-collaborator/django/website/.ve/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 190, in fetch_command
klass = load_command_class(app_name, subcommand)
File "/home/opencontracting/standard-collaborator/django/website/.ve/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 40, in load_command_class
module = import_module('%s.management.commands.%s' % (app_name, name))
File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
__import__(name)
File "/home/opencontracting/standard-collaborator/django/website/.ve/local/lib/python2.7/site-packages/django_assets/management/commands/assets.py", line 29, in <module>
from django.core.management import LaxOptionParser
ImportError: cannot import name LaxOptionParser
stdout:
I suspect this is due to changes in Django 1.8. It's not currently affecting our live/dev sites as the assets have not changed since last time they were successfully deployed.
The text was updated successfully, but these errors were encountered:
From our salt run:
I suspect this is due to changes in Django 1.8. It's not currently affecting our live/dev sites as the assets have not changed since last time they were successfully deployed.
The text was updated successfully, but these errors were encountered: