How does pants handle dynamic imports with dependency inference? For example if we use a typing library which is bloated but we don't want that in the package for lambda deployment to minimise artefact size?

Regarding dynamic imports, there’s some options in this subsystem https://www.pantsbuild.org/docs/reference-python-infer Not sure if that answers your question though. Your example hints at excluding dependencies, that possibly where inferred. You can do that using

!

and

!!

in your dependencies field. See the note at the end of https://www.pantsbuild.org/docs/targets#dependencies-field

Thanks! That partially solves it, would be good to be able to dynamically set the

!

based on a setting, will have a look around the docs

If you're mentioning type-stubs packages, check out https://www.pantsbuild.org/docs/reference-python_requirement#codetype_stub_modulescode

If there’s a select few imports you don’t want to be inferred by the dependency engine, there’s also a pragma you can apply in code:

... # pants: ignore-dep

Hmm maybe not?