46 points adamnemecek 1 hour ago 11 comments
anonymous908213 30 minutes ago | parent
This should be called Python Type Server Protocol, no? Seems weird to mine the generic protocol namespace for a protocol that only supports Python. Especially coming from the company behind LSP, which actually is generic.
wolttam 27 minutes ago | parent
It is namespaced under the pylance project. I also don't see any announcement here, just a markdown file.
Perhaps the post title could use a tweak
adamnemecek 10 minutes ago | parent
This was the announcement https://devblogs.microsoft.com/python/announcing-tsp/
Blackarea 25 minutes ago | parent
100% - it would make more sense if they also supported elixir or other dynamic languages
pantsforbirds 20 minutes ago | parent
I do wonder if it generalizes outside of python similar to how LSPs do.
ahgrta 26 minutes ago | parent
Type-shed, type-server. When can this Python madness stop? How about using CORBA to make it even more enterprisey?
Why don't you spend your resources on F# instead of this nonsense?
Tarean 22 minutes ago | parent
So basically adding machine readable type-at-point queries as an lsp extension so Pylance and Pywright can be separated?
The 'result types'format is super python specific, like not having a for all binder. I don't think this specific schema will be used for any non-python languages.
0cf8612b2e1e 13 minutes ago | parent
It kept with UTF-16. New protocol is a chance to correct that poor decision.