JamSpell installation via pip fails (Windows 11)

[DragonCloudBurst]

I'm attempting to install JamSpell via pip for use with a project that I'm working on at my position as an employee at my university's academic library. I work in the Digital Collections department. For context, we're attempting to improve our OCR process, and we're looking at JamSpell as an option that could spellcheck our OCR processor's output, which commonly produces some erroneous results, especially when it is being run on scans of older documents.

However, despite being able to download Swig 3.0.12's source code, pip fails to install JamSpell. The machine I am using is a Windows 11 PC; I was unable to find any official Swig 3 packages from the Windows package managers that we currently have installed (Cygwin and WinGet. I did notice, however, that Chocolately seems to have a package of this version, which I will attempt to install soon if I can obtain permission to do so...). In an effort to attempt to combat that, I ran the pip install from within the folder where Swig is installed... though I'm not fully up to speed with how pip works, so it's possible that pip isn't picking up on it since I wasn't able to install the older version via pip itself...? I doubt that adding the directory to PYTHONPATH would resolve the issue, since it doesn't contain any actual python files.

As a side note... this could potentially still be an issue with Swig not being properly registered in the machine's PATH variable; since our machines are administrated under our IT department, we occasionally run into issues with more advanced computing tasks.

EDIT to clarify: I did add the directory to PATH.

Regardless, it seems to me that the main issue that we're having stems from JamSpell using an older version of Swig that doesn't appear to be recognized by pip (since I had to download the source code manually from SourceForge).

Do you know of any possible way to get around this? Alternatively, would there be a way to get JamSpell to work with a newer version of Swig?

Apologies if any of this sounds a bit uninformed; I know very little about Swig or C++.

Stack trace:

