Is there a way to deal with cases where there are two third

Question

Is there a way to deal with cases where there are two third party libraries being used but both have the same name In my project I use both the `google api python client` and `google auth` libraries In Python code they re both referred to as `google` for example ```from google import auth from google import api core``` I noticed that I can t specify two separate `module mappings` where the values are the same otherwise the build system gets confused

fast-nail-55400 · Answer

In this case you will have to provide explicit dependencies on the `python sources` targets for the code that is importing those modules

fast-nail-55400 · Answer

For context the `module mappings` feature is part of the Pants dependency inference feature which tries to automatically infer dependencies In cases where it cannot you can still use the `dependencies` field on a target to explicitly set the dependency

fast-nail-55400 · Answer

Are you using a `python requirements ` target

fast-nail-55400 · Answer

If so then the address for each dependency will be the address of the `python requirements` plus ` ` then the name of the Python module

fast-nail-55400 · Answer

e g `3rdparty py google api python client` if the file `3rdparty BUILD` had a `python requirements name= py ` target

cold-soccer-63228 · Answer

Ahh I realized my issue was related to something else altogether It ended up being due to `path to source py` having a dependency on `path init py` but the dependency not being inferred So I went ahead and added the following explicitly ```python sources dependencies= path init py ```

bitter-ability-32190 · Answer

Actually this is supported by `module mappings` `module mappings` allow for any valid package name so in your case `google api python client` should map to `google api core` and likewise fgor `google auth`

bitter-ability-32190 · Answer

You can see our default mapping which you are welcome to open a PR to add more entries to <https github com pantsbuild pants blob 2be9157c5e69bf88216cc1b46d471621226cd967 src python pants backend python dependency inference default module mapping py|https github com pantsbuild pants blob 2be9157c5e69bf88216cc1b46d471621226cd967 s backend python dependency inference default module mapping py>

bitter-ability-32190 · Answer

gt Ahh I realized my issue was related to something else altogether It ended up being due to `path to source py` having a dependency on `path init py` but the dependency not being inferred This shouldn t be necessary Do your inits have contents If so you might want to set <https www pantsbuild org docs reference python infer section inits>

cold-soccer-63228 · Answer

Ah awesome I didn t know <https www pantsbuild org docs reference python infer section inits> was an option That should hopefully prevent me from having to manually specify it Before I do so are there any downsides of enabling this feature We have some instances where there is logic in ` init py` files but we re trying to migrate off of it

bitter-ability-32190 · Answer

Not really other than possible noise As far as I know In Pants 2 13 you ll have <https github com pantsbuild pants pull 15397> which should pretty much always do the right thing

bitter-ability-32190 · Answer

Thanks < hundreds father 404> trophy