Is it only the plugins other than CC that register files? So only IsFileExtRegistered returns true only for Fortran files if only CC and fortran plugins are installed?
I think, currently only FortranProject plugin registers the file extensions for
IsFileExtRegistered and, consequently, it returns 'true' only for Fortran files (if FortranProject plugin is active).
For python, I thought it made the most sense to rely on the lexer to decide what to offer python code completion for, but basing it on file extensions might make the most sense in other cases.
The editor's highlighting (lexer) is based on file extensions anyway.
The patch I proposed leaves it to the plugin to decide what it wants to do.
The same situation is in the current implementation: every CC plugin (FortranProject, PythonCC etc.) decides which files (recognized by file extension) it wants to handle and registers the file extensions accordingly.
I don't argue, that the current C::B implementation is better. If developers think that the new patch is better (simpler, shorter, easier to understand etc.), it is OK.