nushell: issues regarding poetry shell

[icp1994]

• Poetry version: 1.6.1
• Python version: 3.11.4
• OS version and name: Void Linux (Rolling)
• pyproject.toml: generated default from poetry new poetry-nu

• I am on the latest stable Poetry version, installed using a recommended method.
• I have searched the issues of this repo and believe that this is not a duplicate.
• I have consulted the FAQ and blog for any relevant entries or release notes.
• If an exception occurs when executing a command, I executed it again in debug mode (-vvv option) and have included the output below.

Issue

In nushell, the poetry shell command spawns a new shell but doesn't activate associated venv - instead just prints the activation command.

This isn't much of an issue by itself since I only have to press <RET> to run the command and activate the venv. But in the spawned shell, if I start any REPL program their input becomes invisible/masked!

[dimbleby]

You'll likely need to figure out what's going on for yourself if this is important to you.

(My advice whenever people have problems with poetry shell is always: just don't use it! Instead, simply activate your virtual environment as you would have done if poetry shell had never existed)

Some possible clues

• looks like fix: fix poetry shell for nushell #7919 was supposed to send the newline, you can start by investigating why that's not working as expected.
• masked input/output is surely something specific to do with your setup. I suppose that poetry shell and nushell are not a tremendously common combination but - eg per that issue - you're surely not the first to try it and others would have noticed if this was what usually happened...

[icp1994]

After some digging, it's something to do with setecho(False). I don't get invisible inputs when I manually activate the venv or if I edit out "nu" from this conditional.

Related: nushell/nushell#6225

[abn]

I am going to close this for now as this seems like an environment issue rather than a Poetry one. Additionally since #7919 fixes the new line issue and it looks like users are using poetry shell fine under nu, it might not something that affects every nu shell user using Poetry.

@icp1994 if you figure out that this is indeed something to do with Poetry's shell setup and have a fix, please send us a pull request with the details. We can consider it then.

[icp1994]

It's works as expected in the current version (0.90.1) of nushell so likely fixed somewhere in between. But I have moved on to using your suggestion of manually activating venvs as if the subcommand doesn't exist instead.

[github-actions]

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.