Opened 8 years ago

Closed 7 years ago

Last modified 5 years ago

#3245 closed defect (fixed) error on windows when installing from a second level directory

Reported by: dall Owned by: nobody
Component: Uncategorized Version:
Severity: normal Keywords: windows installation
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:


D:\django_src> install
running install
running build
running build_py
error: package directory '\django' does not exist

Attachments (0)

Change History (11)

comment:1 Changed 8 years ago by ramiro <rm0 _at_>


What version of Django are you trying to install?. What are the contents of the D:\django_src directory?

comment:2 Changed 7 years ago by jacob

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

We'll need a lot more information -- Windows version, Python version, etc. -- to even start to fix this. You zhould probably also try django-users before reporting this as a bug.

comment:3 Changed 7 years ago by wfifi

  • Component changed from to Uncategorized

windows install must change line 24

package = dirpath[len_root_dir:].lstrip('/').replace('/', '.')


package = dirpath[len_root_dir:].lstrip('
', '.')

comment:4 Changed 7 years ago by Michael Radziej <mir@…>

  • Keywords windows installation added
  • Summary changed from error on windows to error on windows when installing from a second level directory
  • Triage Stage changed from Unreviewed to Accepted

OK, this makes sense. It seems to happen only when you install it in a second level directory. I cannot check this, but for Windows you'll probably need the same path treatment as for unix. Of course, the replacements from the preceding comment must do the replacements both for unix ('/') and for windows ('

comment:5 Changed 7 years ago by Simon G. <dev@…>

  • Resolution invalid deleted
  • Status changed from closed to reopened

#4082 looks like a duplicate.

comment:6 Changed 7 years ago by mtredinnick

I have a feeling this might have been fixed in [4912]. Could you check if the problem still exists with a recent subversion checkout?

comment:7 follow-up: Changed 7 years ago by Simon G. <dev@…>

#4182 appears to be a duplicate.

comment:8 in reply to: ↑ 7 Changed 7 years ago by Gary Wilson <gary.wilson@…>

Replying to Simon G. <>:

#4182 appears to be a duplicate.

I believe you mean #4128.

comment:9 Changed 7 years ago by anonymous

I had this same problem when trying to install Django from a folder on my Desktop (Windows XP). Changing the slashes on line 24 fixed it.

comment:10 Changed 7 years ago by mtredinnick

  • Resolution set to fixed
  • Status changed from reopened to closed

All the evidence here points to people using versions prior to [4912] -- such as Django 0.96.

comment:11 Changed 7 years ago by Jason <romain_hardouin@…>

Replying to wfifi:

This hack makes works fine on my winXP/Py2.5/Django-0.96.1
Thanx guy

Add Comment

Modify Ticket

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

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

Note: See TracTickets for help on using tickets.