FYI - (sorry about all the posts)
I edited the django-admin.py file and changed the first line where it
calls for env.
Original: /usr/bin/env
Edited: /bin/env
Now it works just fine. Thank you both!
On May 20, 9:41 am, lorax <[EMAIL PROTECTED]> wrote:
> Re: non-std host setup
>
> Ah.. got it.
Re: non-std host setup
Ah.. got it. Thank you. So I can edit django-admin.py with PICO to
point to where they've located "env" and that should take care of the
issue too.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Grou
That worked!
So adding "python" to the front of the command seems to be the trick.
Perhaps I should add a symlink to point to where Python lives?
On May 20, 9:30 am, Marco Buttu <[EMAIL PROTECTED]> wrote:
> On Tue, 2008-05-20 at 05:23 -0700, lorax wrote:
> > I tried to execute the command djan
On Tue, May 20, 2008 at 9:29 AM, lorax <[EMAIL PROTECTED]> wrote:
>
> Re: break python scripts.
>
> This is my first foray into Python so other than Django, I'm not sure
> what I'd break. And I'm not sure what you mean by patch django-
> admin.py to point to where env is.
>
> Thanks for you help.
On Tue, 2008-05-20 at 05:23 -0700, lorax wrote:
> I tried to execute the command django-admin.py startproject mysite.
> That gave me an error:
>
> -sh: /usr/local/Django-0.96.2/django/bin/django-admin.py: /usr/bin/
> env: bad interpreter: No such file or directory
>
> I thought my symlink might
Re: break python scripts.
This is my first foray into Python so other than Django, I'm not sure
what I'd break. And I'm not sure what you mean by patch django-
admin.py to point to where env is.
Thanks for you help.
On May 20, 9:27 am, lorax <[EMAIL PROTECTED]> wrote:
> Seems it's in /bin/env
Seems it's in /bin/env
On May 20, 9:22 am, "Karen Tracey" <[EMAIL PROTECTED]> wrote:
> On Tue, May 20, 2008 at 9:17 AM, lorax <[EMAIL PROTECTED]> wrote:
>
> > BUT!
>
> > env --help DID work
>
> Hmm. So env is in some non-standard place? What does "which env" show?
>
> You could patch your djang
On Tue, May 20, 2008 at 9:17 AM, lorax <[EMAIL PROTECTED]> wrote:
>
> BUT!
>
> env --help DID work
>
Hmm. So env is in some non-standard place? What does "which env" show?
You could patch your django-admin.py to point to where your host has put
env. It's a bit odd for it not to be in /usr/bin
BUT!
env --help DID work
On May 20, 9:01 am, "Gregg Banse" <[EMAIL PROTECTED]> wrote:
> Hi Karen,
> Thanks for the response.
>
> The system didn't like that command. - No such file or directory.
--~--~-~--~~~---~--~~
You received this message because you are subsc
Hi Karen,
Thanks for the response.
The system didn't like that command. - No such file or directory.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django
On Tue, May 20, 2008 at 8:23 AM, lorax <[EMAIL PROTECTED]> wrote:
>
> I've just got the keys to Django 0.96.2 on a semi-dedicated server at
> WestHost. Largely spurred on by the receipt of the first of 4 Django
> books. I fetched a copy of the download using wget and untarred the
> file right from
I've just got the keys to Django 0.96.2 on a semi-dedicated server at
WestHost. Largely spurred on by the receipt of the first of 4 Django
books. I fetched a copy of the download using wget and untarred the
file right from the command line on the server. I then attempted to
add django-admin.py to
12 matches
Mail list logo
