Closed suhassumukh closed 5 years ago
This should be fixed as of the v0.1.0 release today. Thank you for reporting!
I've also addressed a lot of corner cases involving the combination of unicode_literals
and other parts of the parser API, especially the NLTK integration. Please open an issue if anything else comes up!
One of the most problematic things in Py2 is
unicode
andstr
. To backport several features, I (and so do many) usually useThis means when I import your model
benepar_en_small
, I get an error.This is because of
I think making it
basestring
instead of juststr
can resolve this issue. Please let me know if this is comfortable.