Lie Ryan

I'm removing the bug label, this isn't a bug, inlining `__new__` currently isn't supported so it's a new feature. It should be possible to implement, inlining classmethods already mostly works...

@magnuslarsen I think you should create a new ticket. @fecet's ticket is about the sqlite3 error, which is not related to the other neovim/pylsp/autoimport-related issue. I'll provide some context on...

Adding a validation here makes sense to me. It seems like it should be fairly straightforward to add validation here in [rename.py](https://github.com/python-rope/rope/blob/master/rope/refactor/rename.py#L85) to validate that `new_name` should be checked against...

Hi bagel, thank you for the contribution. Since this database is actually really just a "cache"/"index" of the files on disk, I think we don't really need a full blown...

Hi Bagel, thanks for this, the changes for collecting documentation looks reasonable to me. However, I'm not quite seeing the reason why it is necessary to index the docstrings, maybe...

Hi @bagel897, is this PR ready for review or are you still working on it? If it's ready to review, can you please move it out of draft?

`pytool.toml` is global config file, unless you want this to be applied to all of your projects (which is unlikely), you'll likely want to use a local config file for...

@bagel897 other than Database versioning, is there any other things that this PR will need to resolve before this draft PR is "ready for review"?

No worries, if you are not already working on it, I might pick the task for that database schema versioning so the DB versioning probably should have its own ticket.

Hi @SomeoneSerge, thanks for writing this issue and creating the PR. I'm currently travelling on vacation, so my availability to look into rope issues and review PRs will be limited...