Issues with Python 2.7.9 about honcho HOT 7 CLOSED

Thanks for raising an issue. We have a PR #121 that is trying to remedy this

from honcho.

Workaround for those who don't want to wait for #121: put the common args like -e in the subcommand instead of before it.

Example: honcho -e foo.env start bar → honcho start -e foo.env bar

from honcho.

Upstream bug: http://bugs.python.org/issue23058

from honcho.

Thanks @Changaco. Now I am wondering is there actually anything we can do on our part. Will give it a closer look when I'll have some time.

from honcho.

I'm with @slafs on this one. This is pretty clearly a bug in Python 2.7.9, and I'm not sure that breaking backwards compatibility with past versions of Honcho in order to fix it is a good idea.

from honcho.

Just for completeness, I'll add a different situation where it will dramatically affect working code. In this case, if the -f parameter comes before the start command, honcho will endlessly fork new processes.

In a specific case, those working with foreman+honcho in Heroku, will see their startup sequence stop working. Repro files in here, https://gist.github.com/anonymous/6705f438f83e4347850c

Output will look like this

17:12:58 web.1  | started with pid 217
17:12:58 web.1  | 17:12:58 web.1  | started with pid 220
17:12:58 web.1  | 17:12:58 web.1  | 17:12:58 web.1  | started with pid 223
17:12:58 web.1  | 17:12:58 web.1  | 17:12:58 web.1  | 17:12:58 web.1  | started with pid 226
17:12:58 web.1  | 17:12:58 web.1  | 17:12:58 web.1  | 17:12:58 web.1  | 17:12:58 web.1  | started with pid 229
17:12:58 web.1  | 17:12:58 web.1  | 17:12:58 web.1  | 17:12:58 web.1  | 17:12:58 web.1  | 17:12:58 web.1  | started with pid 232

from honcho.

Closed by 1319da7 and released as v0.6.4.

from honcho.