Fix async implementation not supported

[eastonsuo]

No description provided.

[ccordoba12]

Hey @eastonsuo, thanks for your contribution! Could you explain when this is needed?

[eastonsuo]

I want to use asyncio in plugins, such as when do a async http request for another service, or wait for a asyncio.Event and blocked.

(Maybe Endpoint should be changed to AsyncEndpoint to chieve that?) @ccordoba12

Hey @eastonsuo, thanks for your contribution! Could you explain when this is needed?

[ccordoba12]

Please move this to be on top of from functools import partial and leave the blank line here.

[ccordoba12]

I want to use asyncio in plugins, such as when do a async http request for another service, or wait for a asyncio.Event and blocked.

I see, thanks for the explanation.

(Maybe Endpoint should be changed to AsyncEndpoint to chieve that?)

I'm not really sure. @andfoy, what do you think?

[andfoy]

I'm not really sure. @andfoy, what do you think?

@eastonsuo, could you please clarify your asynchronous case of use? We would assume that you would like to get multiple future objects instead of blocking on a call?

[eastonsuo]

I'm not really sure. @andfoy, what do you think?

@eastonsuo, could you please clarify your asynchronous case of use? We would assume that you would like to get multiple future objects instead of blocking on a call?

yes, for example, I would like to post a request asynchronously within a call and on the other hand not blocking another call.

I think it can be realized by an AsyncEndpoint and start server by asyncio.run()

[lieryan]

The idea of async handler is reasonable, but pylsp already start some threads to run hook handlers that may take time (e.g. linters). It may be reasonable to extend this so that all hook handlers have the option to be written as either def or async def. Either way, IMO hook handlers should not be running on the main pylsp thread, so that one slow/broken plugins should not interfere with the performance of the rest of python-lsp-server.

However, this should not be implemented in the flatten() method as suggested in this PR. This doesn't look like the right place to implement that.

[ccordoba12]

Agreed. I think the proper solution is to make the server fully async aware.