collective / collective.recipe.vscode Goto Github PK

Case 1

If you trying to disable any liner from buildout parts(options), like pylint-enabled = False. In the result there is no reflection but should be in settings "python.linting.pylintEnabled": false

Case 2

If you enable any linter first time, again try to disable from buildout parts (options), that's also not working it kept enabled permanently!

It would be nice if you can add the recipe to ~/.buildout/default.cfg and it will find all eggs without having to know anything about the buildout. This would mean the only thing needed to get vscode support is run a buildout without changing it.

I think this should be possible as I did something similar in collective.hostout. If the recipe installs itself as dependent on all other parts of the buildout it will run last. At that point all resolution is done. Buildout compiles a signature of each recipe based on what eggs it's dependent on. It should be possible to hook into that and read that list of eggs.

Hi,

I need more information about configuring VSCode after installed this recipe. This is the relevant part of my develop.cfg:

[omelette]
recipe = collective.recipe.omelette
eggs = ${buildout:eggs}

[vscode]
recipe = collective.recipe.vscode
eggs = ${buildout:eggs}
pylint-enabled = True
autocomplete-use-omelette = True
generate-envfile = True

Within VSCode I connect to my Linux server using the Remote Explorer and cd into ~/plone/zeocluster/parts/omelette/ where I find all the eggs and also my own addons. I then change the Python interpreter to ~/plone/zeocluster/bin/zopepy and enable linting using pylint. It seems to work somehow but it is very slow. Pressing F12 on an import lasts up to a minute until it opens a new tab with the module I am looking for. Any idea to speed this up? Can I do something better here or did I something wrong?

Pylint does not use python.autoComplete.extraPaths to decide if an import is valid or not.

microsoft/vscode-python#2791

Could be useful to generate a .env file containing PYTHONPATH env variable definition that adds same paths in python.autoComplete.extraPaths to the path

[vscode]
recipe = collective.recipe.vscode
eggs = ${instance:eggs}
flake8-enabled = True
flake8-path = ${buildout:directory}/bin/flake8
flake8-arg = --max-line-length 88
black-enabled = True

{'python.pythonPath': '/home/nazrul/www/python/CONTRIBUTIONS_FOLDER/collective.recipe.vscode/bin/python3', 'python.autoComplete.extraPaths': ['/tmp/eggs/egg1.egg', '/tmp/eggs/egg2.egg'], 'python.jediEnabled': True, 'python.linting.flake8Enabled': True, 'python.linting.flake8Path': '/fake/path/flake8', 'python.linting.pylintEnabled': True, 'python.linting.pep8Enabled': 'False', 'python.formatting.provider': 'black', 'python.formatting.blackPath': '/tmp/bin/black', 'python.formatting.blackArgs': ['--line-length', '88']}

Perhaps detect recipes like zc.testrunner and zope2instance and come up with some default launch configurations for those.

Enabling unittest functionality using zc.testrunner would also be nice but doesn't seem there is currently a way to do this even though the vscode unittest runner can find zope tests - see microsoft/vscode-python#12779.

https://stackoverflow.com/questions/77146074/how-to-update-flake8-settings-in-vscode-following-deprecation-warning

https://marketplace.visualstudio.com/items?itemName=ms-python.vscode-pylance

Hi @nazrulworld 👋🏾

Given that you are already a member of https://github.com/collective would you be ok with transferring this project there? 🤞🏾

With GitHub being owned by Microsoft and VSCode being developed by them, we keep seeing more and more integration of the two.

Moreover a quick glance at Plone developers preferred code editor shows that VSCode is gaining more and more popularity 🚀

It would be great if we have it there so more collaboration can happen 😄

no reason it can't install dependencies instead of just search for them.

This is a really nice extension, but it does a bit more than it should do.
One thing is, that when used vs code will hide all html files in the explorer.
That not helpful when you work on a theme ;).

It's no longer used and you get annoying warnings asking if you want to remove it from your settings.json. see https://visualstudiomagazine.com/articles/2020/05/14/vs-code-python.aspx

Maybe there is a way to write it into launch.json or .env or maybe .direnv? see https://code.visualstudio.com/docs/python/environments (note these docs still mention pythonPath so they are out of date)

Otherwise I think you have to set it yourself which is annoying. Unless someone makes a buildout extension.

project-root is a very useful parameter. But it is not documented.

Mispelled omelete in autocomplete-use-omelete both in code and docs

I've encountered a problem where an error during the buildout is thrown.

Updating vscode.
While:
  Updating vscode.
Error: Expecting property name enclosed in double quotes: line 6 column 5 (char 162)

In the end I noticed the additional comma in my .vscode/settings.json (after "editor.formatOnType": true). This comma leads to the error and if you remove it buildout will work again.

{
    "[python]": {
        "editor.defaultFormatter": "ms-python.black-formatter",
        "editor.formatOnSave": true,
        "editor.formatOnType": true,
    },
}

I don't know if this behavior is desired or not but I wanted to share this (& especially the solution).

isort has his own configuration option but there is no trace in config. Not knowing it made me change the settings manually and find it overwrited on the next buildout