Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Clarify what happens when virtualenvs.create is false. #1969

Closed
1 task done
artslob opened this issue Feb 2, 2020 · 1 comment · Fixed by #3027
Closed
1 task done

Clarify what happens when virtualenvs.create is false. #1969

artslob opened this issue Feb 2, 2020 · 1 comment · Fixed by #3027
Labels
area/docs Documentation issues/improvements

Comments

@artslob
Copy link

artslob commented Feb 2, 2020

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

Issue

This issue is about docs on configuration option virtualenvs.create. Currently it says about what happens when option is true. I think, its better to state explicitly, that when option is false, then poetry will install dependencies to current python interpreter/virtualenv.
@artslob artslob added the area/docs Documentation issues/improvements label Feb 2, 2020
@JessicaTegner JessicaTegner mentioned this issue Oct 1, 2020
Merged
2 tasks
finswimmer pushed a commit that referenced this issue Oct 1, 2020
fix #1969 (#3027)
d673342 
* fix #1969

* Added newline
maxispeicher pushed a commit to maxispeicher/poetry that referenced this issue Oct 7, 2020
@maxispeicher
fix python-poetry#1969 (python-poetry#3027)
b6ac85a 
* fix python-poetry#1969

* Added newline
exhuma pushed a commit to exhuma/poetry that referenced this issue Oct 9, 2020
fix python-poetry#1969 (python-poetry#3027)
abd0eda 
* fix python-poetry#1969

* Added newline
@github-actions GitHub Actions
Copy link

github-actions bot commented Mar 2, 2024

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area/docs Documentation issues/improvements
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix #1969
1 participant
@artslob