-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for project-specific "default"/"self" configuration #8083
Comments
…d in a project .poetry directory and added the 'self init' command.
…d in a project .poetry directory and added the 'self init' command.
…d in a project .poetry directory and added the 'self init' command.
The project-level This feature request is slightly more generalised than #5740 Although the main benefit I want is fulfilled by #5740 this feature feels useful also? I've raised a draft PR which appears to be working and doing what I've described above. |
The PR you prepared is not viable. |
After discussion, core maintainers decided that this request will be rejected. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Feature Request
As a developer, I am wanting to have some poetry plugins loaded only for certain projects I have on my development machine and may also want to change other poetry settings between projects (i.e. do or don't create virtual environments).
I propose that poetry will look for a
.poetry
directory in the current working directory, if present, it will use this over the default system config location. I'd expectPOETRY_CONFIG_PATH
env var to take precedence over the.poetry
It could be initialized by running a new
init
self command, something likeRunning this command would create a
.poetry
directory in the current working directory and generate the necessary default files (config.toml
,pyproject.toml
,poetry.lock
)This would enable me as a developer to do the following,
and by including the
.poetry
directory in git, it would mean the dependency/usage of a poetry plugin would be automatically picked up by other developers (though they would probably still need to runpoetry self install
, not sure if this can happen implicitly elsewhere TBD)The text was updated successfully, but these errors were encountered: