HfstPythonVersion4

HFST Python API version 4.0

Differences between versions 3.15.0 and 4.0 are listed here.

HfstMutableTransducer

Currently, we have HfstIterableTransducer, but a more descriptive name would be HfstMutableTransducer.

Exceptions

Maybe not a separate class for each exception but subclass(es) of RuntimeError?

Special characters

A more coherent way of handling and special characters (epsilon, unknown, identity, flag diacritics, space, colon) when converting between text and binary formats. Could long names, e.g. (@_UNKNOWN_SYMBOL_@) be always short (?) by default?

Also, default for handling flag diacritics varies among the python API functions as well as between python API and command line tools.

Keyword argument names and default values

They currently differ between HFST command line tools (options) and python API. Should they be the same?

Version numbering scheme

• Three or four digits?
• Semantic versioning?
• Version numbers separate from HFST command line tools?