I was trying to start my django server, but constantly getting the above error
django version is 1.5 (due to my project's backward compatibility issue, we cannot upgrate it to a newer version)
python version is 2.7.7
I've searched online and find that usually, this is due to Django version, once switched to 1.5, it'll be fine, but for me, it's still there.
Any help please?
Never mind, I solved this problem by creating a python27_env virtual environment and pip installed all required modules, and then it worked.
I'm guessing it's due to something got messed up in my desktop setup for python27.
Thanks guys.
Related
I have freshly installed PrestaShop 1.6.12 and I install PTS Basic Theme from there: PrestaBrain (developer says it's working on 1.6.X versions).
I installed all modules and switched for this theme.
On my website i can see just this:
Error says: No template found for module pspagebuilder. I sent question how to slove this to developer of this theme but i didn't get any answer.
How to fix it? Also maybe should I downgrade my Presta to lower version? Maybe 1.6.11 (how to do that?). I can't find any solution in google.. :(
You've got a reply on your question on PrestaBrain Ticksy :
https://prestabrain.ticksy.com/ticket/1141690/
hi, you can download it in here : https://www.dropbox.com/s/s8klnq2hmljoqb9/pf_basic_full.zip?dl=0
we update module pspagebuilder, psverticalmenu
thanks
I have encountered this issue and tried all previous solutions to no avail. Have tried rolling back requests to older versions, have tried updating pyinstaller. Please guys, if you know a configuration that works, let me know.
I am compiling some python 2.7 code that uses Kivy
I am an idiot. I was piping the wrong python install. I use a separate version for other projects, and I sandbox my kivy one to prevent conflicts... too bad I forgot about that :)
At first, I want to say that I faced the exact same problem described here. But the thing is, the answer doesn't fit me, I installed babel, updated it to the latest version and nothing changed. Also, I uninstalled my phantomjs 1.9.8 and installed 2.0.1, I thought that was a great idea, but again, no result. Does anybody know the reason why this can happen?
Please find addon that's using ES6 in your addons and either remove ES6 code from it or install there Babel.
Django 1.6 disabled the formerly automatically enabled sitesframework. This introduced a bug in the views section of admin docs.
The maintainers have already fixed and closed it
https://code.djangoproject.com/ticket/21386
I have a fresh pip install of 1.6, but the error is still present. My guess is that the fix is currently not built into the latest stable available over PIP?
My question is: What way would you suggest to get that fix into my running setup? (If possible I'd like to leave it on PIP instead of checking out django directly from Github)
Solution from the maintainers
If someone stumbles upon this issue see bouke's reply on the official ticket:
https://code.djangoproject.com/ticket/21386#comment:8
Setting SITE_ID=None in your settings.py solves the error.
This was fixed in the master branch, which is the place where development toward the new major 1.7 release happens. This means the problem will be fixed in 1.7, but the version is not out yet, and won't be for the next couple of months.
You may try asking the Django team (politely!) to backport the change to the stable/1.6.x branch, since its not a new future, but just a fix for a problem in 1.6. Changes in this branch will be included in the minor 1.6.2 release, when it comes out.
My question is: What way would you suggest to get that fix into my
running setup? (If possible I'd like to leave it on PIP instead of
checking out django directly from Github)
You will not find a version with the fix in the Python Package Index (used by pip), as long as a stable release which includes the change doesn't come out.
Here are some options:
Wait till a new stable version with the fix comes out.
NOT RECOMMENDED: You can install a current development version of Django from the master branch. This would solve your particular problem, but would be absolutely insane and most likely would introduce all kinds of other problems.
You can get the 1.6.1 stable version from git, and then try to manually cherry-pick the change from the master branch. It's quite likely this won't work or at least require some additional manual changes, since the change was not originally intended for the 1.6.x branch.
If you get the team to backport the change to the 1.6.x branch you can run Django from this branch. I wouldn't do this in production, but it is much safer than running from master. This of course would be a temporary solution, before a new minor 1.6.x version comes out.
If you get the team to backport the change to the 1.6.x branch, you can get the 1.6.1 stable version from git, and then manually cherry-pick the change from the 1.6.x branch.
I'm working in two projects, the first one is been developed using django/mysql and the other uses django/mongodb.
The first is using django1.5 and it works but the second only works in django1.3, I believe mongodb does not work in django1.5.
When I try to run the django/mongodb project in django1.5 I get:
AttributeError: 'tuple' object has no attribute 'insert'
How can I solve it? can I install both django(1.3 and 1.5) in the same computer and use them for some different projects?
I'm a newbie with mongodb.
Thanks in advance.
Finally I installed both django1.5 to use mysql and 1.3 to use mongodb.
I got it using virtualenv
Here a bit tutorial(In spainsh)
http://plone-spanish-docs.readthedocs.org/en/latest/python/creacion_entornos_virtuales.html