I know this has been asked here a million times before, 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
Traceback (most recent call last):
File "C:\Django-1.1.1\setup.py", line 69, in <module>
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 :)
On Sat, Nov 7, 2009 at 4:15 PM, Zeynel <azeyn...@gmail.com> wrote:
> Hello,
> I know this has been asked here a million times before, 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 > Traceback (most recent call last): > File "C:\Django-1.1.1\setup.py", line 69, in <module> > version = __import__('django').get_version() > ImportError: No module named django
Is there a django directory under c:\Django-1.1.1? There should be. There should also be an __init__.py in that directory. If either of these are missing then likely the problem is whatever tool was used to unpack the tar.gz file. A tool that correctly unzips 0-byte files is required -- I've seen reports before of some Windows tools not handling these properly.
Great! Thank you very much. I downloaded django-1.1.1 again and
untarred again.
django directory is in C:\Django-1.1.1\Django-1.1.1\django....
I don't know why I got 2 Django-1.1.1 folders but installation worked
this time.
There are many __init.py__ files, they are in build directory.
I did the installation as "setup.py install" instead of "python
setup.py install" so the tutorial says that django-admin.py may not be
in the system path.
Now I am going to create a project. Should I create it in the second
Django-1.1.1 folder?
Thanks again!
On Nov 7, 4:55 pm, Karen Tracey <kmtra...@gmail.com> wrote:
> On Sat, Nov 7, 2009 at 4:15 PM, Zeynel <azeyn...@gmail.com> wrote:
> > Hello,
> > I know this has been asked here a million times before, 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
> > Traceback (most recent call last):
> > File "C:\Django-1.1.1\setup.py", line 69, in <module>
> > version = __import__('django').get_version()
> > ImportError: No module named django
> Is there a django directory under c:\Django-1.1.1? There should be. There
> should also be an __init__.py in that directory. If either of these are
> missing then likely the problem is whatever tool was used to unpack the
> tar.gz file. A tool that correctly unzips 0-byte files is required -- I've
> seen reports before of some Windows tools not handling these properly.
> Great! Thank you very much. I downloaded django-1.1.1 again and
> untarred again.
> django directory is in C:\Django-1.1.1\Django-1.1.1\django....
> I don't know why I got 2 Django-1.1.1 folders but installation worked
> this time.
> There are many __init.py__ files, they are in build directory.
> I did the installation as "setup.py install" instead of "python
> setup.py install" so the tutorial says that django-admin.py may not be
> in the system path.
> Now I am going to create a project. Should I create it in the second
> Django-1.1.1 folder?
> Thanks again!
> On Nov 7, 4:55 pm, Karen Tracey <kmtra...@gmail.com> wrote:
> > On Sat, Nov 7, 2009 at 4:15 PM, Zeynel <azeyn...@gmail.com> wrote:
> > > Hello,
> > > I know this has been asked here a million times before, 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
> > > Traceback (most recent call last):
> > > File "C:\Django-1.1.1\setup.py", line 69, in <module>
> > > version = __import__('django').get_version()
> > > ImportError: No module named django
> > Is there a django directory under c:\Django-1.1.1? There should be. There
> > should also be an __init__.py in that directory. If either of these are
> > missing then likely the problem is whatever tool was used to unpack the
> > tar.gz file. A tool that correctly unzips 0-byte files is required -- I've
> > seen reports before of some Windows tools not handling these properly.
> On 8 Kasım, 00:49, Zeynel <azeyn...@gmail.com> wrote:
> > Great! Thank you very much. I downloaded django-1.1.1 again and
> > untarred again.
> > django directory is in C:\Django-1.1.1\Django-1.1.1\django....
> > I don't know why I got 2 Django-1.1.1 folders but installation worked
> > this time.
> > There are many __init.py__ files, they are in build directory.
> > I did the installation as "setup.py install" instead of "python
> > setup.py install" so the tutorial says that django-admin.py may not be
> > in the system path.
> > Now I am going to create a project. Should I create it in the second
> > Django-1.1.1 folder?
> > Thanks again!
> > On Nov 7, 4:55 pm, Karen Tracey <kmtra...@gmail.com> wrote:
> > > On Sat, Nov 7, 2009 at 4:15 PM, Zeynel <azeyn...@gmail.com> wrote:
> > > > Hello,
> > > > I know this has been asked here a million times before, 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
> > > > Traceback (most recent call last):
> > > > File "C:\Django-1.1.1\setup.py", line 69, in <module>
> > > > version = __import__('django').get_version()
> > > > ImportError: No module named django
> > > Is there a django directory under c:\Django-1.1.1? There should be. There
> > > should also be an __init__.py in that directory. If either of these are
> > > missing then likely the problem is whatever tool was used to unpack the
> > > tar.gz file. A tool that correctly unzips 0-byte files is required -- I've
> > > seen reports before of some Windows tools not handling these properly.
|
