Define rye scripts with arguments passthrough?

[wgordon17]

Currently, when defining a rye script, it's just a static command. Is it possible to define a rye script that is able to take a list of arguments? Similar to PDM's arguments placeholder https://pdm-project.org/latest/usage/scripts/#arguments-placeholder?

[wgordon17]

I think this would also be awesome for chained scripts

error: extra arguments to chained commands are not allowed

[Murtagy]

I agree, also passing env vars across the chain seems extremely useful.
e.g. I want to create a temporary database to run my test suite. To do that I run my regular app, but the database string points to a new temporary file. So before each test suite I remove the sqllite database from the previous run. Currently defining this seems a mess

[mitsuhiko]

Arguments can be passed:

[tool.rye.scripts]
foo = "python -c 'import sys; print(sys.argv)'"

C:\Temp\foo>rye run foo 1 2 3
['-c', '1', '2', '3']

Or do I misunderstand the request here?

[mitsuhiko]

I do understand that request, but that opens a box I'm not sure we should open today. However today arguments are supported, just not at a position other than the last.

[Murtagy]

here is my case

[tool.rye.scripts]
dev = { cmd = "litestar --app src.app:app run --reload ", env = {"DB" = "db.sqlite", "EMAIL" = "false"} }

test = { chain = ["test:clean_db", "test:test_suite"]}
"test:clean_db" = "rm -f /tmp/db.sqlite"
"test:test_suite" = "DB=/tmp/db.sqlite pytest"

Running rye run testspits out not readable error "error: No such file or directory (os error 2)".
This is due to env var (DB=...).

I would like to make instead:

test = { chain = ["test:clean_db", "test:test_suite"], env = { "DB": "/tmp/db.sqlite"} }
"test:clean_db" = "rm -f /tmp/db.sqlite"
"test:test_suite" = "pytest"

But DB is not passed towards pytest part

[wgordon17]

@mitsuhiko What about the use case for at least allowing arguments to be passed to child commands from chain commands?

When I try that today, I get error: extra arguments to chained commands are not allowed

[wgordon17]

@Murtagy You should be able to do this

"test:test_suite".cmd = "pytest"
"test:test_suite".env = { DB = "/tmp/db.sqlite" }

Does that solve your issue? That should still work, even with test:test_suite being included in a chain.

[Murtagy]

That indeed solves my problem @wgordon17. Thanks!

[wgordon17]

@Murtagy Don't quote me, but I think you should be able to use env on a composite script to allow the environment variable to persist. Unless you were thinking about dynamic environment variables. That's possibly where my above use case could come in handy, something like...

run-thing = "FOO_BAR={args} /path/to/thing/bin --do-thing"

¯\_(ツ)_/¯