-
Notifications
You must be signed in to change notification settings - Fork 6
Move pytest warning enable into pyproject.toml #118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Wasn't sure on the syntax for this before, so just went with the CLI invocation. I think we just want this (by default) on any `pytest` invocation. Signed-off-by: Stefan VanBuren <[email protected]>
Just a ratchet to ensure we don't inadvertently miss warnings in CI output. Similar to connect-python: connectrpc/connect-python#118
|
hm, wasn't expecting this to fail. maybe related: pytest-dev/pytest#14096? |
|
(and doesn't fail locally 😞) |
Just a ratchet to ensure we don't inadvertently miss warnings in CI output. Similar to connect-python: connectrpc/connect-python#118
|
Doh - I think that's a linux-only codepath being used by pyvoy once on startup. Sent a fix to the library, will see if that can be updated soon enough or if I'll need to vendor it to fix that. |
|
no worries on a quick fix, we can always hold off on landing this on our end, it's a minor thing. |
To pull in ktbarrett/find_libpython#111, for connectrpc/connect-python#118. via `uv lock --upgrade-package find-libpython`.
Signed-off-by: Anuraag Agrawal <[email protected]>
61fc677 to
3a0127b
Compare
|
Thanks for teaching me these practices! |
Wasn't sure on the syntax for this before, so just went with the CLI invocation. I think we just want this (by default) on any
pytestinvocation.