-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
makecldf fails #3
Comments
This is the new behavior! |
It is there to catch explicitly these errors. |
Go to line 222 in First fix, as |
Ah, and if you think that the |
Ah, I get it now, sorry for not reading properly before. There is something wrong, I guess, as the entry should not pass the |
So the fix we need is in pylexibank code, def split_forms(self, item, value):
if value in self.lexemes: # pragma: no cover
self.log.debug('overriding via lexemes.csv: %r -> %r' % (value, self.lexemes[value]))
value = self.lexemes.get(value, value)
return [self.clean_form(item, form)
for form in split_text_with_context(value, separators='/,;')] needs to be modified to: def split_forms(self, item, value):
if value in self.lexemes: # pragma: no cover
self.log.debug('overriding via lexemes.csv: %r -> %r' % (value, self.lexemes[value]))
value = self.lexemes.get(value, value)
forms = [self.clean_form(item, form)
for form in split_text_with_context(value, separators='/,;')]
return [f for f in form if f] Or similar. As this will only return forms that are not |
I'd say, this is a good example, why it was good to modify the behavior of the |
Just linked this as a bug in pylexibank. |
Fixed. |
... on this entry: word 57 = "?" here.
...which means that the following is passed to
add_form
:... and then we fail with
What's the best way to fix this? Should
add_form
catch this? or should this be caught before getting to add_form?The text was updated successfully, but these errors were encountered: