Environment data
- VS Code version: 1.20.1
- Extension version (available under the Extensions sidebar): 2018.2.1
- OS and version: Ubuntu 16.04
Feature Request
(also see #1161)
When I create a new Python project I end up spending a first while setting things up. This involves just about the same things every time: create a setup.py, README, LICENSE, top-level package, tests package, etc. A while back I even went to far as create a tools to automate this.
The extension could do something similar, as well as giving the option for several different project templates (e.g. basic project, CLI project, django project, data analysis project):
- click "create new Python project" on the start page
- pick the project template from a list
- fill in a few details (e.g. project name, repo URL)
However, I'm not sure how much VSC will support that. That said, I think it wouldn't run counter to the VSCode role as an editor.
Ultimately, templates could be drawn from a central clearinghouse (e.g. marketplace) and/or from GH, etc.
Environment data
Feature Request
(also see #1161)
When I create a new Python project I end up spending a first while setting things up. This involves just about the same things every time: create a setup.py, README, LICENSE, top-level package,
testspackage, etc. A while back I even went to far as create a tools to automate this.The extension could do something similar, as well as giving the option for several different project templates (e.g. basic project, CLI project, django project, data analysis project):
However, I'm not sure how much VSC will support that. That said, I think it wouldn't run counter to the VSCode role as an editor.
Ultimately, templates could be drawn from a central clearinghouse (e.g. marketplace) and/or from GH, etc.