search

arteria / django-compat

Forward and backwards compatibility layer for Django 1.4, 1.7, 1.8, 1.9, 1.10, and 1.11
MIT License
106 stars 30 forks source link

New version brokes with Django==1.5.10 and six==1.3.0 #36

Closed joac closed 9 years ago

joac commented 9 years ago 
   File "/var/www/.virtualenvs/ditchcity/local/lib/python2.7/site-packages/django/db/models/loading.py", line 72, in _populate
     self.load_app(app_name, True)
   File "/var/www/.virtualenvs/ditchcity/local/lib/python2.7/site-packages/django/db/models/loading.py", line 94, in load_app
     app_module = import_module(app_name)
   File "/var/www/.virtualenvs/ditchcity/local/lib/python2.7/site-packages/django/utils/importlib.py", line 35, in import_module
     __import__(name)
   File "/var/www/.virtualenvs/ditchcity/local/lib/python2.7/site-packages/compat/__init__.py", line 42, in <module>
     from six.moves._thread import get_ident  # noqa
 ImportError: No module named _thread
ubuntu@staging:~$ python --version
Python 2.7.6
philippeowagner commented 9 years ago

django-compat intends to provide for- and backwards compatibility to all version supported by django itself. This is the list of all supported version at the moment. More info can be taken from the mailing list.

philippeowagner commented 9 years ago

(@joac the idea is to make all your apps "compatible" using compat and then upgrade django itself to the next or latest greatest release.)