brash-baker-9119010/31/2022, 2:40 PM
list, and another is for a type that is included in
, whose import is gated behind an
guard in the test file. This worked without issue in 2.13; is this a bug, or a legitimate new change in behavior? If the latter, what would be the recommended way to fix this? Thanks.
sparse-lifeguard-9573710/31/2022, 2:43 PM
then you can add a comment on the import line to explicitly disable dependency inference - I think the warning messages you’re seeing should include the comment
into your main requirements, and mark it as a type module
brash-baker-9119010/31/2022, 2:44 PM
sparse-lifeguard-9573710/31/2022, 2:45 PM
is a stubs module
brash-baker-9119010/31/2022, 2:51 PM
, which is what Pants was complaining about. The documentation for that field suggests it's more for plugins that pytest itself needs, rather than dependencies that the tests actually need.
sparse-lifeguard-9573710/31/2022, 2:52 PM
subsystem can’t “see” extra-requirements fields in other subsystems
brash-baker-9119010/31/2022, 2:52 PM
sparse-lifeguard-9573710/31/2022, 2:53 PM
brash-baker-9119010/31/2022, 3:00 PM
dependency into my main requirements file also appears to work.