vim-localvimrc VS coc-pyright

A big part of 'project awareness' implies (to me at least!) that a project is organized in some meaningful way: test/view/model/service/domain files all relate to one another by their naming conventions and location in the project tree.When I start/join a project I look for documentation of the project's structure (or document it myself!). Then for vim:- use https://github.com/embear/vim-localvimrc - drop a .vimrc in the project so I can tweak vim to suit the project.

Something like Localvimrc?

Project-specific editor config: vim-localvimrc, vim-addon-local-vimrc

Is vim modeline a good way to do it? What do you think about that solution: https://github.com/embear/vim-localvimrc?

This is pretty much the last one, but with available commands. One I find particularly useful is LocalVimRCCleanup. I'm not sure how common of a use-case this is, but AutoSource stores the hashes of each file you approved, and a common command I run while testing is rm ~/.autosource_hashdir/* :p

Nice video. I have a similar approach for isolating project specific commands and configurations. I may borrow your idea for a project specific menu to run tasks. For a project dedicated vimrc I use embear/vim-localvimrc for a few years because it has auto discovery and auto change directory for a project, and require confirmation for loading the vimrc file.

Python has several here, pylsp, pyright & a fork of vscode-python

If you use coc.nvim, the coc-pyright module supports inlay hints: https://github.com/fannheyward/coc-pyright

I highly recommend coc.nvim with coc-pyright for python support. Works regardless of vim variant (vim/nvim/etc)

Yup! Go here: https://github.com/fannheyward/coc-pyright And search for python.linting.mypyEnabled

I think coc-python has been deprecated for a while. You might want to try coc-pyright: https://github.com/fannheyward/coc-pyright

And for python dev, you can try & install these coc extension: - https://github.com/fannheyward/coc-pyright - https://github.com/yaegassy/coc-htmldjango

VSCode's LSP was the key technology that enabled Vim to get IDE features. I've heard it works well for python.

As a bonus, pyright's baked in vscode support - something it shares with typescript - not only implies a buttery smooth vs code environment, but also leaves the door open for other lsp-friendly editor/IDE plugins. I personally use neovim and coc.nvim, and as it turns out pyright integrates with coc.nvim quite nicely.

coc-pyright is considered the successor to coc-python.