rationale behind scan_for_not_found=True

[ltalirz]

The default manager is currently set to always re-scan, when encountering an empty group in iter_entry_points:
https://github.com/DropD/reentry/blob/1d17bfdc00b7824980783f9a825cb202d28c281f/reentry/default_manager.py#L35
https://github.com/DropD/reentry/blob/1d17bfdc00b7824980783f9a825cb202d28c281f/reentry/default_manager.py#L48-L50

1. Just for the record, what was the rationale behind making this the default ?
2. In aiida, there are many places where we don't want that (e.g. verdi autocompletion). Currently, we are creating our own entrypoint manager with scan_for_not_found=False. Is this the way to go or should one simply add a scan_for_not_found parameter to iter_entry_points in reentry and always use the default manager from reentry?

[DropD]

1. To play well with tools entry points written without reentry in mind.
   Setuptools' default behaviour is similar in that no manual scan needs to be used to find a freshly installed entry point (which might not be aware of reentry). Reentry emulates this behaviour by scanning the first time it is used, instead of every time).

2. However it is clear that cases such as these exist, and that is what the scan_for_not_found parameter is for. Both are viable options, where passing it to iter_entry_points is meant for one-offs and creating an alternative plugin manager is meant for situations where this usage is prevalent. I am sure you are using it the intended way in this case.