Re: Problems installing a Django package

Throwing away virtualenv is actually best way to get problems (unless you're working with solutions like docker or vagrant). Virtualenv makes easy to check that you really do have only certain packages, certain versions and they won't generate any sudden surprises. On Thu, 13 Aug 2015 04:27:02

Re: Problems installing a Django package

I use no virtualenv, to throw away solutions in that direction.. (didn't wanna to go hard first time). *pip* is only installed in 3.2, so that wasn't the problem. I've solved the problem right now, but after an hour of trial and error, I think the only think was to do *--upgrade wheel*. Is was

Re: Problems installing a Django package

Is wheel in latest version? Also your wheel package is installed in wheel in /usr/local/lib/python3.2/dist-packages but the django-muro-humoristas is being installed in /home/rompepc/.local/lib/python3.2/site-packages So have you activated a virtualenv ? Also i tried to installed a

Problems installing a Django package

I did the tutorial for reusable apps for Django. All went well... but then I get problems when installing the app. Processing ./django-muro_humoristas/dist/django-muro_humoristas-1.tar.gz Requirement already satisfied (use --upgrade to upgrade): django-muro-humoristas==1 from

Having problems installing Heroku database

Trying to get started with Django. My tutorial tells me to run pip install dj-database-url. When I do that, I get: postgres@precise64:/vagrant/projects2/microblog$ pip install dj-database-url Downloading/unpacking dj-database-url Cannot fetch index base URL http://pypi.python.org/simple/ Could

Re: Problems installing my first django app

use command whereis django-admin.py (ubuntu, fedora, centos etc) put this on folder /usr/local/bin. if whereis result not found use another command: find / -iname 'django-admin*'and you will see all files that begin with django-admin (* is coringa) Em domingo, 12 de maio de 2013

Problems installing my first django app

I've followed the tutorial for building my first app on django. I run all the comands via ssh to my remote server. I make a directory on my server into 'public_html' default directory. Then on this folder I run the comand django-admin.py startproject mysite When I try to run the manage.py...it

Re: Problems installing south as part of django-cms

Check whether the toolbar directory has __init__.py in it. Then try from cms.middleware import toolbar On Fri, Dec 10, 2010 at 12:20 AM, wilbur wrote: > I have checked my python path, and I see: > > /usr/local/lib/python2.6/dist-packages/django_cms-2.1.0.beta3- > py2.6.egg > >

Re: Problems installing south as part of django-cms

I have checked my python path, and I see: /usr/local/lib/python2.6/dist-packages/django_cms-2.1.0.beta3- py2.6.egg as one of the directories. If i point to the module I want with: 'cms.middleware.toolbar.ToolbarMiddleware',(##and this path DOES exist in the directory structure) in my

Re: Problems installing south as part of django-cms

Hi, the problem look to be that cms is not in your python path. It should work without hard copying it in other directory. Are you able to import this middleware from the python interpeter? If not check your python path. On Thu, Dec 9, 2010 at 11:25 PM, wilbur wrote: > Hello and

Re: Problems installing south as part of django-cms

Hello and thank you, Removing south worked fine. I initially had problems loading middleware classes to settings.py for the following: #'cms.middleware.page.CurrentPageMiddleware', #'cms.middleware.user.CurrentUserMiddleware', #'cms.middleware.toolbar.ToolbarMiddleware',

Re: Problems installing south as part of django-cms

The simplest solution: remove south from the list of installed application, run ./manage.py syncdb this will create you tables the way thay have to be and everything will be ok. This will not fix your south problem, but will allow you to use django cms. If you later fix the south, just run

Problems installing south as part of django-cms

Hello, I am having a hell of a time getting Django-CMS up and running. I am using Django 1.1.1, and South 0.7.3 (by way of using easy_install south systemwide, though my Ubuntu synaptic package manager says 0.6-1) on Ubuntu 10.04 (Lucid). I am following the CMS tutorial at

Re: Problems installing

Anyone have any ideas? Would love to get this install off the ground... -Andy On Nov 5, 1:24 pm, "skipmartin" <[EMAIL PROTECTED]> wrote: > Tearing my hair out here... > > Getting a "400 - Bad Request" > > I've done everything I can find in any tutorial... please help! Trying > to run on Apache

Problems installing

Tearing my hair out here... Getting a "400 - Bad Request" I've done everything I can find in any tutorial... please help! Trying to run on Apache 1.3 with FastCGI In my httpd.conf FastCGIExternalServer

Re: Problems installing django

That was it ..after removing the old python all is ok --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To

Re: Problems installing django

fixing the indention resovled the error there...thanks when I import array, cPickle I received the error again Mod_python error: "PythonHandler mptest" Traceback (most recent call last): File "/usr/lib/python2.3/site-packages/mod_python/apache.py", line 287, in HandlerDispatch

Re: Problems installing django

On Mon, 2006-02-27 at 16:17 -0800, [EMAIL PROTECTED] wrote: > Both import array and import cPicke import with no problems from > command line > > To test further, I set up a quick hello world test outside of django > using > > > AddHandler mod_python .py > PythonHandler mptest >

Re: Problems installing django

Both import array and import cPicke import with no problems from command line To test further, I set up a quick hello world test outside of django using AddHandler mod_python .py PythonHandler mptest PythonDebug On and placing the following contents in test: from mod_python import

Re: Problems installing django

On Mon, 2006-02-27 at 15:13 -0800, [EMAIL PROTECTED] wrote: > I'm using Apache 2x and Python 2.3 ... using /mysite/ when I open the > page in the browser I get the following message: > > ImproperlyConfigured: Could not load database backend: > /usr/lib/python2.3/lib-dynload/arraymodule.so:

Problems installing django

I'm using Apache 2x and Python 2.3 ... using /mysite/ when I open the page in the browser I get the following message: ImproperlyConfigured: Could not load database backend: /usr/lib/python2.3/lib-dynload/arraymodule.so: undefined symbol: PyUnicodeUCS4_FromUnicode. Is your DATABASE_ENGINE