-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Support using conda to install Pylint #301
Comments
Scenario 1 Should we still allow the user to select conda as an option to install the module? I don't think so. |
Do we even need to let the user choose? Shouldn't we just use |
Lol, agreed. |
Not sure whether this is the right place to start this discussion, but here goes: Came across a blog post the other day about that being the |
I think they're referring to the fact that Then again, people who use |
I am not a fan of the easter egg @brettcannon mentions, but I'm working on a project that chose to use pipenv and it is a great workflow. I work on Windows, and the one issue I have come across is pipenv's lack of history buffer support in Windows cmd console: pew-org/pew#165. If I'm not mistaken, proper support in the Python plugin to direct calls to the pipenv interpreter through vscode would dodge some of the setbacks and make a significant positive impact on using pipenv in Windows, which is otherwise an unduly stunted workflow. |
I'm moving the discussion of |
We will probably want to auto-select the approach based on whether a conda install is selected for the interpreter or not.
The text was updated successfully, but these errors were encountered: