| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks for the PR. Don't forget to add a news entry.
Sorry, something went wrong.
There was a problem hiding this comment.
What issue is this for? We need a bit more discussion on the topic of file-based activation events (in package.json). For example, there are other files that are just as valid as markers for Python projects (requirements.txt, pytest.ini, etc.). Furthermore, note that we don't already have "workspaceContains:**/*.py" in the list. So a bit more discussion in a corresponding issue would be helpful.
Sorry, something went wrong.
|
Eric Snow (@ericsnowcurrently) I specifically wanted to concentrate just on the pyproject.toml since that is a PEP standard file. There is another PR that has a wide variety of files it aims to support, but because of that appears to be stalled for several months due to disagreements that may never be resolved. In the meantime, VSCode continues to have a sub-par Python user experience because the extension isn't even activated until you open a .py file in the editor. |
Sorry, something went wrong.
Sorry, something went wrong.
|
Kudos, SonarCloud Quality Gate passed!
|
Sorry, something went wrong.
|
Can we please move forward with this and merge? If not, please advise as to what is blocking. |
Sorry, something went wrong.
|
I'm fine with the PR (though I'd suggest adding setup.py to it). However, I'm double-checking with someone else first. Thanks for your patience. |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
We'll also look at adding workspaceContains:setup.py in the near future.
Sorry, something went wrong.
|
And sorry that took so long to sort out. Thanks for your patience. 😄 |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
(for #4765)
This PR adds triggering off of 'pyproject.toml' in the workspace root to load the extension.
I'm hoping that using this standard file is easier to get merged vs. the "kitchen-sink" approach that has stalled another PR due to debates and disagreements.