home.social

#pylance — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #pylance, aggregated by home.social.

fetched live
  1. Alguém conhece um bom tutorial de #RAG que não use o #ChromaDB como banco vetorial? O desgraçado não está funcionando no #Python 3.10 ou maior graças ao #Pylance

  2. Alguém conhece um bom tutorial de #RAG que não use o #ChromaDB como banco vetorial? O desgraçado não está funcionando no #Python 3.10 ou maior graças ao #Pylance

  3. Alguém conhece um bom tutorial de #RAG que não use o #ChromaDB como banco vetorial? O desgraçado não está funcionando no #Python 3.10 ou maior graças ao #Pylance

  4. Alguém conhece um bom tutorial de #RAG que não use o #ChromaDB como banco vetorial? O desgraçado não está funcionando no #Python 3.10 ou maior graças ao #Pylance

  5. Stumbled across this issue on #GitHub after experiencing the same thing myself. Found the thread pretty hilarious. I wonder what you guys think?
    github.com/microsoft/pylance-r
    #vscode #python #pylance #linting #poll

  6. Stumbled across this issue on #GitHub after experiencing the same thing myself. Found the thread pretty hilarious. I wonder what you guys think?
    github.com/microsoft/pylance-r
    #vscode #python #pylance #linting #poll

  7. Stumbled across this issue on #GitHub after experiencing the same thing myself. Found the thread pretty hilarious. I wonder what you guys think?
    github.com/microsoft/pylance-r
    #vscode #python #pylance #linting #poll

  8. Stumbled across this issue on #GitHub after experiencing the same thing myself. Found the thread pretty hilarious. I wonder what you guys think?
    github.com/microsoft/pylance-r
    #vscode #python #pylance #linting #poll

  9. Stumbled across this issue on #GitHub after experiencing the same thing myself. Found the thread pretty hilarious. I wonder what you guys think?
    github.com/microsoft/pylance-r
    #vscode #python #pylance #linting #poll

  10. CW: Microsoft, Malware

    Der Python-Language-Server #Pylance, eine von #Microsoft entwickelte Extension für Visual Studio Code, enthält eine waschechte #ReDoS-Attacke (regular expression denial of service).

    Kern des Angriffs ist ein regulärer Ausdruck (siehe Screenshot), der offenbar dazu gedacht ist, Debugger-Prozesse in eine Quasi-Endlos-Busy-Loop-Falle mit 100% CPU-Auslastung laufen zu lassen.

    Zwar lässt sich die Attacke mit minimalem Aufwand unschädlich machen, aber: heilige Scheiße! Solche Aktionen sind eines billionenschweren Tech-Konzerns mehr als unwürdig.

  11. CW: Microsoft, Malware

    Der Python-Language-Server #Pylance, eine von #Microsoft entwickelte Extension für Visual Studio Code, enthält eine waschechte #ReDoS-Attacke (regular expression denial of service).

    Kern des Angriffs ist ein regulärer Ausdruck (siehe Screenshot), der offenbar dazu gedacht ist, Debugger-Prozesse in eine Quasi-Endlos-Busy-Loop-Falle mit 100% CPU-Auslastung laufen zu lassen.

    Zwar lässt sich die Attacke mit minimalem Aufwand unschädlich machen, aber: heilige Scheiße! Solche Aktionen sind eines billionenschweren Tech-Konzerns mehr als unwürdig.

  12. CW: Microsoft, Malware

    Der Python-Language-Server #Pylance, eine von #Microsoft entwickelte Extension für Visual Studio Code, enthält eine waschechte #ReDoS-Attacke (regular expression denial of service).

    Kern des Angriffs ist ein regulärer Ausdruck (siehe Screenshot), der offenbar dazu gedacht ist, Debugger-Prozesse in eine Quasi-Endlos-Busy-Loop-Falle mit 100% CPU-Auslastung laufen zu lassen.

    Zwar lässt sich die Attacke mit minimalem Aufwand unschädlich machen, aber: heilige Scheiße! Solche Aktionen sind eines billionenschweren Tech-Konzerns mehr als unwürdig.

  13. CW: Microsoft, Malware

    Der Python-Language-Server #Pylance, eine von #Microsoft entwickelte Extension für Visual Studio Code, enthält eine waschechte #ReDoS-Attacke (regular expression denial of service).

    Kern des Angriffs ist ein regulärer Ausdruck (siehe Screenshot), der offenbar dazu gedacht ist, Debugger-Prozesse in eine Quasi-Endlos-Busy-Loop-Falle mit 100% CPU-Auslastung laufen zu lassen.

    Zwar lässt sich die Attacke mit minimalem Aufwand unschädlich machen, aber: heilige Scheiße! Solche Aktionen sind eines billionenschweren Tech-Konzerns mehr als unwürdig.

  14. If #pylance includes a wrong typing for a function, where do I have to open the ticket? Pylance or the #typeshed project?

    The definition from calendar.pyi is basically wrong as the function returns actually list[list[list[date]]].

    ```python
    def yeardatescalendar(self, year: int, width: int = 3) -> list[list[int]]: ...
    ```

    #python #typing

  15. If includes a wrong typing for a function, where do I have to open the ticket? Pylance or the project?

    The definition from calendar.pyi is basically wrong as the function returns actually list[list[list[date]]].

    ```python
    def yeardatescalendar(self, year: int, width: int = 3) -> list[list[int]]: ...
    ```

  16. If #pylance includes a wrong typing for a function, where do I have to open the ticket? Pylance or the #typeshed project?

    The definition from calendar.pyi is basically wrong as the function returns actually list[list[list[date]]].

    ```python
    def yeardatescalendar(self, year: int, width: int = 3) -> list[list[int]]: ...
    ```

    #python #typing

  17. If #pylance includes a wrong typing for a function, where do I have to open the ticket? Pylance or the #typeshed project?

    The definition from calendar.pyi is basically wrong as the function returns actually list[list[list[date]]].

    ```python
    def yeardatescalendar(self, year: int, width: int = 3) -> list[list[int]]: ...
    ```

    #python #typing

  18. If #pylance includes a wrong typing for a function, where do I have to open the ticket? Pylance or the #typeshed project?

    The definition from calendar.pyi is basically wrong as the function returns actually list[list[list[date]]].

    ```python
    def yeardatescalendar(self, year: int, width: int = 3) -> list[list[int]]: ...
    ```

    #python #typing

  19. #Python #PythonTyping #Pyright #Pylance #Mypy

    Is there a way to create type stub only for part of the library?

    For example: I want to include types for a single object, but don't want to maintain full copy of the library types.

    github.com/carltongibson/djang

  20. #Python #PythonTyping #Pyright #Pylance #Mypy

    Is there a way to create type stub only for part of the library?

    For example: I want to include types for a single object, but don't want to maintain full copy of the library types.

    github.com/carltongibson/djang

  21. Anybody found a way to make the #Pylance type checker understand Click decorators?

    #Mypy understands them just fine.

    #Python #PyRight

  22. Anybody found a way to make the #Pylance type checker understand Click decorators?

    #Mypy understands them just fine.

    #Python #PyRight

  23. Anybody found a way to make the #Pylance type checker understand Click decorators?

    #Mypy understands them just fine.

    #Python #PyRight

  24. Anybody found a way to make the #Pylance type checker understand Click decorators?

    #Mypy understands them just fine.

    #Python #PyRight

  25. Anybody found a way to make the #Pylance type checker understand Click decorators?

    #Mypy understands them just fine.

    #Python #PyRight

  26. github.com/microsoft/pylance-r

    What do you expect when renaming import?

    I expect import to be renamed, not target class. Join the discussion.

    #Python #pyright #pylance

  27. #ICYMI check out the latest 🥳 Release Party 🥳 featuring cool highlights from the April #vscode release! @OliviaGuzzardo is joined by members of the team to talk about #copilotchat #pylance #devcontainers and more! 🎥 youtube.com/live/mhYCTz-rswE
    @roblourens t.co/tzCaemVKc1

    :sys_twitter: twitter.com/code/status/165705

  28. #ICYMI check out the latest 🥳 Release Party 🥳 featuring cool highlights from the April #vscode release! @OliviaGuzzardo is joined by members of the team to talk about #copilotchat #pylance #devcontainers and more! 🎥 youtube.com/live/mhYCTz-rswE
    @roblourens t.co/tzCaemVKc1

    :sys_twitter: twitter.com/code/status/165705

  29. #ICYMI check out the latest 🥳 Release Party 🥳 featuring cool highlights from the April #vscode release! @OliviaGuzzardo is joined by members of the team to talk about #copilotchat #pylance #devcontainers and more! 🎥 youtube.com/live/mhYCTz-rswE
    @roblourens t.co/tzCaemVKc1

    :sys_twitter: twitter.com/code/status/165705

  30. #ICYMI check out the latest 🥳 Release Party 🥳 featuring cool highlights from the April #vscode release! @OliviaGuzzardo is joined by members of the team to talk about #copilotchat #pylance #devcontainers and more! 🎥 youtube.com/live/mhYCTz-rswE
    @roblourens t.co/tzCaemVKc1

    :sys_twitter: twitter.com/code/status/165705

  31. #ICYMI check out the latest 🥳 Release Party 🥳 featuring cool highlights from the April #vscode release! @OliviaGuzzardo is joined by members of the team to talk about #copilotchat #pylance #devcontainers and more! 🎥 youtube.com/live/mhYCTz-rswE
    @roblourens t.co/tzCaemVKc1

    :sys_twitter: twitter.com/code/status/165705

  32. ⌛ We're going live in 10 minutes with another 🎉 VS Code Release Party 🎉 Join us for demos on the newest features in #vscode and chat with the team! 🎬 youtube.com/live/mhYCTz-rswE
    #Jupyter #copilot #pylance t.co/uv1fUN72PE

    :sys_twitter: twitter.com/code/status/165667

  33. ⌛ We're going live in 10 minutes with another 🎉 VS Code Release Party 🎉 Join us for demos on the newest features in #vscode and chat with the team! 🎬 youtube.com/live/mhYCTz-rswE
    #Jupyter #copilot #pylance t.co/uv1fUN72PE

    :sys_twitter: twitter.com/code/status/165667

  34. ⌛ We're going live in 10 minutes with another 🎉 VS Code Release Party 🎉 Join us for demos on the newest features in #vscode and chat with the team! 🎬 youtube.com/live/mhYCTz-rswE
    #Jupyter #copilot #pylance t.co/uv1fUN72PE

    :sys_twitter: twitter.com/code/status/165667

  35. ⌛ We're going live in 10 minutes with another 🎉 VS Code Release Party 🎉 Join us for demos on the newest features in #vscode and chat with the team! 🎬 youtube.com/live/mhYCTz-rswE
    #Jupyter #copilot #pylance t.co/uv1fUN72PE

    :sys_twitter: twitter.com/code/status/165667

  36. ⌛ We're going live in 10 minutes with another 🎉 VS Code Release Party 🎉 Join us for demos on the newest features in #vscode and chat with the team! 🎬 youtube.com/live/mhYCTz-rswE
    #Jupyter #copilot #pylance t.co/uv1fUN72PE

    :sys_twitter: twitter.com/code/status/165667

  37. It's another 🎉 VS Code Release Party 🎉 We are psyched to demo the newest features including #Pylance, #devcontainers, drag and drop and #copilotchat!
    Mark your 📅 and join us this Thursday aka.ms/code-livestream-page
    8 am Seattle / 11 am New York / 4 pm London
    @OliviaGuzzardo t.co/7zV6q3BdtL

    :sys_twitter: twitter.com/code/status/165527

  38. It's another 🎉 VS Code Release Party 🎉 We are psyched to demo the newest features including #Pylance, #devcontainers, drag and drop and #copilotchat!
    Mark your 📅 and join us this Thursday aka.ms/code-livestream-page
    8 am Seattle / 11 am New York / 4 pm London
    @OliviaGuzzardo t.co/7zV6q3BdtL

    :sys_twitter: twitter.com/code/status/165527

  39. It's another 🎉 VS Code Release Party 🎉 We are psyched to demo the newest features including #Pylance, #devcontainers, drag and drop and #copilotchat!
    Mark your 📅 and join us this Thursday aka.ms/code-livestream-page
    8 am Seattle / 11 am New York / 4 pm London
    @OliviaGuzzardo t.co/7zV6q3BdtL

    :sys_twitter: twitter.com/code/status/165527

  40. It's another 🎉 VS Code Release Party 🎉 We are psyched to demo the newest features including #Pylance, #devcontainers, drag and drop and #copilotchat!
    Mark your 📅 and join us this Thursday aka.ms/code-livestream-page
    8 am Seattle / 11 am New York / 4 pm London
    @OliviaGuzzardo t.co/7zV6q3BdtL

    :sys_twitter: twitter.com/code/status/165527

  41. It's another 🎉 VS Code Release Party 🎉 We are psyched to demo the newest features including #Pylance, #devcontainers, drag and drop and #copilotchat!
    Mark your 📅 and join us this Thursday aka.ms/code-livestream-page
    8 am Seattle / 11 am New York / 4 pm London
    @OliviaGuzzardo t.co/7zV6q3BdtL

    :sys_twitter: twitter.com/code/status/165527

  42. Apparently, #pylance can now be configured to automatically create an f-string when a { is added to a string.

    Currently disabled by default; can be enabled at the "python.analysis.autoFormatStrings" setting in #VSCode once the May Update has been installed.

    #Python

    devblogs.microsoft.com/python/

  43. Apparently, #pylance can now be configured to automatically create an f-string when a { is added to a string.

    Currently disabled by default; can be enabled at the "python.analysis.autoFormatStrings" setting in #VSCode once the May Update has been installed.

    #Python

    devblogs.microsoft.com/python/

  44. Apparently, can now be configured to automatically create an f-string when a { is added to a string.

    Currently disabled by default; can be enabled at the "python.analysis.autoFormatStrings" setting in once the May Update has been installed.

    devblogs.microsoft.com/python/

  45. Apparently, #pylance can now be configured to automatically create an f-string when a { is added to a string.

    Currently disabled by default; can be enabled at the "python.analysis.autoFormatStrings" setting in #VSCode once the May Update has been installed.

    #Python

    devblogs.microsoft.com/python/

  46. I hope that I'm not the only one excited to see "Improved IntelliSense support for pytest" in the latest release notes for Visual Studio Code

    #Python #PyTest #Pylance #VSCode #VisualStudioCode

  47. I hope that I'm not the only one excited to see "Improved IntelliSense support for pytest" in the latest release notes for Visual Studio Code

    #Python #PyTest #Pylance #VSCode #VisualStudioCode

  48. I hope that I'm not the only one excited to see "Improved IntelliSense support for pytest" in the latest release notes for Visual Studio Code

    #Python #PyTest #Pylance #VSCode #VisualStudioCode

  49. I hope that I'm not the only one excited to see "Improved IntelliSense support for pytest" in the latest release notes for Visual Studio Code

    #Python #PyTest #Pylance #VSCode #VisualStudioCode

  50. I hope that I'm not the only one excited to see "Improved IntelliSense support for pytest" in the latest release notes for Visual Studio Code

    #Python #PyTest #Pylance #VSCode #VisualStudioCode

  51. #VSCode 1.75 is out, and along with it some improvements to #Python stuff!

    code.visualstudio.com/updates/

    The `Create Environment` command will now ask what requirements files and/or `pyproject.toml` optional dependencies you would like to see installed.

    This release also sees #Pylance having automatic indentation (if you want; controlled by a setting).

    🤫 I hear if you use Pylance pre-release you can get #pytest fixture support for "Go to Definition" and completions

    code.visualstudio.com/updates/

  52. 1.75 is out, and along with it some improvements to stuff!

    code.visualstudio.com/updates/

    The `Create Environment` command will now ask what requirements files and/or `pyproject.toml` optional dependencies you would like to see installed.

    This release also sees having automatic indentation (if you want; controlled by a setting).

    🤫 I hear if you use Pylance pre-release you can get fixture support for "Go to Definition" and completions

    code.visualstudio.com/updates/

  53. #VSCode 1.75 is out, and along with it some improvements to #Python stuff!

    code.visualstudio.com/updates/

    The `Create Environment` command will now ask what requirements files and/or `pyproject.toml` optional dependencies you would like to see installed.

    This release also sees #Pylance having automatic indentation (if you want; controlled by a setting).

    🤫 I hear if you use Pylance pre-release you can get #pytest fixture support for "Go to Definition" and completions

    code.visualstudio.com/updates/

  54. #VSCode 1.75 is out, and along with it some improvements to #Python stuff!

    code.visualstudio.com/updates/

    The `Create Environment` command will now ask what requirements files and/or `pyproject.toml` optional dependencies you would like to see installed.

    This release also sees #Pylance having automatic indentation (if you want; controlled by a setting).

    🤫 I hear if you use Pylance pre-release you can get #pytest fixture support for "Go to Definition" and completions

    code.visualstudio.com/updates/

  55. #VSCode 1.75 is out, and along with it some improvements to #Python stuff!

    code.visualstudio.com/updates/

    The `Create Environment` command will now ask what requirements files and/or `pyproject.toml` optional dependencies you would like to see installed.

    This release also sees #Pylance having automatic indentation (if you want; controlled by a setting).

    🤫 I hear if you use Pylance pre-release you can get #pytest fixture support for "Go to Definition" and completions

    code.visualstudio.com/updates/

  56. @clayton I remember interacting with #PyCharm Community Edition one year ago, and it wasn't bad! Language server is what interested me a lot (not without few shortcomings). Indexing is more transparent, good integration with linters and formatters.

    Meanwhile, in #VSCode I always feel like Python support remains deficient - virtual environments require more work to do than necessary, leaving you with the quirks of non-OSS #Pylance language server as an added "bonus". Integrated #JupyterNotebook.

  57. @clayton I remember interacting with #PyCharm Community Edition one year ago, and it wasn't bad! Language server is what interested me a lot (not without few shortcomings). Indexing is more transparent, good integration with linters and formatters.

    Meanwhile, in #VSCode I always feel like Python support remains deficient - virtual environments require more work to do than necessary, leaving you with the quirks of non-OSS #Pylance language server as an added "bonus". Integrated #JupyterNotebook.

  58. @clayton I remember interacting with Community Edition one year ago, and it wasn't bad! Language server is what interested me a lot (not without few shortcomings). Indexing is more transparent, good integration with linters and formatters.

    Meanwhile, in I always feel like Python support remains deficient - virtual environments require more work to do than necessary, leaving you with the quirks of non-OSS language server as an added "bonus". Integrated .

  59. Obligatory #introduction. I'm not a hashtag guy but they make searching work (sorry).

    Hi, I'm Jake, a senior software engineer at #microsoft working on the #typescript team (doing cool stuff like github.com/microsoft/TypeScrip , build, perf stuff).

    Previously, I worked on #Pylance / #pyright for #python.

    My favorite and most used language, shockingly, is Go (#golang).

    Though I'm on Windows for work / gaming, I've otherwise been running #archlinux for well over a decade (love sway, i3 before that).

  60. Obligatory . I'm not a hashtag guy but they make searching work (sorry).

    Hi, I'm Jake, a senior software engineer at working on the team (doing cool stuff like github.com/microsoft/TypeScrip , build, perf stuff).

    Previously, I worked on / for .

    My favorite and most used language, shockingly, is Go (#golang).

    Though I'm on Windows for work / gaming, I've otherwise been running for well over a decade (love sway, i3 before that).