Missing manage.py

1,980 views
Skip to first unread message

Faeez Abd Rahman

unread,
Apr 16, 2012, 7:26:32 AM4/16/12
to django...@googlegroups.com
Hi,

I have a problem whenever I create a new project using the start project command, no manage.py file is created. 

I'm using Mac OS X. Thank you in advance

andrea mucci

unread,
Apr 16, 2012, 2:16:14 PM4/16/12
to django...@googlegroups.com
hi

could you post
django version
python version
you use virtualenv? if yes what version
and the code you use to generate the project

cheers

> --
> You received this message because you are subscribed to the Google Groups "Django users" group.
> To post to this group, send email to django...@googlegroups.com.
> To unsubscribe from this group, send email to django-users...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

Buddy Lindsey, Jr.

unread,
Apr 16, 2012, 2:17:39 PM4/16/12
to django...@googlegroups.com
If you are using Django 1.4 check in the application folder of your project below your project folder. It should be in there.

Faeez Abd Rahman wrote:

Tonton

unread,
Apr 16, 2012, 2:43:44 PM4/16/12
to django...@googlegroups.com
after project you need to do start app for making module

T.

Faeez Abd Rahman

unread,
Apr 18, 2012, 6:31:58 AM4/18/12
to django...@googlegroups.com
Hi,

Hi,

I'm using Django 1.4, Python 2.7 and nope I did not use virtual env.

Faeez Abd Rahman

unread,
Apr 18, 2012, 6:35:31 AM4/18/12
to django...@googlegroups.com
Hi Buddy,

Nope it's not there, I have tried to create another project, still not there. 

mysite/
    mysite/
        __init__.py
        settings.py
        urls.py
        wsgi.py

I followed the tutorial, so all files created as above, except for manage.py

Faeez Abd Rahman

unread,
Apr 18, 2012, 6:36:52 AM4/18/12
to django...@googlegroups.com
Hi tonton,

without the manage.py, I can't create any apps.

Tom Evans

unread,
Apr 18, 2012, 6:44:16 AM4/18/12
to django...@googlegroups.com
On Wed, Apr 18, 2012 at 11:35 AM, Faeez Abd Rahman
<faeez.a...@gmail.com> wrote:
> Hi Buddy,
>
> Nope it's not there, I have tried to create another project, still not
> there.
>
> mysite/
> mysite/
> __init__.py
> settings.py
> urls.py
> wsgi.py
>
>
> I followed the tutorial, so all files created as above, except for manage.py
>
>

Could you reinstall django please, and try again.

By reinstall, I mean that you should find and completely remove the
django package from your python-packages, and then install it again.
Just installing django over the top of an existing django package may
not behave correctly.

To clarify, when you run "django-admin.py startproject", what happens
is that django copies a stub directory from the installed version of
django to the name specified by startproject. Therefore, if the files
that 'startproject' copies are not correct, it stands to reason that
the issue is that the stub directory does not have the correct files
in it.

I have no idea how this could have happened, but wiping it away and
reinstalling should ensure that the stub directory has the right files
in it.

Cheers

Tom

Faeez Abd Rahman

unread,
Apr 18, 2012, 6:54:50 AM4/18/12
to django...@googlegroups.com
Hi,

I will try to remove and install django as you suggest, but before that I like to look for that stub directory. Where is the location of that stub directory?

thanks.

Tom Evans

unread,
Apr 18, 2012, 7:00:38 AM4/18/12
to django...@googlegroups.com
On Wed, Apr 18, 2012 at 11:54 AM, Faeez Abd Rahman
<faeez.a...@gmail.com> wrote:
> Hi,
>
> I will try to remove and install django as you suggest, but before that I
> like to look for that stub directory. Where is the location of that stub
> directory?
>
> thanks.
>

I don't know the specifics of your OS or how you installed Django, so
I cannot really answer that.

Python packages are stored in a 'site-packages' folder*. On my OS,
that is '/usr/local/lib/python2.7/site-packages'.

In the 'site-packages' folder, there should be a folder called 'django'.

In the 'django' folder, the stub project template is in 'conf/project_template/'

Cheers

Tom

* Or any other folder in your PYTHONPATH

Faeez Abd Rahman

unread,
Apr 18, 2012, 7:28:19 AM4/18/12
to django...@googlegroups.com
I'm using Mac OS X version 10.7.3. I tried installed Django using SVN and download and running the setup.py command, both results in the missing manage.py file.

I manage to find the location of the stub directory 

/project_template
/project_name
_init_.py
_init_.pyc
settings.py
settings.pyc
urls.py
urls.pyc
wsgi.py
wsgi.pyc

so i guess there should be manage.py under the project_template folder then. I try to reinstall Django then and see how it goes.

thanks.


Ramiro Morales

unread,
Oct 4, 2012, 8:59:34 AM10/4/12
to django...@googlegroups.com
I think so. The usual reason for the problem you are experiencing is a
previous installation of Django on top of which the one you are trying
to use was installed without unintalling the older one first *.

So, the recommended action in such cases is to ensure you start with a
clean slate buy removing any and all traces of the old files causing
trouble.

2012/10/4, Django_Newbie <anu...@gmail.com>:
> Hi..
> I am using Django 1.4.1 on Windows 7 and face similar problem. I dont see
> manage.py
>
> All I have is:
> __init__.py
> settings.py
> urls.py
> wsgi.py
>
>
> Is reinstalling Django only option?
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/django-users/-/_GE2ct9_qi0J.
> To post to this group, send email to django...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>

--
Enviado desde mi dispositivo móvil

Ramiro Morales

Laxmikant Gurnalkar

unread,
Oct 4, 2012, 11:20:42 AM10/4/12
to django...@googlegroups.com
you can update, instead of reinstalling.
cheers 
Laxmikant

Matt Schinckel

unread,
Oct 4, 2012, 8:34:08 PM10/4/12
to django...@googlegroups.com
An even better solution is to always work in a virtualenv: that way you can 
easily try out new packages, and not worry about conflicts.

Matt.
Reply all
Reply to author
Forward
0 new messages