Sorry I misread the question.
To make this work I edited the fabfile:
I changed line 503 to
run("virtualenv -p python3 %s" % env.proj_name)
Then I blew away the python 2.7 environment
fab remove
The created the python 3 environment
fab create
Then redeployed
fab deploy
Hope that helps.
On Monday, April 29, 2019 at 11:47:42 PM UTC-7, Mike Dewhirst wrote:
>
> Just tried deploying Mezzanine 4.3.1 to a DigitalOcean droplet with
> Python3.6.
>
> Fabric3 and Python3 were used on the dev machine and Python3.6 is
> installed on the droplet. It seems however that fabfile.py line 58 calls
> for python rather than python3 ...
>
> env.manage = "%s/bin/python %s/manage.py" % (env.venv_path, env.proj_path)
>
>
> I don't know enough about how virtualenv names its python interpreter so
> I may be wrong about all this. The droplet was created with Ubuntu 18.04
> and did not have Python2.7 before the deployment but it certainly did
> afterwards.
>
> How can I get away from Python 2.7?
>
> Thanks
>
> Mike
>
--
You received this message because you are subscribed to the Google Groups
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