pip install jamspell
Collecting jamspell
  Using cached jamspell-0.0.12.tar.gz (174 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Building wheels for collected packages: jamspell
  Building wheel for jamspell (pyproject.toml) ... error
  error: subprocess-exited-with-error

  × Building wheel for jamspell (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [125 lines of output]
      C:\Users\SPIVEYA23\AppData\Local\Temp\pip-build-env-w8y0yvxq\overlay\Lib\site-packages\setuptools\dist.py:599: SetuptoolsDeprecationWarning: Invalid dash-separated key 'description-file' in 'metadata' (setup.cfg), please use the underscore name 'description_file' instead.
      !!

              ********************************************************************************
              Usage of dash-separated 'description-file' will not be supported in future
              versions. Please use the underscore name 'description_file' instead.
              (Affected: jamspell).

              By 2026-Mar-03, you need to update your project and remove deprecated calls
              or your builds will no longer be supported.

              See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details.
              ********************************************************************************

      !!
        opt = self._enforce_underscore(opt, section)
      C:\Users\SPIVEYA23\AppData\Local\Temp\pip-build-env-w8y0yvxq\overlay\Lib\site-packages\setuptools\dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated.
      !!

              ********************************************************************************
              Please consider removing the following classifiers in favor of a SPDX license expression:

              License :: OSI Approved :: MIT License

              See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.
              ********************************************************************************

      !!
        self._finalize_license_expression()
      running bdist_wheel
      running build
      running build_ext
      building '_jamspell' extension
      <string>:48: DeprecationWarning: Use shutil.which instead of find_executable
      Traceback (most recent call last):
        File "C:\Users\SPIVEYA23\AppData\Local\Programs\Python\Python313\Lib\site-packages\pip\_vendor\pyproject_hooks\_in_process\_in_process.py", line 389, in <module>
          main()
          ~~~~^^
        File "C:\Users\SPIVEYA23\AppData\Local\Programs\Python\Python313\Lib\site-packages\pip\_vendor\pyproject_hooks\_in_process\_in_process.py", line 373, in main
          json_out["return_val"] = hook(**hook_input["kwargs"])
                                   ~~~~^^^^^^^^^^^^^^^^^^^^^^^^
        File "C:\Users\SPIVEYA23\AppData\Local\Programs\Python\Python313\Lib\site-packages\pip\_vendor\pyproject_hooks\_in_process\_in_process.py", line 280, in build_wheel
          return _build_backend().build_wheel(
                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
              wheel_directory, config_settings, metadata_directory
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
          )
          ^
        File "C:\Users\SPIVEYA23\AppData\Local\Temp\pip-build-env-w8y0yvxq\overlay\Lib\site-packages\setuptools\build_meta.py", line 435, in build_wheel
          return _build(['bdist_wheel', '--dist-info-dir', str(metadata_directory)])
        File "C:\Users\SPIVEYA23\AppData\Local\Temp\pip-build-env-w8y0yvxq\overlay\Lib\site-packages\setuptools\build_meta.py", line 423, in _build
          return self._build_with_temp_dir(
                 ~~~~~~~~~~~~~~~~~~~~~~~~~^
              cmd,
              ^^^^
          ...<3 lines>...
              self._arbitrary_args(config_settings),
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
          )
          ^
        File "C:\Users\SPIVEYA23\AppData\Local\Temp\pip-build-env-w8y0yvxq\overlay\Lib\site-packages\setuptools\build_meta.py", line 404, in _build_with_temp_dir
          self.run_setup()
          ~~~~~~~~~~~~~~^^
        File "C:\Users\SPIVEYA23\AppData\Local\Temp\pip-build-env-w8y0yvxq\overlay\Lib\site-packages\setuptools\build_meta.py", line 512, in run_setup
          super().run_setup(setup_script=setup_script)
          ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "C:\Users\SPIVEYA23\AppData\Local\Temp\pip-build-env-w8y0yvxq\overlay\Lib\site-packages\setuptools\build_meta.py", line 317, in run_setup
          exec(code, locals())
          ~~~~^^^^^^^^^^^^^^^^
        File "<string>", line 55, in <module>
        File "C:\Users\SPIVEYA23\AppData\Local\Temp\pip-build-env-w8y0yvxq\overlay\Lib\site-packages\setuptools\__init__.py", line 115, in setup
          return distutils.core.setup(**attrs)
                 ~~~~~~~~~~~~~~~~~~~~^^^^^^^^^
        File "C:\Users\SPIVEYA23\AppData\Local\Temp\pip-build-env-w8y0yvxq\overlay\Lib\site-packages\setuptools\_distutils\core.py", line 186, in setup
          return run_commands(dist)
        File "C:\Users\SPIVEYA23\AppData\Local\Temp\pip-build-env-w8y0yvxq\overlay\Lib\site-packages\setuptools\_distutils\core.py", line 202, in run_commands
          dist.run_commands()
          ~~~~~~~~~~~~~~~~~^^
        File "C:\Users\SPIVEYA23\AppData\Local\Temp\pip-build-env-w8y0yvxq\overlay\Lib\site-packages\setuptools\_distutils\dist.py", line 1002, in run_commands
          self.run_command(cmd)
          ~~~~~~~~~~~~~~~~^^^^^
        File "C:\Users\SPIVEYA23\AppData\Local\Temp\pip-build-env-w8y0yvxq\overlay\Lib\site-packages\setuptools\dist.py", line 1102, in run_command
          super().run_command(command)
          ~~~~~~~~~~~~~~~~~~~^^^^^^^^^
        File "C:\Users\SPIVEYA23\AppData\Local\Temp\pip-build-env-w8y0yvxq\overlay\Lib\site-packages\setuptools\_distutils\dist.py", line 1021, in run_command
          cmd_obj.run()
          ~~~~~~~~~~~^^
        File "C:\Users\SPIVEYA23\AppData\Local\Temp\pip-build-env-w8y0yvxq\overlay\Lib\site-packages\setuptools\command\bdist_wheel.py", line 370, in run
          self.run_command("build")
          ~~~~~~~~~~~~~~~~^^^^^^^^^
        File "C:\Users\SPIVEYA23\AppData\Local\Temp\pip-build-env-w8y0yvxq\overlay\Lib\site-packages\setuptools\_distutils\cmd.py", line 357, in run_command
          self.distribution.run_command(command)
          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^
        File "C:\Users\SPIVEYA23\AppData\Local\Temp\pip-build-env-w8y0yvxq\overlay\Lib\site-packages\setuptools\dist.py", line 1102, in run_command
          super().run_command(command)
          ~~~~~~~~~~~~~~~~~~~^^^^^^^^^
        File "C:\Users\SPIVEYA23\AppData\Local\Temp\pip-build-env-w8y0yvxq\overlay\Lib\site-packages\setuptools\_distutils\dist.py", line 1021, in run_command
          cmd_obj.run()
          ~~~~~~~~~~~^^
        File "<string>", line 37, in run
        File "C:\Users\SPIVEYA23\AppData\Local\Temp\pip-build-env-w8y0yvxq\overlay\Lib\site-packages\setuptools\_distutils\cmd.py", line 357, in run_command
          self.distribution.run_command(command)
          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^
        File "C:\Users\SPIVEYA23\AppData\Local\Temp\pip-build-env-w8y0yvxq\overlay\Lib\site-packages\setuptools\dist.py", line 1102, in run_command
          super().run_command(command)
          ~~~~~~~~~~~~~~~~~~~^^^^^^^^^
        File "C:\Users\SPIVEYA23\AppData\Local\Temp\pip-build-env-w8y0yvxq\overlay\Lib\site-packages\setuptools\_distutils\dist.py", line 1021, in run_command
          cmd_obj.run()
          ~~~~~~~~~~~^^
        File "C:\Users\SPIVEYA23\AppData\Local\Temp\pip-build-env-w8y0yvxq\overlay\Lib\site-packages\setuptools\_distutils\command\build_ext.py", line 368, in run
          self.build_extensions()
          ~~~~~~~~~~~~~~~~~~~~~^^
        File "C:\Users\SPIVEYA23\AppData\Local\Temp\pip-build-env-w8y0yvxq\overlay\Lib\site-packages\setuptools\_distutils\command\build_ext.py", line 484, in build_extensions
          self._build_extensions_serial()
          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
        File "C:\Users\SPIVEYA23\AppData\Local\Temp\pip-build-env-w8y0yvxq\overlay\Lib\site-packages\setuptools\_distutils\command\build_ext.py", line 510, in _build_extensions_serial
          self.build_extension(ext)
          ~~~~~~~~~~~~~~~~~~~~^^^^^
        File "C:\Users\SPIVEYA23\AppData\Local\Temp\pip-build-env-w8y0yvxq\overlay\Lib\site-packages\setuptools\_distutils\command\build_ext.py", line 543, in build_extension
          sources = self.swig_sources(sources, ext)
        File "C:\Users\SPIVEYA23\AppData\Local\Temp\pip-build-env-w8y0yvxq\overlay\Lib\site-packages\setuptools\_distutils\command\build_ext.py", line 641, in swig_sources
          swig = self.swig or self.find_swig()
                              ~~~~~~~~~~~~~~^^
        File "<string>", line 49, in find_swig
      AssertionError
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for jamspell
Failed to build jamspell
error: failed-wheel-build-for-install

× Failed to build installable wheels for some pyproject.toml based projects

System information:
OS: Microsoft Windows 11 Education, version 24H2, OS build 26100.6899
Python version: Python 3.17.7
Pip version: 25.2
Swig version: 3.0.12

[DragonCloudBurst]

Update: I was able to install Swig 3.0.12 properly via Chocolatey; the build still fails but gives different output.

pip install jamspell
Collecting jamspell
  Using cached jamspell-0.0.12.tar.gz (174 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Building wheels for collected packages: jamspell
  Building wheel for jamspell (pyproject.toml) ... error
  error: subprocess-exited-with-error

  × Building wheel for jamspell (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [66 lines of output]
      C:\Users\SPIVEYA23\AppData\Local\Temp\pip-build-env-j5rx_gfg\overlay\Lib\site-packages\setuptools\dist.py:599: SetuptoolsDeprecationWarning: Invalid dash-separated key 'description-file' in 'metadata' (setup.cfg), please use the underscore name 'description_file' instead.
      !!

              ********************************************************************************
              Usage of dash-separated 'description-file' will not be supported in future
              versions. Please use the underscore name 'description_file' instead.
              (Affected: jamspell).

              By 2026-Mar-03, you need to update your project and remove deprecated calls
              or your builds will no longer be supported.

              See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details.
              ********************************************************************************

      !!
        opt = self._enforce_underscore(opt, section)
      C:\Users\SPIVEYA23\AppData\Local\Temp\pip-build-env-j5rx_gfg\overlay\Lib\site-packages\setuptools\dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated.
      !!

              ********************************************************************************
              Please consider removing the following classifiers in favor of a SPDX license expression:

              License :: OSI Approved :: MIT License

              See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.
              ********************************************************************************

      !!
        self._finalize_license_expression()
      running bdist_wheel
      running build
      running build_ext
      building '_jamspell' extension
      <string>:48: DeprecationWarning: Use shutil.which instead of find_executable
      swigging jamspell.i to jamspell_wrap.cpp
      C:\Users\SPIVEYA23\Documents\swigwin-3.0.12\swigwin-3.0.12\swig.exe -python -c++ -o jamspell_wrap.cpp jamspell.i
      creating build\temp.win-amd64-cpython-313\Release\contrib\cityhash
      creating build\temp.win-amd64-cpython-313\Release\contrib\phf
      creating build\temp.win-amd64-cpython-313\Release\jamspell
      "C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.44.35207\bin\HostX86\x64\cl.exe" /c /nologo /O2 /W3 /GL /DNDEBUG /MD -I. -Ijamspell -IC:\Users\SPIVEYA23\AppData\Local\Programs\Python\Python313\include -IC:\Users\SPIVEYA23\AppData\Local\Programs\Python\Python313\Include "-IC:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.44.35207\include" "-IC:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.44.35207\ATLMFC\include" "-IC:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\VS\include" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.26100.0\ucrt" "-IC:\Program Files (x86)\Windows Kits\10\\include\10.0.26100.0\\um" "-IC:\Program Files (x86)\Windows Kits\10\\include\10.0.26100.0\\shared" "-IC:\Program Files (x86)\Windows Kits\10\\include\10.0.26100.0\\winrt" "-IC:\Program Files (x86)\Windows Kits\10\\include\10.0.26100.0\\cppwinrt" /EHsc /Tpcontrib\cityhash\city.cc /Fobuild\temp.win-amd64-cpython-313\Release\contrib\cityhash\city.obj -std=c++11 -O2
      cl : Command line warning D9002 : ignoring unknown option '-std=c++11'
      city.cc
      contrib\cityhash\city.cc(165): warning C4267: 'initializing': conversion from 'size_t' to 'uint32', possible loss of data
      contrib\cityhash\city.cc(178): warning C4267: 'argument': conversion from 'size_t' to 'uint32', possible loss of data
      contrib\cityhash\city.cc(182): warning C4267: 'initializing': conversion from 'size_t' to 'uint32', possible loss of data
      contrib\cityhash\city.cc(182): warning C4267: 'initializing': conversion from 'size_t' to 'uint32', possible loss of data
      contrib\cityhash\city.cc(197): warning C4267: 'initializing': conversion from 'size_t' to 'uint32', possible loss of data
      contrib\cityhash\city.cc(197): warning C4267: 'initializing': conversion from 'size_t' to 'uint32', possible loss of data
      contrib\cityhash\city.cc(302): warning C4267: 'initializing': conversion from 'size_t' to 'uint32', possible loss of data
      contrib\cityhash\city.cc(420): warning C4267: 'initializing': conversion from 'size_t' to 'long', possible loss of data
      "C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.44.35207\bin\HostX86\x64\cl.exe" /c /nologo /O2 /W3 /GL /DNDEBUG /MD -I. -Ijamspell -IC:\Users\SPIVEYA23\AppData\Local\Programs\Python\Python313\include -IC:\Users\SPIVEYA23\AppData\Local\Programs\Python\Python313\Include "-IC:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.44.35207\include" "-IC:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.44.35207\ATLMFC\include" "-IC:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\VS\include" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.26100.0\ucrt" "-IC:\Program Files (x86)\Windows Kits\10\\include\10.0.26100.0\\um" "-IC:\Program Files (x86)\Windows Kits\10\\include\10.0.26100.0\\shared" "-IC:\Program Files (x86)\Windows Kits\10\\include\10.0.26100.0\\winrt" "-IC:\Program Files (x86)\Windows Kits\10\\include\10.0.26100.0\\cppwinrt" /EHsc /Tpcontrib\phf\phf.cc /Fobuild\temp.win-amd64-cpython-313\Release\contrib\phf\phf.obj -std=c++11 -O2
      cl : Command line warning D9002 : ignoring unknown option '-std=c++11'
      phf.cc
      contrib\phf\phf.cc(414): warning C4244: 'argument': conversion from 'uint64_t' to 'uint32_t', possible loss of data
      contrib\phf\phf.cc(578): warning C4267: 'argument': conversion from 'size_t' to 'uint32_t', possible loss of data
      contrib\phf\phf.cc(578): note: the template instantiation context (the oldest one first) is
      contrib\phf\phf.cc(682): note: see reference to function template instantiation 'int PHF::init<uint32_t,true>(phf *,const uint32_t [],const size_t,const size_t,const size_t,const phf_seed_t)' being compiled
      contrib\phf\phf.cc(583): warning C4267: 'argument': conversion from 'size_t' to 'uint32_t', possible loss of data
      contrib\phf\phf.cc(595): warning C4267: 'argument': conversion from 'size_t' to 'uint32_t', possible loss of data
      contrib\phf\phf.cc(600): warning C4267: '=': conversion from 'size_t' to 'uint32_t', possible loss of data
      contrib\phf\phf.cc(601): warning C4267: '=': conversion from 'size_t' to 'uint32_t', possible loss of data
      "C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.44.35207\bin\HostX86\x64\cl.exe" /c /nologo /O2 /W3 /GL /DNDEBUG /MD -I. -Ijamspell -IC:\Users\SPIVEYA23\AppData\Local\Programs\Python\Python313\include -IC:\Users\SPIVEYA23\AppData\Local\Programs\Python\Python313\Include "-IC:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.44.35207\include" "-IC:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.44.35207\ATLMFC\include" "-IC:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\VS\include" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.26100.0\ucrt" "-IC:\Program Files (x86)\Windows Kits\10\\include\10.0.26100.0\\um" "-IC:\Program Files (x86)\Windows Kits\10\\include\10.0.26100.0\\shared" "-IC:\Program Files (x86)\Windows Kits\10\\include\10.0.26100.0\\winrt" "-IC:\Program Files (x86)\Windows Kits\10\\include\10.0.26100.0\\cppwinrt" /EHsc /Tpjamspell_wrap.cpp /Fobuild\temp.win-amd64-cpython-313\Release\jamspell_wrap.obj -std=c++11 -O2
      cl : Command line warning D9002 : ignoring unknown option '-std=c++11'
      jamspell_wrap.cpp
      jamspell_wrap.cpp(4724): error C3861: 'PyUnicode_GetSize': identifier not found
      error: command 'C:\\Program Files\\Microsoft Visual Studio\\2022\\Community\\VC\\Tools\\MSVC\\14.44.35207\\bin\\HostX86\\x64\\cl.exe' failed with exit code 2
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for jamspell
Failed to build jamspell
error: failed-wheel-build-for-install

× Failed to build installable wheels for some pyproject.toml based projects
╰─> jamspell

[Hacker979]

I had exactly the same problem. I ended up rewriting the build, but when I run it, the script still overloads the system and doesn't produce anything. I tried preserving the logic by writing it in Python. The percentage of correction errors was worse than SymSpell even after selecting the best values for the test, I only got a better result in one category of my test. So, basically, I created a hybrid of a symspell with a 480k dictionary, error probability checking with a key missclick, and a similar idea as in Jampspell, but without a neural network, with better results.

[DragonCloudBurst]

I had exactly the same problem. I ended up rewriting the build, but when I run it, the script still overloads the system and doesn't produce anything. I tried preserving the logic by writing it in Python. The percentage of correction errors was worse than SymSpell even after selecting the best values for the test, I only got a better result in one category of my test. So, basically, I created a hybrid of a symspell with a 480k dictionary, error probability checking with a key missclick, and a similar idea as in Jampspell, but without a neural network, with better results.

That sounds great, do you have a repo to this code that you wrote?

[Hacker979]

I had exactly the same problem. I ended up rewriting the build, but when I run it, the script still overloads the system and doesn't produce anything. I tried preserving the logic by writing it in Python. The percentage of correction errors was worse than SymSpell even after selecting the best values for the test, I only got a better result in one category of my test. So, basically, I created a hybrid of a symspell with a 480k dictionary, error probability checking with a key missclick, and a similar idea as in Jampspell, but without a neural network, with better results.

That sounds great, do you have a repo to this code that you wrote?

I'm also interested in fast and correct spell checker. I tried to install this one, but just yesterday I wrote a hybrid method and didn't finish it. You'll be able to use a symspell with a large dictionary, It's the fastest and best compared to others, and it's enough for now. Later, I'll compare my method and send you a link.

[DragonCloudBurst]

Update: I was able to get JamSpell to install specifically in a Python 3.11.0 virtual environment. I'm leaving this issue up for now, though, as I feel that it's still a problem that the program won't install at all on newer versions.

[Hacker979]

Update: I was able to get JamSpell to install specifically in a Python 3.11.0 virtual environment. I'm leaving this issue up for now, though, as I feel that it's still a problem that the program won't install at all on newer versions.

Thanks for letting me know, I tested the dictionary on half a million words, introduced all sorts of methods, and with my hybridspell reduced the errors to 0 percent compared to Sym spell of 13 percent. The percentage of words that were corrected 70 in all categories, while the others spellcheckers were less than 60, and still, when testing with unfamiliar words, there were no corrections, and the implementation of that speech in text for games is useless. I found a free way to use neural networks through LMM7.io. It works the best, but the delay is about a second per word(I didn't try to correct the whole sentence at once). With the right algorithms, I can cache everything in a frequency dictionary and I use it to speed up corrections, in conjunction with a sym spell, in your case, you can also use jamspell, I will conduct tests and let you know

[Hacker979]

Update: I was able to get JamSpell to install specifically in a Python 3.11.0 virtual environment. I'm leaving this issue up for now, though, as I feel that it's still a problem that the program won't install at all on newer versions.

I installed jamspell, but it doesn't want to give out the text, but only loads and unloads something in memory. Also, when comparing with almost unfamiliar words, my hybrid method gave 30% with 0.5% misses. And the AI was able to easily pick up 96% of the correct words with 0% misses, but it took a lot of time; changing the dictionary is much easier than making changes to the AI jamspell model every time. You can try using Symspell to get a level of confidence in a word, filtering out those that will then be processed by a slow AI, which will provide accurate data for updating the dictionary.

[DragonCloudBurst]

Update: I was able to get JamSpell to install specifically in a Python 3.11.0 virtual environment. I'm leaving this issue up for now, though, as I feel that it's still a problem that the program won't install at all on newer versions.

I installed jamspell, but it doesn't want to give out the text, but only loads and unloads something in memory. Also, when comparing with almost unfamiliar words, my hybrid method gave 30% with 0.5% misses. And the AI was able to easily pick up 96% of the correct words with 0% misses, but it took a lot of time; changing the dictionary is much easier than making changes to the AI jamspell model every time. You can try using Symspell to get a level of confidence in a word, filtering out those that will then be processed by a slow AI, which will provide accurate data for updating the dictionary.

Great, thanks for the update! I'll keep trying on my end to use JamSpell. I have a suspicion that the machine I'm running it on may be a bottleneck for the AI model, though. Fortunately, we should be getting new desktops soon...

[Hacker979]

Update: I was able to get JamSpell to install specifically in a Python 3.11.0 virtual environment. I'm leaving this issue up for now, though, as I feel that it's still a problem that the program won't install at all on newer versions.

I installed jamspell, but it doesn't want to give out the text, but only loads and unloads something in memory. Also, when comparing with almost unfamiliar words, my hybrid method gave 30% with 0.5% misses. And the AI was able to easily pick up 96% of the correct words with 0% misses, but it took a lot of time; changing the dictionary is much easier than making changes to the AI jamspell model every time. You can try using Symspell to get a level of confidence in a word, filtering out those that will then be processed by a slow AI, which will provide accurate data for updating the dictionary.

Great, thanks for the update! I'll keep trying on my end to use JamSpell. I have a suspicion that the machine I'm running it on may be a bottleneck for the AI model, though. Fortunately, we should be getting new desktops soon...

My computer is pretty good, but there's a problem with the program. I wrote a Python script that uses the same model as Jamspell, but the results are worse than the alternatives. While finding good datasets is difficult, the model requires further training.