You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
pedantic/verify does not control all the warnings in VO table parsing #8775
As pointed out by @astrofrog in #8756 , pedantic (renamed to verify in #8715) does not universally control all the warnings emitted when parsing VO table. This is an API design question.
In this example, it explicitly calls vo_warn, which would give warning (or not), but it will never promote the warning to error even if config['verify'] is set to 'exception'. But should it ever be an error, given that some default is assigned anyway in L303?
In this example, config is passed into the constructor as if it means something, but it is not stored by the class. As a result, the following emits a warning:
changed the title [-]pedantic/verify does not control all the warnings in votable parsing[/-][+]pedantic/verify does not control all the warnings in VO table parsing[/+]on May 29, 2019
Activity
[-]pedantic/verify does not control all the warnings in votable parsing[/-][+]pedantic/verify does not control all the warnings in VO table parsing[/+]pllim commentedon Apr 30, 2021
Somewhat related... #11677 (review)