10 comments

  • rjbwork 1 minute ago
    It's such a shame python got such mindshare. It's a disaster of a language and ecosystem that people keep bolting and hacking things that much better thought out languages have had for decades.
  • anonymous908213 36 minutes ago
    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.
    • rzzzt 3 minutes ago
      Type Server Subsystem for Python
    • wolttam 34 minutes ago
      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

    • pantsforbirds 26 minutes ago
      I do wonder if it generalizes outside of python similar to how LSPs do.
    • Blackarea 32 minutes ago
      100% - it would make more sense if they also supported elixir or other dynamic languages
  • rmzs0711 8 minutes ago
    Is there any application for that, except python?
  • Tarean 28 minutes ago
    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 19 minutes ago
    It kept with UTF-16. New protocol is a chance to correct that poor decision.
  • paaloeye 30 minutes ago
    Interesting, LSP, DAP, MCP, and TSP now...
    • intrasight 13 minutes ago
      TSP : TriSodium Phosphate. Very good for cleaning up a mess.
  • ahgrta 33 minutes ago
    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?

  • beaconflint 15 minutes ago
    [flagged]
  • wetpaws 45 minutes ago
    [dead]