Aanand Prasad
Aanand Prasad
I don't think so. `pty.sockets()` opens the HTTP connections. `pty.start()` just hooks them up to stdin/out/err.
If you're using Docker Machine, you can point docker-py at it using `docker-machine env` and the `kwargs_from_env()` utility method. ``` python from docker import Client from docker.utils import kwargs_from_env client...
This looks alright as a default. It adds another API call to `exec_command`, but people can always avoid that by using the lower-level `ExecOperation` interface. LGTM
Yeah, we can probably make this more automatic. @shin- - how does docker-py do it?
Makes sense to me, particularly if Compose is the primary/only consumer of it. @bfirsh, @samalba?
Oh, I don't mean to suggest we roll it into Compose - just that if you're happy to hand it over to github.com/docker, I think it's a good idea.
Ping @samalba, who's got the GitHub power I believe. Sam - what would be involved in moving this repo to the docker org?
Sorry, I'm afraid I don't maintain this project any more - I haven't used it in years. I recommend you try another tool - a quick Google turns up [PurifyCSS](https://github.com/purifycss/purifycss)...
Thanks! I have very little time to look after deadweight these days, but I'll take a look as soon as I can.
Cool, thanks! Can you add a test for it?