Poetry run doesn't work with --directory= #434

Activity

1. Secrus

   added this to the 3.0 milestone on Nov 28, 2024
2. Secrus

   added

   bugSomething isn't working as expectedSomething isn't working as expected

   on Jan 3, 2025
3. latk commented on Jan 18, 2025

   

   latk

   on Jan 18, 2025

   Last edited by latk

   More actions

   I recently stumbled across the same issue with the poetry --project option. @abn kindly tried to fix this in the Poetry code that pre-processes arguments before passing them to Poetry, but that arguably just makes the problem worse. I'm not sure it can be fixed without explicit support by Cleo for this pattern?

   In this context, I'd like to highlight that Poetry/Cleo handling of short and long options with values seems to be fairly unpredictable, e.g. I'd expect poetry -C path, poetry -Cpath, poetry --directory path, and poetry --directory=path to all be fully equivalent (and similarly for -P/--project). These equivalences are a common Linux command line convention (aka "whatever GNU getopt_long does", also well-supported by Python's argparse module). Yet we can observe a diverse range of errors with the poetry [OPTIONS] run [OPTIONS] COMMAND... syntax.

   References:

   • my Poetry issue: documented CLI option syntax with values doesn't work for subcommands poetry#10051
   • attempted fix in Poetry: fix(app): improve global opt and run cmd parsing poetry#10067
   • my reproduction steps + analysis: fix(app): improve global opt and run cmd parsing poetry#10067 (comment)