Djangocms tutorial install error AttributeError: 'module' has no attribute 'atomic'
I am trying to install djangocms with no success. Details follow
I have the following system:
Windows 8.1 64 bit installation
Python 2.7.8
You can see in the djangocms output that I ended up using the django version to install:
Django version 1.5
I started using djangocms tutorial https://github.com/divio/django-cms-tutorial/blob/master/Step%201%20-%20Initial%20Setup.md
I have installed new python, pip and virtualenv. Then I created a virtualenv, activated it and used pip from inside that virtualenv to install the package
djangocms installer
I ran into an error when I go to step
djangocms -p. my_site
At this point I am specifying the django version as recommended during the installation process. Django version (choices: 1.4, 1.5, 1.6, stable) [stable by default]: 1.5
I really can't figure out the way out. I read it and searched this group site to the best of my ability, as well as the bug tracker on the training site github.
The output is from the gist link below. Note that I made a slight change to this output, I named the project djangocms mysite, not my_site. I achieved the same failure with both
https://gist.github.com/GaryHendrick/107ec2db9dad14928bfd
Error after the initial stack reads
AttributeError: 'module' object has no attribute 'atomic'
Do you have any of you?
Regards,
Gary
source to share
It turned out that the tutorial for djangocms was modified on August 5th, you can see the history of the changes here and according to the changed instructions this error will be prevented from occurring, but maybe some people will be helped by my experience in the future. I will explain
The exception that came out of
djangocms -p . my_site
was
AttributeError: 'module' object has no attribute 'atomic'
It turns out I caused this problem by choosing the Django 1.5 prompt:
Django version (choices: 1.4, 1.5, 1.6, stable) [default stable]:
You will see that the following link indicates that the atomic setup is new from Django 1.6.
https://docs.djangoproject.com/en/1.6/ref/settings/#std:setting-DATABASE-ATOMIC_REQUESTS
I'm not sure about the solution if you need to use the Django version <1.6 that is suggested as an option above, but if you have the flexibility to use the Django 1.6 version or higher, you won't run into the exception I made.
source to share