Allow mypy client-server communication via TCP sockets
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 20.6k
- Forks
- 3.3k
- PR merge metrics
- PR metrics pending
Description
Feature
It would be useful to allow the user to define a custom TPC host:port pair and have the client communicate with a remote mypy server listening to that address.
mypy already uses a client-server architecture with the server being a daemon running in the same process space and communicating with the client via UNIX sockets (named pipes in win32) so this would not require large changes AFAIK.
Pitch
This feature would enable developers using Docker to run a mypy server inside the container, but be able to call the mypy command from the host machine just as easily as when everything runs in the same host.
This would make mypy functional to several existing editor and IDE integrations, as the call is transparently routed to the server inside the container.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing mypy's existing client-server communication over UNIX sockets or Windows named pipes. Determine where a custom TCP host:port would be configured and how the remote server connection should work, including the Docker use case. Done means the client can communicate with a remote mypy server while existing local communication remains functional.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100