all last):
File "C:\Django-1.1.1\setup.py", line 69, in
version = __import__('django').get_version()
ImportError: No module named django
I was very excited to start studying the tutorial but couldn't even
install it :)
Thank you
--~--~-~--~~~-
Ok, so I've managed to get django running using mod_python on some other
machines, but today I'm being stymied:
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send ema
t;, line 1, in
import django
ImportError: No module named django
Would you please give me help some advice what to do here? Many thanks.
--
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@g
> windows shell:
>
> C:\Django-1.1.1>setup.py install
> Traceback (most recent call last):
> File "C:\Django-1.1.1\setup.py", line 69, in
>version = __import__('django').get_version()
> ImportError: No module named django
>
>
Is there a django di
e this out. This is the error message on the
> > windows shell:
>
> > C:\Django-1.1.1>setup.py install
> > Traceback (most recent call last):
> > File "C:\Django-1.1.1\setup.py", line 69, in
> > version = __import__('django').get_version()
> > > windows shell:
>
> > > C:\Django-1.1.1>setup.py install
> > > Traceback (most recent call last):
> > > File "C:\Django-1.1.1\setup.py", line 69, in
> > > version = __import__('django').get_version()
> > > I
but I couldn't
> > > > find the right answer. It seems something to do with PYTHONPATH. Can
> > > > anyone help me figure this out. This is the error message on the
> > > > windows shell:
>
> > > > C:\Django-1.1.1>setup.py install
> >
Hi all,
Totally new to django and just trying to get it installed but I keep
getting the "ImportError: No module named django" error. I've searched
around quite a bit looking for the answer to my problem but nothing seems
to work.
I'm running python vers 2.7.2 and hav
I installed Django on my iMac running Lepoard. I installed the
official release and followed the instructions, but when I try to
import Django to Python I get the following message:
"ImportError No module named django" on top of this, I now have 2
Python folders version 2.5.
Has anyo
thonHandler django.core.handlers.modpython
#SetEnv DJANGO_SETTINGS_MODULE trainspotted.settings
PythonDebug On
PythonPath "sys.path"
Of course, now when I go to my apache site I get:
Mod_python error: "PythonHandler django.core.handlers.modpython"
Traceback (m
directory and run "./manage.py
syncdb", I get this error:
ImportError: No module named django
I'm running Python 2.4.3 in case that matters - any ideas?
Thanks,
Craig
--~--~-~--~~~---~--~~
You received this message because you are subscribed to t
I have poked around looking for an answer to this and none of the
suggestions/fixes I found did the trick.
Ubuntu 6.06/Python
2.4.3/Apache2.0.55/mod_python3.1.4/mySQL5.0.22/Django0.95
Relevant bits to follow
httpd.conf:
SetHandler mod_python
PythonHandler django.core.hand
I'm getting this error
Traceback (most recent call last):
File "C:/Users/lenovo/Desktop/Django Projects/telusko/telusko/urls.py",
line 16, in
from django.contrib import admin
*ModuleNotFoundError: No module named 'django'*
could someone please help in resolving
Err, sorry, I meant to cancel and sent this instead. I believe I found my
problem while preparing to email about this (wasn't looking close enough
at the error message, and it looks like apache was looking in the wrong
python's site-packages)
On Thu, 2 Apr 2009, Jeff Gentry wrote:
>
> Ok, so I
nterpreter and typing import django"
>
> I assume that the "Python interactive interpreter" is IDLE (Python
> GUI). When i run it and on the command line I write "import django", I
> get a message as follwoing:
> >>> import django
> Traceback (most re
> > interpreter and typing import django"
>
> > I assume that the "Python interactive interpreter" is IDLE (Python
> > GUI). When i run it and on the command line I write "import django", I
> > get a message as follwoing:
> > >>>
stalled by running the Python interactive
> > > interpreter and typing import django"
> >
> > > I assume that the "Python interactive interpreter" is IDLE (Python
> > > GUI). When i run it and on the command line I write "import django",
start with a tutorial on the Djangos website which
>> > > says:
>> > > "You can tell Django is installed by running the Python interactive
>> > > interpreter and typing import django"
>> >
>> > > I assume that the "Python interactive inte
On Mon, Apr 15, 2013 at 12:40 PM, Starboy wrote:
> Hi all,
>
> Totally new to django and just trying to get it installed but I keep getting
> the "ImportError: No module named django" error. I've searched around quite
> a bit looking for the answer to my problem but
This is likely the cause of the problem. You should always install
packages with setup.py (as mentioned by the previous poster). I've found
Mac OS X to have lots of "false" site-packages folders. setup.py will
make sure it gets to the correct one. Also some packages may have extra
installation step
Yep, I'm on 10.8.3. I tried sudo python setup.py install and it asked for a
password. I assumed it was just looking for my system password but that
didn't work.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and s
On Mon, Apr 15, 2013 at 2:02 PM, Nathan Hall wrote:
>
> Yep, I'm on 10.8.3. I tried sudo python setup.py install and it asked for
> a password. I assumed it was just looking for my system password but that
> didn't work.
It's asking for your own password.
--
You received this message because yo
I tried my password, it doesn't work.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send emai
On Mon, Apr 15, 2013 at 2:24 PM, Nathan Hall wrote:
> I tried my password, it doesn't work.
Go to System Preferences, Users and Groups. Is your account an Admin
account? If not, you can't sudo. You'll need someone with an admin
account to install it for you. But if you don't have an admin account
Yep, I've got admin access, it's my personal machine.
Actually, I looked again and it may not have been a password issue, this
was the message I received: "python: can't open file 'setup.py': [Errno 2]
No such file or directory"
On Mon, Apr 15, 2013 at 4:29 PM, Larry Martell wrote:
> On Mon, Apr
On Mon, Apr 15, 2013 at 2:34 PM, Nathan Hall wrote:
> Yep, I've got admin access, it's my personal machine.
>
> Actually, I looked again and it may not have been a password issue, this was
> the message I received: "python: can't open file 'setup.py': [Errno 2] No
> such file or directory"
Then y
doesn't pip and virtualenv work on mac?
On Mon, Apr 15, 2013 at 11:37 PM, Larry Martell wrote:
> On Mon, Apr 15, 2013 at 2:34 PM, Nathan Hall wrote:
> > Yep, I've got admin access, it's my personal machine.
> >
> > Actually, I looked again and it may not have been a password issue, this
> was
>
I've never used pip or virtualenv.
When I did this: tar xzvf Django-1.5.1.tar.gz
I got this:
tar: Error opening archive: Failed to open 'Django-1.5.1.tar.gz'
On Mon, Apr 15, 2013 at 4:40 PM, Avraham Serour wrote:
> doesn't pip and virtualenv work on mac?
>
>
> On Mon, Apr 15, 2013 at 11:37 P
On Mon, Apr 15, 2013 at 2:47 PM, Nathan Hall wrote:
> I've never used pip or virtualenv.
>
> When I did this: tar xzvf Django-1.5.1.tar.gz
>
> I got this:
> tar: Error opening archive: Failed to open 'Django-1.5.1.tar.gz'
Then either you're not in the directory it was downloaded to
(typically ~/D
Are you in the same directory as Django-1.5.1.tar.gz?
_Nik
On 4/15/2013 1:47 PM, Nathan Hall wrote:
> I've never used pip or virtualenv.
>
> When I did this: tar xzvf Django-1.5.1.tar.gz
>
> I got this:
> tar: Error opening archive: Failed to open 'Django-1.5.1.tar.gz'
>
>
>
> On Mon, Apr 15, 201
Ok, that was it, being completely unfamiliar with the Mac Terminal, I was
in the wrong directory. I navigated to the proper directory and got it
installed. Thanks for the help guys!
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe
ll, it showed the
following error message:
Traceback (most recent call last):
File "", line 1, in
import django
ImportError: No module named django
I searched over the internet and did not find useful information.
Please help.
Many thanks in advance.
--
You received this
Thank you to anyone who may be of help...
PROBLEM:
ImportError: No module named django
MY SETTINGS:
/Working/django/django/__init__.py (file exists)
/Working/projects/ (my main project
folder)
/Working/projects/mysite('mysite' proj
How did you exactly install it?
Which folders are in your PYTHONPATH?
Juanjo
--
mi blog: http://www.juanjoconti.com.ar
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, se
Hi,
This means that Django is not in the PYTHONPATH. To check what's in
that path, run the following in Python:
>>> import sys
>>> print sys.path
On Jul 9, 9:35 am, Juanjo Conti <[EMAIL PROTECTED]> wrote:
> How did you exactly install it?
> Which folders are in your PYTHONPATH?
>
> Juanjo
> --
Ok, for the PYTHONPATH I got:
>>> import sys
>>> print sys.path
['', '/System/Library/Frameworks/Python.framework/Versions/2.5/lib/
python25.zip', '/System/Library/Frameworks/Python.framework/Versions/
2.5/lib/python2.5', '/System/Library/Frameworks/Python.framework/
Versions/2.5/lib/python2.5/pl
Apparently Django is not present in the PYTHONPATH and therefore not
reachable by Python.
I'm not a Mac user, but some help can be found on google.
Try there for example:
http://antoniocangiano.com/2007/12/22/how-to-install-django-with-mysql-on-mac-os-x/
http://www.rhonabwy.com/wp/2006/07/20/inst
Thanks for the links I'll check them out
One last question, I re-did the installation for Django using some
instructions I found on Google. When I open Python now and type:
>>> import.django
>>> django.VERSION
>>> (0,96 ) "There's something else after the 0, 96 but I can't remember what
>>> it
Yes, the install worked. If you can import a module without error,
it's installed successfully.
Mostly. ;) You can also successfully import a module even if it is
not on PYTHON_PATH, if you are in the same directory as the module.
---Peter Herndon
On 7/9/08, MadMax007 <[EMAIL PROTECTED]> wro
Great!
and I just want to say thank you to everyone that helped me with this
problem, it is very much appreciated.
On Jul 9, 6:03 pm, "Peter Herndon" <[EMAIL PROTECTED]> wrote:
> Yes, the install worked. If you can import a module without error,
> it's installed successfully.
>
> Mostly. ;) Yo
ks good! So I now went to add this into my Apache config:
>
>
> SetHandler python-program
> PythonHandler django.core.handlers.modpython
> #SetEnv DJANGO_SETTINGS_MODULE trainspotted.settings
> PythonDebug On
> PythonPath "sys.path"
>
>
>
ceback (most recent call last):
File "", line 1, in ?
ImportError: No module named django
>>> import sys
>>> sys.path
['', '/usr/lib/python24.zip', '/usr/lib/python2.4', '/usr/lib/
python2.4/plat-linux2', '/usr/lib/python2.
apache python
> Password:
> Python 2.4.3 (#1, Mar 14 2007, 18:51:08)
> [GCC 4.1.1 20070105 (Red Hat 4.1.1-52)] on linux2
> Type "help", "copyright", "credits" or "license" for more information.>>>
> import django
>
> Tr
Password:
> Python 2.4.3 (#1, Mar 14 2007, 18:51:08)
> [GCC 4.1.1 20070105 (Red Hat 4.1.1-52)] on linux2
> Type "help", "copyright", "credits" or "license" for more information.>>>
> import django
>
> Traceback (most recent call
;, "credits" or "license" for more information.>>>
> import django
>
> Traceback (most recent call last):
> File "", line 1, in ?
> ImportError: No module named django>>> import sys
> >>> sys.path
>
> ['', '/usr/
On 28 Jun 2006, at 14:39, Craig Marshall wrote:
> I can run python interactively and type "import django" and get no
> errors, but when I go into our project directory and run "./manage.py
> syncdb", I get this error:
>
> ImportError: No module named django
&
> It sounds like you might have two versions of Python installed. You
> should confirm that the shebang line in ./manage.py is for the right
> version. Alternatively, running 'python manage.py syncdb' should work.
The shebang says "#!/usr/bin/env python", which returns 2.4.3 when
asked. (So does
t when I go into our project directory and run "./manage.py
> syncdb", I get this error:
>
> ImportError: No module named django
Is this the best place to ask this kind of question, or would I be
better off trying irc or something else?
Thanks,
Craig
--~--~-~--~~
nstalled Ubuntu completely on top
of Debian and then installed Django from SVN again? You're not being
explicit enough.
> I can run python interactively and type "import django" and get no
> errors, but when I go into our project directory and run "./manage.py
> syncdb", I
> This is very strangely worded. You installed Ubuntu completely on top
> of Debian and then installed Django from SVN again? You're not being
> explicit enough.
Sorry for being unclear. I had debian sarge installed, and I installed
django from svn at that point. Then I wiped my machine entirely,
On 6/30/06, Craig Marshall <[EMAIL PROTECTED]> wrote:
> Only the symlink I made called "django" which points to the actual
> django dir in my $HOME
I'd advise you to drop the symlink and use the PYTHONPATH variable,
but that's just my hunch based on no empirical data.
--
Jeroen Ruigrok van der
> I'd advise you to drop the symlink and use the PYTHONPATH variable,
> but that's just my hunch based on no empirical data.
Okay, I just deleted /usr/lib/python2.4/site-packages/django (which
was the symlink), and added to the PYTHONPATH environment variable the
actual django directory, and if f
On 6/30/06, Craig Marshall <[EMAIL PROTECTED]> wrote:
> I can
> import django at the python prompt, but running syncdb gives me the
> ImportError.
What does python -v manage.py yield? 't Will be a long output.
Probably best to put it up on a URL if you can.
--
Jeroen Ruigrok van der Werven
--~
On Mon, 2006-07-17 at 03:57 -0700, markguy wrote:
> I have poked around looking for an answer to this and none of the
> suggestions/fixes I found did the trick.
>
> Ubuntu 6.06/Python
> 2.4.3/Apache2.0.55/mod_python3.1.4/mySQL5.0.22/Django0.95
>
> Relevant bits to follow
> httpd.conf:
>
>
I'm covering all the bases. Or trying to.
re: django_source: Wow. Uh, thanks. I have no idea why I typed that out
fully in httpd.conf. Fixing that leads to a new error:
EnvironmentError: Could not import settings 'bbg.settings' (Is it on
sys.path? Does it have syntax errors?): No module named bb
On Mon, 2006-07-17 at 04:43 -0700, markguy wrote:
> I'm covering all the bases. Or trying to.
>
> re: django_source: Wow. Uh, thanks. I have no idea why I typed that out
> fully in httpd.conf. Fixing that leads to a new error:
>
> EnvironmentError: Could not import settings 'bbg.settings' (Is it
Malcolm Tredinnick wrote:
> That should be easy enough to diagnose. My initial guess would be that
> bbg is in django_projects/, rather than django_src/, just from the way
> you named your directories. Remember that .bash_profile is obviously not
> going to be run by Apache (it's not bash, after
y", line
287, in HandlerDispatch
log=debug)
File "/usr/lib/python2.4/site-packages/mod_python/apache.py", line
454, in import_module
f, p, d = imp.find_module(parts[i], path)
ImportError: No module named django
That suggests that mod_python has lost sight of django.
Changing bbg.goods to bbg.goods.url throws the same exception as
bbg.goods.
--~--~-~--~~~---~--~~
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
On Mon, 2006-07-17 at 07:45 -0700, markguy wrote:
> So, what you were *really* suggesting was that PYTHONPATH should
> include the project directory, not the django_src directory? I saw that
> while skimming through the docs.
>
> I changed PYTHONPATH to reflect that (apparently, adding both
> dir
On Mon, 2006-07-17 at 07:34 -0700, markguy wrote:
>
> Malcolm Tredinnick wrote:
>
> > That should be easy enough to diagnose. My initial guess would be that
> > bbg is in django_projects/, rather than django_src/, just from the way
> > you named your directories. Remember that .bash_profile is o
On Mon, 2006-07-17 at 08:22 -0700, markguy wrote:
> Changing bbg.goods to bbg.goods.url throws the same exception as
> bbg.goods.
So inside your project directory, try something like the following (I am
pasting a terminal session using one of my own projects just to show
what sort of output I see
That fixed that particular issue. My unfamiliarity with Python lists
betrayed me there.
--~--~-~--~~~---~--~~
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@googleg
I've got my output at least resembling yours now, thanks to your
explanation about the difference between URL config and apps.
I'm using this for urlpatterns:
( r'^$' , 'django.views.generic.simple.direct_to_template' , {
'template' : 'index.html' } ) ,
However, there's a new wrinkle. While tryi
Okay, ./manage.py syncdb before ./manage.py sql goods is apparently a
good idea.
So, I've now got a very basic index page loading up as expected.
I'm off for a couple drinks to see if I can wrap my head around how
Django compartmentalizes things and then will endeavor to not bring
many more prob
On Mon, 2006-07-17 at 18:58 -0700, markguy wrote:
> I've got my output at least resembling yours now, thanks to your
> explanation about the difference between URL config and apps.
>
> I'm using this for urlpatterns:
> ( r'^$' , 'django.views.generic.simple.direct_to_template' , {
> 'template' :
No module named django someone help me
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this g
(most recent call last):
> File "C:/Users/lenovo/Desktop/Django Projects/telusko/telusko/urls.py",
> line 16, in
> from django.contrib import admin
>
> *ModuleNotFoundError: No module named 'django'*
>
> could someone please help in resolving this
Hi --
I'm attempting to run Django on OSX 10.6. I've installed Python2.5 and
Py25-Django (Django v1.1) via MacPorts. But I am receiving the famed
"ImportError: No module named django" error.
Django is installed in this directory:
/opt/local/lib/python2.5/site-packages/
ost recent call last):
> File "", line 1, in
> import django
> ImportError: No module named django
>
> I searched over the internet and did not find useful information.
>
> Please help.
>
> Many thanks in advance.
>
>
> --
> You received this messa
following error message:
> >
> > Traceback (most recent call last):
> > File "", line 1, in
> > import django
> > ImportError: No module named django
> >
> > I searched over the internet and did not find useful information.
> >
\anaconda\lib\site-package.
> >
> > However, when I run "import django" in Python 2.7.6 shell, it showed the
> > following error message:
> >
> > Traceback (most recent call last):
> > File "", line 1, in
> > import django
in the python shell try running:
import sys
sys.path
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this
django is in your sys.path?
2008/1/16, Scott <[EMAIL PROTECTED]>:
>
>
> Thank you to anyone who may be of help...
>
> PROBLEM:
>
> ImportError: No module named django
>
> MY SETTINGS:
>
> /Working/django/django/__init__.py (file exists)
> /Working/proje
1234,
Yes, with these directives:
SetHandler python-program
PythonPath "['/Working/django','/Working/modules','/Working/
projects','/Working/projects/mysite'] + sys.path"
SetEnv DJANGO_SETTINGS_MODULE mysite.settings
PythonHandler mod_python.testhandler
#PythonH
First verify Django is being picked up from where you think it is by
doing:
import django
print django.__file__
Second, ensure that the installed Django files have permissions that
would allow user that Apache may be running as to access it. That is,
if Apache is running as a service and the
On Jan 15, 2008 6:55 PM, Scott <[EMAIL PROTECTED]> wrote:
> MY SYSTEM:
>
> OS = { Red Hat Enterprise Linux 5 | RHEL 5 | RHEL5 }
> Python 2.4.3 (#1, Dec 11 2006, 11:38:52)
> Apache/2.2.3 (Red Hat) Server
> mod_python.version '3.2.8'
> Django VERSION = (0, 97, 'pre')
>
>From all the information you
On Jan 15, 2008 9:48 PM, Scott <[EMAIL PROTECTED]> wrote:
> /Working/django
Out of curiosity, what are the contents of this directory? Is this the
root of the django distribution (containing things like 'docs',
'tests' and another 'django' directory), or is this the django code
itself (containing
@Graham:
It looks like it is a working django load. Also, the permissions are
the same as when they were able to load while in the python site
packages folder.
---
Python 2.4.3 (#1, Dec 11 2006, 11:38:52)
[GCC 4.1.1 20061130 (Red Hat 4.1.1-43)] on linux2
Type "help", "copyright", "cred
Try pip install django
Marsel Tzatzo,
Mobile Software Engineer
I welcome VSRE emails. Learn more at http://vsre.info/
> On 27 Mar 2018, at 12:48, MFM ™ wrote:
>
> No module named django someone help me
>
> --
>
try : pip install django (if pip is installed)
try : pip3 install django (if pip3 is installed)
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsu
ngo v1.1) via MacPorts. But I am receiving the famed
> "ImportError: No module named django" error.
>
> Django is installed in this directory:
> /opt/local/lib/python2.5/site-packages/django/
>
> To check my $PYTHONPATH, I went to the Python shell and tried "print
&g
Please post the results of these commands:
which python
python -V
You can have different versions of Python installed (or even the same version)
in multiple places on your Mac. The most likely situation is that when you're
trying to actually run things you're using different version of Pyth
Thanks for the reply.
"which python" returns: /opt/local/bin/python
"python -V" returns: Python 2.5.5
I know I've got the OSX default Pythons installed as well, but I've done my
best to avoid running those.
Like I said in my first email, printing sys.path in the python prompt returns a
big li
Printing sys.modules won't show django unless you've imported Django.
What are you trying to do, anyway? You don't normally import Django in a Python
script. You usually start a Django project by using django-admin.py and letting
it create a manage.py which uses the proper Python.
Search your s
Aha, that is helpful. I think I've partially solved this now.
If I run 'import django' at the command line, then it seems to import fine;
there is no error message, and 'print sys.modules' now lists it.
So I tried specifying the site-packages path at the top of my script and it
removed the Impo
Sorry, I should clarify.
When I wrote:
> So I tried specifying the site-packages path at the top of my script...
I meant that I added these lines:
~~
import sys
sys.path.insert(0, "/opt/local/lib/python2.5/site-packages")
~~
=T=
--
You received this message because you are subscribed to the G
On 03/03/2010 07:27 PM, Tim Jones wrote:
So I tried specifying the site-packages path at the top of my script
and it removed the ImportError. That makes it seem like my
web-server's pythong is running with different pythonpath settings
than my command-line's python. I think I can probably unravel
ained that it
didn't have permission.
Good luck,
Steve
On Wed, Mar 3, 2010 at 2:15 PM, Tones wrote:
> Hi --
>
> I'm attempting to run Django on OSX 10.6. I've installed Python2.5 and
> Py25-Django (Django v1.1) via MacPorts. But I am receiving the famed
> &qu
ype import django in the python interpreter, it says No module
named django.
I found someone who had had a similar problem, and I'm guessing it
could be connected to the fact that Lion comes with Python 2.7.1? My
Django version is 1.2.5. Again, I know almost nothing about Python, so
I could be wa
gt; with it. A few weeks ago, I upgraded my mac to run Lion and now, when
> I type import django in the python interpreter, it says No module
> named django.
>
> I found someone who had had a similar problem, and I'm guessing it
> could be connected to the fact that Lion comes
installed
> > Django on my mac (running Snow Leopard). I took me quite some time,
> > but I got it running. After that I didn't get around to doing anything
> > with it. A few weeks ago, I upgraded my mac to run Lion and now, when
> > I type import django in the py
;t get around to doing anything
> > > with it. A few weeks ago, I upgraded my mac to run Lion and now, when
> > > I type import django in the python interpreter, it says No module
> > > named django.
> >
> > > I found someone who had had a similar proble
On Thu, Oct 27, 2011 at 2:43 PM, Andre Terra wrote:
> You can run different versions of python using virtualenv [1]. It is hands
> down the best way to handle multiple python environments.
>
> You can use virtualenvwrapper [2] to automate some of the process. I'm not
> sure how good it is on Mac O
Good luck with installing MySQL-python. You'll probably see an error at some
point that the Module MySQLdb is missing if you use MySQL and don't install
it. Last time, with Snow Leapord, I had to install "Mac Ports" to get it
working.
If you don't want to use the complexity of the virtual environm
On Thu, Oct 27, 2011 at 9:20 AM, Kurtis Mullins
wrote:
> If you don't want to use the complexity of the virtual environment, just run
> "sudo easy_install django" or "sudo pip install django" from your terminal.
> This will install Django system-wide.
the same commands work inside a virtualenv. w
get around to doing anything
> > > with it. A few weeks ago, I upgraded my mac to run Lion and now, when
> > > I type import django in the python interpreter, it says No module
> > > named django.
>
> > > I found someone who had had a similar problem, and I'
Hello Angelika,
As a test you may want to try the defaults command ( for more info "$ man
defaults" and/or google "mac os x defaults" ) to see if your Django install
is still in the site-packages of an older version of python. Try something
like this on the command line...
$ defaults write co
Angelika may not want to get into virtualenv and virtualenvwrapper at this
point. If you're just getting into Python/Django it may be more overhead
than you want to deal with conceptually at this time. If your project is
simple or you're just learning then you may want to wait until you feel t
IMHO, If you can't understand how imports and sys.path work, it's best to
put the Django book aside and read up on the basics of installing and
running Python.
Cheers,
AT
On Thu, Oct 27, 2011 at 1:55 PM, creecode wrote:
> Angelika may not want to get into virtualenv and virtualenvwrapper at th
1 - 100 of 108 matches
Mail list logo
