Update CONTRIBUTING.md #154
Labels
good first issue
Easy things for newbies
Comments
nat-n
added a commit
to nat-n/copier
that referenced
this issue
Aug 16, 2020
The new `[tool.poe.tasks]` section and new poetry based workflow are a complete replacement for the makefile which has also been removed.
nat-n
added a commit
to nat-n/copier
that referenced
this issue
Aug 17, 2020
…a complete replacement for the makefile which has also been removed. Also - update CONTRIBUTING.MD copier-org#154 to keep things coherent - add tox dev dep and config to pyproject.toml
nat-n
added a commit
to nat-n/copier
that referenced
this issue
Aug 17, 2020
…a complete replacement for the makefile which has also been removed. Also - update CONTRIBUTING.MD copier-org#154 to keep things coherent - add tox dev dep and config to pyproject.toml
nat-n
added a commit
to nat-n/copier
that referenced
this issue
Aug 21, 2020
The new `[tool.poe.tasks]` section and new poetry based workflow are a complete replacement for the makefile which has also been removed. copier-org#129 Also: - add devtasks for python functions to be referenced as poe tasks - update CONTRIBUTING.MD copier-org#154 to keep things coherent - remove reference to tox - update ci to work with more expressive toml syntax (upgrade pip) - and use poe tasks in ci
yajo
pushed a commit
that referenced
this issue
Aug 21, 2020
The new `[tool.poe.tasks]` section and new poetry based workflow are a complete replacement for the makefile which has also been removed. #129 Also: - add devtasks for python functions to be referenced as poe tasks - update CONTRIBUTING.MD #154 to keep things coherent - remove reference to tox - update ci to work with more expressive toml syntax (upgrade pip) - and use poe tasks in ci
|
Seeing how you improved CONTRIBUTING.md in this commit, maybe this issue could be closed? Maybe just one thing I noticed: you track VSCode settings and set the path to the interpreter to - "python.pythonPath": ".venv/bin/python"
+ "python.pythonPath": "/home/pawamoy/.cache/pypoetry/virtualenvs/copier-AExR1Oeb-py3.9/bin/python"Not sure how to circumvent that though. |
|
Yes, that's because of microsoft/vscode-python#8372. For now, the only way to use both tools sanely and share out-of-the-box settings is to tell poetry to save the venv local to the project. I should document that. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Once the dev setup has stabilized it will be time to reflect the changes back into the dev docs:
CONTRIBUTING.md.See also: #129 #132
The text was updated successfully, but these errors were encountered: