From 93e1464e6a464cbf85332fd5169ed95fa688b536 Mon Sep 17 00:00:00 2001 From: Joe Rickerby Date: Sat, 1 Apr 2023 11:06:53 +0100 Subject: [PATCH] some changes after seeing how this renders --- docs/options.md | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/docs/options.md b/docs/options.md index db99ffc3..92371b04 100644 --- a/docs/options.md +++ b/docs/options.md @@ -1172,14 +1172,6 @@ The command is run in a shell, so you can write things like `cmd1 && cmd2`. Platform-specific environment variables are also available:
`CIBW_TEST_COMMAND_MACOS` | `CIBW_TEST_COMMAND_WINDOWS` | `CIBW_TEST_COMMAND_LINUX` -!!! tip - - It's isn't recommended to `cd` to your project directory before running tests, - because Python might resolve `import yourpackage` relative to the working dir, - but we want to test the wheel you just built. However, if you're sure that's not - an issue for you and your workflow requires it, on Windows you should do `cd /d`, - because the CWD and project dir might be on different drives. - #### Examples !!! tab examples "Environment variables" @@ -1222,6 +1214,13 @@ Platform-specific environment variables are also available:
In configuration files, you can use an array, and the items will be joined with `&&`. +!!! note + + It's isn't recommended to `cd` to your project directory before running tests, + because Python might resolve `import yourpackage` relative to the working dir, + and we want to test the wheel you just built. However, if you're sure that's not + an issue for you and your workflow requires it, on Windows you should do `cd /d`, + because the CWD and project dir might be on different drives. ### `CIBW_BEFORE_TEST` {: #before-test} > Execute a shell command before testing each wheel