Do not use **kwargs for pretty printing in databases

bob.db.base.Database is deprecated Use bob.db.base.FileDatabase instead

added 1 commit

• 41c0afd4 - pass along the kwargs

Compare with previous version

mentioned in merge request bob.pad.base!21 (merged)

added 1 commit

• ce5ac634 - Do not use pretty prininting with kwargs

Compare with previous version

changed title from bob.db.base.Database is deprecated. to **{+Do not use kwargs for pretty printing in databases+}

changed the description

Fixes the issues introduced by: bob.db.base!34 (merged)

mentioned in merge request bob.bio.face!36 (merged)

assigned to @amohammadi

@mguenther I am going to merge this since a lot of packages depend on this. Please feel free to review this later and I will make the changes.

mentioned in commit cafee446

merged

mentioned in commit bob.db.base@e83d24d5

Sorry, I bought a new computer lately and these mails went into spam folder.

Thanks for merging.

@mguenther it would be good to phase out this kwargs feature for printing eventually in all base classes.

The idea of this feature is that we currently have a unified mechanism of printing all options of all tools and write them into the Experiment.info file. I am not sure if I like the **kwargs in the base class constructor either. Currently, the issue is that **kwargs in the constructor are swallowing typos, which might lead to an unwanted setup.

If you find a better way to implement the same functionality, please go ahead. Maybe we should have a register_option(self, **kwargs) function instead. This would, however, be a major surgery on all classes implemented in bob.bio.