Thanks for the suggestions. I had stopped Apache, and I also tried a fresh
install in a new virtualenv.
That actually helped me discover the root cause of the problem because I
got a different traceback during a fresh install. Pasting it here in case
others run into the same problem someday:
Or clone into a new virtualenv (you are using virtualenv, aren't you, and
you are using requires.txt and pip, and your code is in revision control,
right?), then change the Apache configuration to use the new VE and restart.
On Wed, Feb 17, 2016 at 7:00 AM, Mike Dewhirst
wrote:
> Try stopping Ap
Try stopping Apache during the upgrade. I need to do that on Ubuntu.
Good luck
Connected by Motorola
Tanuka Dutta wrote:
>
>
>
>
>down votefavorite
>
>Hello,
>
>I have a Linux CentOS 6.7 installation on a VM. A few months ago, I had -
>compiled and installed Python 2.7.8 on it - installed vi
Try sto
Connected by Motorola
Tanuka Dutta wrote:
>
>
>
>
>down votefavorite
>
>Hello,
>
>I have a Linux CentOS 6.7 installation on a VM. A few months ago, I had -
>compiled and installed Python 2.7.8 on it - installed virtualenv-13.1.2 in
>/usr/lib/python2.7/site-packages - installed Django
4 matches
Mail list logo