dripline should have generically useful implementations for Providers, specifics ones for for a particular instrument should be able to specified in the config file as an absolute path to a source file. Syntax is TBD but presumably either require a module name in snake_case to match the class name in CamelCase, or just add a optional standard field for module_path... At that time it may make sense to rename the "module" field to "class" or "instance_type" or similar. Probably allow either name for compatibility for now and schedule "module" for deprecation in the next major version bump.
dripline should have generically useful implementations for Providers, specifics ones for for a particular instrument should be able to specified in the config file as an absolute path to a source file. Syntax is TBD but presumably either require a module name in snake_case to match the class name in CamelCase, or just add a optional standard field for module_path... At that time it may make sense to rename the "module" field to "class" or "instance_type" or similar. Probably allow either name for compatibility for now and schedule "module" for deprecation in the next major version bump.