1 Issue closed by 1 person

• pylyzer's trange complection behavior in neovim

  #71 closed Feb 16, 2025

1 Issue opened by 1 person

• Lots of (false) errors on a Python file that compiles well with Codon

  #124 opened Feb 17, 2025

11 Unresolved conversations

Sometimes conversations happen on old items that aren’t yet closed. Here is a list of all the Issues and Pull Requests with unresolved conversations.

• Mason: How do I specify python environment to use in pylyzer?

  #55 commented on Feb 12, 2025 • 0 new comments

• Better error messages for unsupported features

  #42 commented on Feb 12, 2025 • 0 new comments

• Reaching too deep in import resolution

  #41 commented on Feb 12, 2025 • 0 new comments

• textDocument/hover causes pylyzer to exit in neovim-nightly

  #39 commented on Feb 12, 2025 • 0 new comments

• Package-level imports resolution

  #33 commented on Feb 13, 2025 • 0 new comments

• [Feature] failure to source imported modules from pyenv virtualenv site-packages folder

  #31 commented on Feb 13, 2025 • 0 new comments

• pylyzer extension on https://open-vsx.org/ for VSCodium users

  #17 commented on Feb 14, 2025 • 0 new comments

• Unreasonable errors on built-in type constructor such as int()

  #15 commented on Feb 15, 2025 • 0 new comments

• Feature request: pytest-pylyzer

  #84 commented on Feb 15, 2025 • 0 new comments

• Possible false errors

  #118 commented on Feb 17, 2025 • 0 new comments

• As a tool for python developers: readability is debatable

  #14 commented on Feb 17, 2025 • 0 new comments