that folder is empty too. On Apr 30, 3:40 pm, christian verkerk <christianverk...@gmail.com> 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... > > On Apr 30, 4:34 pm, shofty <m...@shofty.me> wrote: > > > > > > > > > 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 that a version will be taken down if > > there is a security issue? or am i making that up?
-- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
