Mismatch in lookup method if compared to python's SymSpell

[RevadiSai]

Earlier I am using python Symspell which can easily installed through python's pip. And later i have created a fast-api server to use Symspell as an API. Currently for faster performance I wanted to use go lang HTTP server instead python's fast-api. For this, I am using this go-symspell library.

However, I am observing a mismatch between these two implementations for lookup method even if i am using same dictionaries ( both unigram and bigram ). Can someone please help me here with any suggestions?

pip module reference: symspellpy

[SamMHD]

Hello dear @RevadiSai
Can you please share your examples?
Currently we have made some improvements to vanilla Symspell here, I just want to take a look at examples to see if it's intended or it's a bug.

[RevadiSai]

Hi @SamMHD
I am using LookupCompound function in both python's Library and this go-symspell library with same unigram and bigram dictionaries and getting different results in both of them. Here are few examples

input	symspellpy	go-symspell
chhattpati shuvaji maharaj	chhatrpati shivaji maharaj	chhat pati shivaji maharaj
ganagama thimmaiah conventional hall	gangama thimmaiah conventional hall	janagama thimmaiah conventional hall
Kemopegowda International Terminal 2	kempegowda international terminal 2	kemp gowda international terminal 2

[sepehrsoh]

Hi @RevadiSai ,
We have most of the tests of symspellpy package here.
we use option pattern to set symspell config, i suugest firt look at tests, but if your issue continues we can check it implementation and compare with what you do in symspellpy