Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Add support for per-project settings

See original GitHub issue

I have searched the issues of this repo and believe that this is not a duplicate.

Issue

Sometimes you might want some settings to be set on a per-project basis. For instance, you might want your virtualenv to be created inside the project’s directory only for the current project.

To make this possible, we could add a --local option to the config command.

The example use case above would then look like this:

poetry config settings.virtualenvs.in-project true --local

And alternative way would be to make namespace command: config:local:

poetry config:local settings.virtualenvs.in-project true

Issue Analytics

State:
Created 5 years ago
Reactions:39
Comments:9 (4 by maintainers)

Top GitHub Comments

27reactions

jacebrowningcommented, Jul 9, 2019

Has any consideration been given to storing some of these local settings in pyproject.toml? I would like every user of a given project to have a virtual environment at ./venv/ so that other tools/scripts/editors can depend on it.

21reactions

sdispatercommented, Jul 31, 2019

This is implemented in #1272 and will be available in the next 1.0.0 release