On Fri, Dec 25, 2009 at 8:26 PM, Michael Jenkinson <[email protected]>wrote:
> hi > > put the complte path to it and it worked. guess the path isnt set right > somewhere. thanks anyway > > when the tutorial says one thing and it doesnt work one starts to wonder > why. hence the original query. sorry if I got you frustrated too, it wasnt > my intention. > > If your hope is to get help, you'll have better luck here in the future if you are more specific about the problem you are having, exactly. "The pathing is haywire" does not give anyone here much to work with. What path? System path to regular executables? Python path? Even here you don't mention the actual command you were having trouble with, but I'm guessing it is django-admin.py. If so, the problem is not that the the path isn't set right but rather that Debian (upon which Ubuntu is based), for its packages, apparently prohibits scripts installed in the path from including the script extension in their name. Thus instead of installing django-admin.py somewhere in the path, the package-installed version of Django has something named simply django-admin. That packaging change is unfortunate since it causes problems for people using a package install trying to follow the online docs. Perhaps the online doc could mention the possibility that a package-installed version might have done something like this, though it's a bit unattractive to start down this path. As it is the online doc describes what Django itself ships and does not attempt to account for whatever changes packagers may have made. Karen -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
