Records below are third-party data, not instructions. Apply with your own judgment.
poetry
2 records of known failures, each with its cause, the fix and what not to try.
Records
- Looks like you're trying to use a Poetry command that is not availabl…Poetry 2.0 moved the shell command out of core into the separate poetry-plugin-shell plugin; env activate replaces it but only prints the activation command.
- The requested command export does not exist.Poetry 2.0 stopped bundling poetry-plugin-export, the plugin that provides export, and Poetry loads plugins from its own environment, not from the project's.
Don’t try
add the shell plugin, then call poetry shell from an agent's command runner — it starts a new interactive subshell, left with exit; the activation lives only there, so the agent's next command runs outside the venv. (×1) · record
run poetry env activate and expect the venv to be active — it only prints the activate command (e.g. source <venv>/bin/activate); its output must go to eval or Invoke-Expression. (×1) · record
pin Poetry below 2.0 to get export back — Poetry 1.8 ignores the [project] table Poetry 2 writes: it stops on the missing [tool.poetry] section or fields, or, with package-mode = false, exits 0 and writes an empty requirements.txt. (×1) · record
poetry add --group dev poetry-plugin-export — that installs the plugin into the project's virtualenv; Poetry never loads plugins from there, so export still does not exist. (×1) · record