Visual Studio Code configuration for buildout-based Python projects
Project description
Introduction
collective.recipe.vscode is the buildout recipe for Visual Studio Code lover who wants python autocomplete and intelliSense features while developing python Buildout based project, normally buildout eggs are not available in python path even if you provide virtualenv python path. This tool will help not only adding eggs path as python extraPath but also you can manage per project basis vscode settings for linter, autoformatting.
A general question may arise that why we will use this tool, whether we can create Visual Studio Code project settings easily (we have better knowledge over Visual Studio Code configuration)? Well i completely agree with you, but if you want to get benefited from Visual Studio Code autocompletion feature (basically I am lover of autocompletion), you have to add all eggs links and it is hard to manage eggs links manually if the size of project is big (think about any Plone powered project), beside it is good practice allways use project specific linter path. For example my global flake8 linter doesn’t work for my python3 project!
Installation
Install collective.recipe.vscode is simple enough, just need to create a section for vscode to your buildout. Before using collective.recipe.vscode, if you are going to use linter feature, make those are added in eggs section or globally installed.
Example Buildout:
[buildout] parts += vscode [vscode] recipe = collective.recipe.vscode eggs = ${buildout:eggs} flake8-enabled = True flake8-path = ${buildout:directory}/bin/flake8 black-enabled = True black-args = ----line-length 88
Available Options
- eggs
Required: Yes
Default: None
Your project’s list of eggs, those are going to be added as extra path for autocomplete and intelliSense.
- python-path
Required: No
Default: collective.recipe.vscode will find current python executable path.
The python executable path for current project, if you are using virtual environment then should be that python path. FYI: ${home} and ${project} variable should work.
flake8-enabled
Required: No
Default: False
Flag that indicates flake8 based linting.
- flake8-path
Required: No
Default: try to find flake8 executable path automatically.
- flake8-args
Required: No
Default: “”
pylint-enabled
Required: No Default: False
- pylint-path
Required: No
Default: try to find pylint executable path automatically.
- pylint-args
Required: No
Default:
- pep8-enabled
Required: No
Default: False
- pep8-path
Required: No
Default: try to find pep8 executable path automatically.
- pep8-args
Required: No
Default: “”
- jedi-enabled
Required: No
Default: False
- jedi-path
Required: No
Default: “”
- omelette-location
Required: No
Default: ${buildout:directory}/parts/omelette - the default omelette location.
- autocomplete-use-omelete
Required: No
Default: False
- black-enabled
Required: No
Default: False
- black-path
Required: No
Default: try to find black executable path automatically.
You could provide buildout specific black executable. It is very flexible way to avoid using global pylint. Example of relative path usecase: i.) ${buildout:directory}/bin/black ii.) $project_path/bin/black iii.) ./bin/black iv.) ~/path/bin/black
- black-args
Required: No
Default: ‘’
- ignore-develop
Required: No
Default: False
If you don’t want development eggs, should go for autocompletion.
- ignores
Required: No
Default: “”
If you want specific eggs should not go for autocompletion.
- packages
Required: No
Default: “”
Location of some python scripts or non standard modules (don’t have setup file), you want to be in system path.
Links
Code repository:
Continuous Integration:
Issue Tracker:
https://github.com/nazrulworld/collective.recipe.vscode/issues
Example Usage
Install vscode recipe with stndard settings:
>>> write(sample_buildout, 'buildout.cfg', ... """ ... [buildout] ... develop = ... %(test_dir)s/develop/vscodetest_pkg1 ... eggs = ... vscodetest_pkg1 ... zc.recipe.egg ... zc.buildout ... parts = vscode ... ... [vscode] ... recipe = collective.recipe.vscode ... packages = %(test_dir)s/Products ... ignore-develop = False ... eggs = ${buildout:eggs} ... flake8-enabled = True ... flake8-path = ${buildout:directory}/bin/flake8 ... black-enabled = True ... black-path = $project_path/bin/black ... black-args = --line-length 88 ... --skip-string-normalization ... """ % globals()) >>> output_lower = system(buildout + ' -c buildout.cfg').lower() >>> "installing vscode." in output_lower True >>> 'tests/develop/vscodetest_pkg1' in output_lower True >>> ls(sample_buildout) - .installed.cfg d .vscode d bin - buildout.cfg d develop-eggs d eggs d parts <BLANKLINE> >>> import json >>> import os >>> from collective.recipe.vscode.recipes import mappings >>> settings_dir = os.path.join(sample_buildout, ".vscode") >>> vsc_settings = json.loads(read(settings_dir, 'settings.json')) >>> len(vsc_settings[mappings['autocomplete-extrapaths']]) == 4 True >>> mappings['flake8-enabled'] in vsc_settings True >>> vsc_settings[mappings['formatting-provider']] == "black" True
VS Code settings with all default options:
>>> write(sample_buildout, 'buildout.cfg', ... """ ... [buildout] ... develop = ... %(test_dir)s/develop/vscodetest_pkg1 ... eggs = ... vscodetest_pkg1 ... zc.recipe.egg ... parts = vscode ... ... [vscode] ... recipe = collective.recipe.vscode ... eggs = ${buildout:eggs} ... """ % globals()) >>> output = system(buildout + ' -c buildout.cfg').lower() >>> vsc_settings = json.loads(read(settings_dir, 'settings.json')) >>> mappings['flake8-path'] not in vsc_settings True >>> len(vsc_settings[mappings['autocomplete-extrapaths']]) == 3 True
Contributors
Md Nazrul Islam<email2nazrul@gmail.com>, Original Author.
Changelog
0.1.0 (2019-02-10)
Initial release. [nazrulworld]
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
File details
Details for the file collective.recipe.vscode-0.1.0.tar.gz
.
File metadata
- Download URL: collective.recipe.vscode-0.1.0.tar.gz
- Upload date:
- Size: 16.4 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/1.12.1 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.7.3 requests-toolbelt/0.9.1 tqdm/4.30.0 CPython/3.6.7
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | 99fc98c9135a3d5b21ecbf00edb0462fffdceda33c601079affd258ac744bbd4 |
|
MD5 | 748bb6347e08a38add65404d6553c7f1 |
|
BLAKE2b-256 | f1511850accf4bb9f0f871f868a2d9876da438dd4c512c9cc4b426fd37a92ddf |
File details
Details for the file collective.recipe.vscode-0.1.0-py2.py3-none-any.whl
.
File metadata
- Download URL: collective.recipe.vscode-0.1.0-py2.py3-none-any.whl
- Upload date:
- Size: 18.3 kB
- Tags: Python 2, Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/1.12.1 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.7.3 requests-toolbelt/0.9.1 tqdm/4.30.0 CPython/3.6.7
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | ecda318b416b06b4185ea1cd36bb7f41c45d2da11f1765efb259195d00770af5 |
|
MD5 | a9609b13136f4b2c2651810086f5d1f8 |
|
BLAKE2b-256 | 9c7c940735ffc7e54504827eb9d451371b7a3470c2d07b0711ba8122b5492605 |