Pierce Lopez
Pierce Lopez
In https://github.com/nsqio/nsq/issues/853#issuecomment-280900898 judwhite says "If people prefer to use NSSM there are ways to support that without removing native support" (for nsqd/nsqlookupd running directly as windows services). I think that...
I set `--use-statsd-prefixes=false` and also configure my statsd implementation to not include such prefixes. It's possible that if you do have/want such prefixes, it's less tested and buggy. It may...
Probably a better idea: add a thread mode as an alternative to the multiprocessing mode for parallel execution. `env` would be a thread-local variable. Most typical tasks would work with...
Yeah, this assumes that you decorate your task functions with `@task`
that's not related to this PR or the issue this PR attempts to solve (parallel under python-3.8). that only is related to getting a PTY
I'm pretty sure *parallel* mode never worked with windows anyway, so we could just switch to "fork" method now.
We have seen this kind of thing before ... the fabric-1 parallel mode forks separate processes, and this apparently requires pickling some objects into bytes to pass between processes, and...
It looks like this is going to be quite a pickle. I untangled some wrappers in https://github.com/ploxiln/fab-classic/compare/master...ploxiln:python38_parallel and it seems that it's the task callables that are the real problem...
I came up with a hacky way, which might only work for top-level `@task` decorated functions. see https://github.com/ploxiln/fab-classic/pull/32 and maybe try with: ``` pip install https://github.com/ploxiln/fab-classic/archive/python38_parallel.tar.gz ``` (not proper enough...