I'm realizing that when upgrading to recent Heroku stacks (ex heroku-22), Heroku will complain about the Python version I've been using to run our instance of the boundary service (python-3.7.5).
I tried running an upgrade locally, only to realize that upgrading causes problems with Django, where it runs from django.utils.encoding import python_2_unicode_compatible
. At least according to Stack Overflow, it might be possible to either remove that line entirely, or to run pip install six
and from six import python_2_unicode_compatible
.
I haven't been able test this yet, I'm trying to figure out if I can revert my setup to deploy anything, but I'll test it if I can figure that part out.