1

Error when running collectstatic (manage.py)

When following the installation & setup steps for Askbot as described in the Askbot documentation (chapter "Initial Configuration of Askbot"), I run into the following error when trying to run python manage.py collectstatic after having completed askbot-setup (see last line of console output below... there is a metaclass conflict):


$ python manage.py collecstatic
Traceback (most recent call last):
  File "manage.py", line 10, in <module>
    execute_from_command_line(sys.argv)
  File "/home/caap-askbot-admin/.local/lib/python2.7/site-packages/django/core/management/__init__.py", line 354, in execute_from_command_line
    utility.execute()
  File "/home/caap-askbot-admin/.local/lib/python2.7/site-packages/django/core/management/__init__.py", line 328, in execute
    django.setup()
  File "/home/caap-askbot-admin/.local/lib/python2.7/site-packages/django/__init__.py", line 18, in setup
    apps.populate(settings.INSTALLED_APPS)
  File "/home/caap-askbot-admin/.local/lib/python2.7/site-packages/django/apps/registry.py", line 108, in populate
    app_config.import_models(all_models)
  File "/home/caap-askbot-admin/.local/lib/python2.7/site-packages/django/apps/config.py", line 198, in import_models
    self.models_module = import_module(models_module_name)
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
    __import__(name)
  File "/home/caap-askbot-admin/.local/lib/python2.7/site-packages/askbot/models/__init__.py", line 2, in <module>
    startup_procedures.run()
  File "/home/caap-askbot-admin/.local/lib/python2.7/site-packages/askbot/startup_procedures.py", line 1086, in run
    run_startup_tests()
  File "/home/caap-askbot-admin/.local/lib/python2.7/site-packages/askbot/startup_procedures.py", line 1012, in run_startup_tests
    test_modules()
  File "/home/caap-askbot-admin/.local/lib/python2.7/site-packages/askbot/startup_procedures.py", line 289, in test_modules
    try_import(mod_name, pip_path)
  File "/home/caap-askbot-admin/.local/lib/python2.7/site-packages/askbot/startup_procedures.py", line 209, in try_import
    load_module(module_name)
  File "/home/caap-askbot-admin/.local/lib/python2.7/site-packages/askbot/utils/loading.py", line 23, in load_module
    return __import__(mod_path, globals(), locals(), [], -1)
  File "/home/caap-askbot-admin/.local/lib/python2.7/site-packages/picklefield/__init__.py", line 5, in <module>
    from picklefield.fields import PickledObjectField # reexport
  File "/home/caap-askbot-admin/.local/lib/python2.7/site-packages/picklefield/fields.py", line 79, in <module>
    class PickledObjectField(_get_subfield_superclass()):
  File "/home/caap-askbot-admin/.local/lib/python2.7/site-packages/django/db/models/fields/subclassing.py", line 24, in __new__
    new_class = super(SubfieldBase, cls).__new__(cls, name, bases, attrs)
TypeError: Error when calling the metaclass bases
    metaclass conflict: the metaclass of a derived class must be a (non-strict) subclass of the metaclasses of all its bases

Has anyone encountered the same or similar problem?

I am running Ubuntu 16.04 LTS and Python 2.7.12...

fema's avatar
11
fema
asked 2017-09-18 10:54:51 -0600
edit flag offensive 0 remove flag close merge delete

Comments

add a comment see more comments

3 Answers

0

did you configure your smtp hots in settings.py ?

Gabriel Luk's avatar
36
Gabriel Luk
answered 2018-11-27 01:50:32 -0600
edit flag offensive 0 remove flag delete link

Comments

add a comment see more comments
0

means manage.py not found at your location try to run this command from your askbot installation directory...

gopalraha's avatar
332
gopalraha
answered 2017-09-24 12:00:51 -0600, updated 2017-09-24 12:01:05 -0600
edit flag offensive 0 remove flag delete link

Comments

I have the same error and running in the correct directory. This is not the answer for me. Stumped by this one. Seems like a coding error...?

Rupreck's avatar Rupreck (2017-10-01 03:50:40 -0600) edit
add a comment see more comments
0

I got the same error when setting up the project. re-creating the virtual environment solved the issue. and major thing, if you are getting errors in mysqldb or mysql-python installation, check and verify the version of six. It should be six==1.10.0.

I'm running on ubuntu 14.04 and Python 2.7. so for you also it won't be the problem.

testuser's avatar
21
testuser
answered 2019-07-03 04:33:16 -0600
edit flag offensive 0 remove flag delete link

Comments

add a comment see more comments