-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[solved] ImportError: No module named django_proxy.signals #62
Comments
Need to take a look into this but low on my priority queue right now. sorry. Thanks for being patient and giving Mingus a try. |
I'm afraid that installing mercurial didn't fix the issue for me. Though I'm not sure if I'm doing something wrong. Following the installation instructions doesn't automatically install django, pip downloads it, but I then have to go to the bin/Django folder and run the setup.py install prompt. Then when I come back to run the manage.py syncdb command, I get hit with the django_proxy.signals error. |
@vectorfrog I'm not very active with Mingus these days but if I do get a chance to take a look I'll do my best to clean up this and any other issues I run into. No time estimate on this though. Thanks. |
No Worries monty, I'm rolling with a self created CMS for now. I appreciate all of the great open source CMS systems for django that you and others have placed on github. It's been a great way to learn. |
@vectorfrog do you solve this problem now ? I have met this too. |
Hello i had the same issue of
#44
which throws the "ImportError: No module named django_proxy.signals" error
is very easy to solve just install mercurial because the missing components are on googlecode
so just write
sudo apt-get install mercurial
and repeat the requirements
pip install -r stable-requirements.txt
cheers.
liuggio
The text was updated successfully, but these errors were encountered: