-
-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Infinite loading #110
Comments
+2 |
Hey guys! I'm not a maintainer but I ran in a similar issue, turned out that running
Printed the following errors:
which was already solved in this issue So I reinstalled it using the sistems package manager and it did exported the correct environment variables; So, since you guys are on MacOS, I'd try using homebrew
Hope it helps |
+3 the above solution with reinstalling did not work for me. Running pylyzer from cli is also stuck |
Didn't helped for me too, Pylyzer is ok with finding env variables or libraries, but still fails to load. |
I'm having the same issue. I setup pylyzer through nix shell using 0.0.66 (I made an overlay for it). My CLI is also stuck in a loop forever. |
@mtshiba Still reproduces on v0.0.67 |
Could problem be in using python 3.12 typing features? I've managed to show the parser produces a stack-overflow on my code and its all written with generics and 3.12 typing. |
Same problem version 0.67.0 and 0.68.0 too |
UPD. Some of my old projects using poetry works fine. |
UPD 2. Found repo with Poetry, where error is still reproduces, so there's probably no dependency between package managers. Also, if I remove .venv in any of these projects, Pylyzer is not stuck anymore. Looks like specific virtual environment state breaks pylyzer. |
I've been having similar issues; fixed the To debug this, I've After trying out versions I'm assuming there's some sort of dependency or environment variable that used to be set via |
It seems that a bug in the Erg compiler was causing the checker to hang. |
Not great for a first experience:
Never completes, never does anything. Is there something I am missing here? |
Sorry, but it still reproduces with UV. Analysis ends only for test.py file located in root folder. All files in |
Hello, thank you for adding virtual environment support.
I've just installed latest Pylyzer version from Cargo, added Pylyzer as source for nvim_lsp and I see infinite loading on "checking files...". However, it seems like using pylyzer on single file from terminal works fine.
Problem reproduces for VSCode too.
Useful information:
Pylyzer: 0.0.66
OS: MacOS Sequoia 15.0.1
Python version: 3.10.13
Package manager: Rye/UV
Processor: Apple M1
Any thoughts what can be wrong?
The text was updated successfully, but these errors were encountered: