Code

#19958 closed Bug (invalid)

django-admin.py startproject [projectname] does not create manage.py

Reported by: gabriel_wolmarans@… Owned by: nobody
Component: Python 3 Version: 1.5
Severity: Release blocker Keywords: manage.py
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

I've downloaded and installed Django 1.5. I then created a new project using startproject, and guess what, no manage.py? What's up guys?

Attachments (1)

Django102.png (47.3 KB) - added by gabriel_wolmarans@… 17 months ago.
PowerShell

Download all attachments as: .zip

Change History (6)

comment:1 Changed 17 months ago by carljm

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to needsinfo
  • Status changed from new to closed

I don't know, you tell me :-) Startproject works fine here in Python 3, it does generate a manage.py. So at the very least we'll need full reproduction instructions (preferably a pasted shell session showing exactly what you did). Reopen when you provide additional details.

Changed 17 months ago by gabriel_wolmarans@…

PowerShell

comment:2 Changed 17 months ago by gabriel_wolmarans@…

  • Resolution needsinfo deleted
  • Status changed from closed to new
  • Summary changed from django-admin.py startproject [projectname] does not creat manage.py to django-admin.py startproject [projectname] does not create manage.py

Windows PowerShell
Copyright (C) 2009 Microsoft Corporation. All rights reserved.

PS C:\Users\Gabriel> cd d:\GitHub\Python\Django\
PS D:\GitHub\Python\Django> django-admin.py startproject Django102
PS D:\GitHub\Python\Django> cd Django102
PS D:\GitHub\Python\Django\Django102> dir

Directory: D:\GitHub\Python\Django\Django102

Mode LastWriteTime Length Name


d---- 2013/03/01 06:21 PM Django102

PS D:\GitHub\Python\Django\Django102> cd Django102
PS D:\GitHub\Python\Django\Django102\Django102> dir

Directory: D:\GitHub\Python\Django\Django102\Django102

Mode LastWriteTime Length Name


-a--- 2013/03/01 06:21 PM 5543 settings.py
-a--- 2013/03/01 06:21 PM 582 urls.py
-a--- 2013/03/01 06:21 PM 1168 wsgi.py
-a--- 2013/03/01 06:21 PM 0 init.py

PS D:\GitHub\Python\Django\Django102\Django102>

comment:3 Changed 17 months ago by carljm

Thanks for the extra info, and the report.

How did you install Django?

Can you open up a Python shell and type import django; django.__file__ to see where Django is installed? And then go to that location, and go into the django\conf\project_template subdirectory - do you see a manage.py file there?

Do you see this problem only with Python 3, or also with Python 2 (if you have the ability to test with both)?

comment:4 Changed 17 months ago by gabriel_wolmarans@…

I've checked both 33 & 27 directories, and found the 'manage.py' file.

But I found and deleted a django directory without the 'mangage.py' in my 'C://Python27/Lib' directory
that was causing the problem.

It works fine now.

My bad, so sorry for the inconvenience and false alarm.

comment:5 Changed 17 months ago by anonymous

  • Resolution set to invalid
  • Status changed from new to closed

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.