Converted my Django site to Python 3 and now I can’t run Fabric to deploy it—my attempts to port to Fabric 2 so far in vain.
Current plan: use Pipenv to manage a separate Python-2 environment for Fabric.
I can install fabric 1.14 globally and it runs with Python 2.7 even though my virtualenv is python3. Hence deployed and discovered another snag: I assumed that uWSGI used the Python version in the virtualenv but noooooo you need to recompile it to use Python3. :sob:
I used to have a static-HTML site. Maybe this is the time to throw up my hands and switch to using Jekyl or whatever. Maintaining software is a mug's game these days.
Upgraded uWSGI so I can use plugins to switch Python versions. Can't run my site. After endless fiddling with uWSGI config files I find I can't run the site with ./manage run server either so I guess I need to reexamine all the Django settings next.
OK the plan doesn't work because Pipenv expects you to use only one Python per application, which is not exactly unreasonable but is inconvenient in this weird case.