I want to make a package that namespaces avro

[baseplate-admin]

Hi, we have a package, avro.py that uses the same namespace as avro. When invoking pyinstaller, it looks for hooks-avro.py.

So, my question is:

1. Can we modify the hook to pick up avro.py instead of avro?
2. Can we exclude the hook's execution?

cc : @hitblast

[bwoodsend]

This question doesn't make a lot of sense but I'm guessing you mean that you have a package with the same importable name as avro and you want to prevent the hook-avro.py (which is intended for the other avro) from running?

[baseplate-admin]

This question doesn't make a lot of sense but I'm guessing you mean that you have a package with the same importable name as avro and you want to prevent the hook-avro.py (which is intended for the other avro) from running?

More or less yes.

[bwoodsend]

I guess it's high time that we started putting guards in hooks that check that the distribution that they're targeting is installed...

[rokm]

True, although that won't completely solve the problem. It might help avoiding errors when the expected distribution is unavailable, but if you have an eponymous private package that also requires some hook functionality, you will still need to override the hook. And I suppose name clashes are less common with "public" packages (e.g., PyPI-published), because wider exposure ensures in issues being reported against one of the distributions.

[rokm]

You can override any standard hook from PyInstaller or pyinstaller-hooks-contrib by creating your own hook, and passing its parent directory to PyInstaller via --additional-hooks-dir.

E.g., create a directory called my-hooks, and create hook-avro.py in it. Then pass the path to your custom hooks directory to PyInstaller via --additional-hooks-dir my-hooks. Your custom hook will then be ran instead of the one provided by pyinstaller-hooks-contrib. You can make it completely no-op (leave it empty), or customize it to your package, if necessary.

[baseplate-admin]

E.g., create a directory called my-hooks, and create hook-avro.py in it. Then pass the path to your custom hooks directory to PyInstaller via --additional-hooks-dir my-hooks. Your custom hook will then be ran instead of the one provided by pyinstaller-hooks-contrib. You can make it completely no-op (leave it empty), or customize it to your package, if necessary.

Worked

Thanks a bunch