Closed Neah-Ko closed 1 week ago
Using cargo install --locked --path=.
worked for me
https://github.com/mtshiba/pylyzer/issues/78#issuecomment-2022917309
Using
cargo install --locked --path=.
worked for me #78 (comment)
Thanks @aarnros the installation did proceed that way.
However, at first glance it doesn't seem that pylyzer (or the vscode extension) is production grade yet.
In the first few seconds of use I can notice that:
venv
@property
class method decorator stating that property is not defineddict(key1=val1, key2=val2...)
class MyClass(ParentClass):
stating MyClass
type is not defined. def myDecorator(f): def wrapper(): f() return wrapper
__init__
And finally after opening few files from my project to write this review I get this popup:
Please build using cargo install --path . --locked
.
Most of the issues you pointed out have been fixed in the latest version.
Hello,
Today I learned about the existence of this package and wanted to try vscode extension.
cargo
/rustc
debian bookworm
repos are too low (rustc ~ 1.6x)rustup
i.e.curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
to get latestThen after git clone
https://github.com/mtshiba/pylyzer.git
:System info:
I found no matching issue for this. Should I downgrade pylyzer version ?
EDIT: Browsing some issue, I found that I needed to install ERG and set ERG_PATH, which I've done that way:
and
export ERG_PATH=/path/to/erg
Which didn't changed to error.EDIT 2: After a systemwide
find
, I set ERG_PATH=/home/user/.erg/
instead, but it didn't worked either.