You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the issues of this repo and believe that this is not a duplicate.
I have searched the documentation and believe that my question is not covered.
Feature Request
Small setback
If poetry shell is run from a script, then $SHELL is going to be set to what that script was executed in. Example scenario:
I am using zsh
I write scripts to help teammates work with Poetry (they are coming from other tools), for example a .env which gets sourced by autoenv etc, and then does poetry shell at the end. I make these scripts have a bash shebang because that's the sane default for most at the company
I still want to be using zsh when poetry shell is called in one of these contexts
Easy fix
Option: support for $POETRY_SHELL variable that will be checked before $SHELL variable
This option seems sensible to me
Option: support for something like poetry shell --precedence /bin/zsh /bin/bash etc
Option: support for something like that, but at poetry config level
I will submit a PR once we agree on how it should work!
The text was updated successfully, but these errors were encountered:
floer32
changed the title
Small feature request for 'poetry shell' preferences
Small feature request for 'poetry shell' to accept something besides $SHELL
Mar 10, 2019
Feature Request
Small setback
If
poetry shell
is run from a script, then$SHELL
is going to be set to what that script was executed in. Example scenario:zsh
.env
which gets sourced by autoenv etc, and then doespoetry shell
at the end. I make these scripts have abash
shebang because that's the sane default for most at the companyzsh
whenpoetry shell
is called in one of these contextsEasy fix
$POETRY_SHELL
variable that will be checked before$SHELL
variablepoetry shell --precedence /bin/zsh /bin/bash
etcpoetry config
levelI will submit a PR once we agree on how it should work!
The text was updated successfully, but these errors were encountered: