Sevilay Bayatli <sevilaybaya...@gmail.com>
čálii:

> $ curl '
> http://localhost:8080/perWord?lang=kaz-tur&modes=morph&q=Сен+бардың+ба
> <http://localhost:8080/perWord?lang=kaz-tur&modes=morph&q=%D0%A1%D0%B5%D0%BD+%D0%B1%D0%B0%D1%80%D0%B4%D1%8B%D2%A3+%D0%B1%D0%B0>
> ?'
>
> Exception in thread Thread-8:
> multiprocessing.pool.RemoteTraceback:
> """
> Traceback (most recent call last):
>   File "/usr/lib/python3.5/multiprocessing/pool.py", line 119, in worker
>     result = (True, func(*args, **kwds))
>   File
> "/home/sevilay/engine-code/apertium-apy/apertium_apy/handlers/per_word.py",
> line 36, in process_per_word
>     morph_lexical_units = remove_dot_from_deformat(query,
> re.findall(lexical_unit_re, analysis))
>   File "/usr/lib/python3.5/re.py", line 213, in findall
>     return _compile(pattern, flags).findall(string)
> TypeError: expected string or bytes-like object
> """
>
> The above exception was the direct cause of the following exception:
>
> Traceback (most recent call last):
>   File "/usr/lib/python3.5/threading.py", line 914, in _bootstrap_inner
>     self.run()
>   File "/usr/lib/python3.5/threading.py", line 862, in run
>     self._target(*self._args, **self._kwargs)
>   File
> "/home/sevilay/engine-code/apertium-apy/apertium_apy/handlers/per_word.py",
> line 141, in worker
>     callback(result.get(timeout=self.timeout))
>   File "/usr/lib/python3.5/multiprocessing/pool.py", line 608, in get
>     raise self._value
> TypeError: expected string or bytes-like object

This might be a problem in apy, maybe worth raising an issue:
https://github.com/goavki/apertium-apy/issues

Attachment: signature.asc
Description: PGP signature

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Reply via email to