heroku local python version

[heroku]

heroku local python version

[jdx]

@kennethreitz do you have any idea? I'm not sure what is going on here

[opyate]

I even tried conda install python=3.6.3 and changing runtime.txt to python-3.6.3 as per the latest supported version.

[opyate]

Digging through Heroku CLI/util etc to see how my environment is interrogated.

UPDATE: hint to look at node foreman.

[opyate]

Foreman clearly finds System py27 (at "/Library/Python/2.7"):

% heroku local
[WARN] No ENV file found
16:43:54 web.1   |  [2018-01-05 16:43:54 +0000] [27288] [INFO] Starting gunicorn 19.7.1
16:43:54 web.1   |  [2018-01-05 16:43:54 +0000] [27288] [INFO] Listening at: http://0.0.0.0:5000 (27288)
16:43:54 web.1   |  [2018-01-05 16:43:54 +0000] [27288] [INFO] Using worker: sync
16:43:54 web.1   |  [2018-01-05 16:43:54 +0000] [27292] [INFO] Booting worker with pid: 27292
16:43:54 web.1   |  [2018-01-05 16:43:54 +0000] [27293] [INFO] Booting worker with pid: 27293
16:43:54 web.1   |  [2018-01-05 16:43:54 +0000] [27294] [INFO] Booting worker with pid: 27294
16:43:54 web.1   |  [2018-01-05 16:43:54 +0000] [27292] [ERROR] invalid syntax (__init__.py, line 5)
16:43:54 web.1   |  Traceback (most recent call last):
16:43:54 web.1   |    File "/Library/Python/2.7/site-packages/gunicorn/workers/base.py", line 135, in load_wsgi
16:43:54 web.1   |      self.wsgi = self.app.wsgi()

[opyate]

#41 also tried here: strongloop/node-foreman#149

[kennethreitz]

Heroku local is not aware of runtime.txt, like the heroku runtime is. Whatever python is normally, it will remain.

[kennethreitz]

I recommend creating a virtualenv with the desired Python interpreter and activating it before invoking heroku local.

[opyate]

Thanks for the suggestions.

So many moving parts: heroku, conda, python, foreman, gunicorn.

I suspect the problem with OSX system python clashing with conda python somehow, and gunicorn not getting the correct environment (or the wrong/old gunicorn in /Library/Python/2.7/site-packages/gunicorn being used).

Anyhoo, closing, as this is clearly not a heroku-local issue.