Project maintenance and future plans

[ssbarnea]

I ended up finding dockerpy while trying to find a solution to decouple molecule-docker driver from needing docker cli for one particular minor feature: ability to step inside a container for debugging it.

That is important because some users can connect to remote DOCKER_HOST while they do not have docker cli installed locally (probably even impossible on some platforms/architectures).

Still, considering the number of open bugs, unresolved PRs and lack of releases in 4 years makes me think that maybe that would not be the wisest to add an unmaintained project as e dependency, especially when you aim to support a wide range of python versions (py36-py39).

Here are few questions:

• is anyone using it in production?
• how much effort it would be needed to revive the broken CI
• any concerns regarding breaking changes introduced in current versions of docker-py?

PS. If the state is not really bad I may be able to give a hand to revive it.

[gridhead]

@ssbarnea,

To answer your first question, please check the following screenshot out.

It is included as one of the dependencies to docker-compose in its installation package on Ubuntu, so I think it would be safe to assume that it is used in production in one of the most important applications.

[weddige]

As Docker Compose abandoned Python (and therefore this package) with V2 the question is still relevant. Is this package dead or not?

[hartwork]

@d11wtq any thoughts?

Related: #31