is there something wrong with the packages at whatever server they are
hosted?
pip install upgrade django==1.3 -E envname just isnt working.
installed django into the virtualenv just this morning and its put
1.2.3 in there. can get it to upgrade to 1.3 at all.
if i recall theres a possibility th
just managed to install 1.3 on my mac, so i guess the problem is on
the debian vps.
is there some sort of package manager i need to point somewhere else?
i'll go do a google.
On Apr 30, 3:34 pm, shofty wrote:
> is there something wrong with the packages at whatever server they are
> hosted?
>
> p
Sometimes virtualenv does not delete an existing install out of the
MY_ENV/build directory causing an upgrade to fail. delete that build
directory and try again.
Also using sudo can somethings screw things up...
On Apr 30, 4:34 pm, shofty wrote:
> is there something wrong with the packages at wh
nah, theres something else going on here, i've successfully
uninstalled then downloaded 1.3 with pip but when i open up the
settings file, the staticfiles stuff and the logging stuff are
missing.
used pip install django==1.3 -E envname
but on the mac its definitely brought down the right version.
that folder is empty too.
On Apr 30, 3:40 pm, christian verkerk
wrote:
> Sometimes virtualenv does not delete an existing install out of the
> MY_ENV/build directory causing an upgrade to fail. delete that build
> directory and try again.
>
> Also using sudo can somethings screw things up...
>
>
recreated the virtualenv from scratch totally, still got the same
result. what am i doing wrong here? really cant work it out.
On Apr 30, 4:11 pm, shofty wrote:
> that folder is empty too.
>
> On Apr 30, 3:40 pm, christian verkerk
> wrote:
>
>
>
>
>
>
>
> > Sometimes virtualenv does not delete a
El 30/04/11 18:06, shofty escribió:
> recreated the virtualenv from scratch totally, still got the same
> result. what am i doing wrong here? really cant work it out.
Exactly what is the output?
What is the content of $HOME/.pip/pip.log?
$ cat $HOME/.pip/pip.log
Also, I don't understand what y
1.3.0 final
and this time after a clean reinstall, django-admin has indeed created
the settings file i was expecting.
i think im coming round to the idea that i might have django installed
outside of the virtualenvs and somehow the settings.py was created
from that.
On Apr 30, 6:11 pm, Andres Lu
its just dawned on me what i've done.
forgot to add the lines into the top of the django-admin.py to
activate the virtualenv when it is used
tjhanks for the help guys.
On Apr 30, 6:11 pm, Andres Lucena wrote:
> El 30/04/11 18:06, shofty escribi :
>
> > recreated the virtualenv from scratch tota
You shouldn't have to. Django should be installed within the virtualenv --
that's kind of the point of virtualenv.
You can have any versions of any Python packages (like Django) without any
effect on your OS's Python installation or other virtualenvs.
--
You received this message because you are
10 matches
Mail list logo
