Hi,

Quoting Pelle Hjek (2018-03-02 13:03:36)
> Joseph Nuthalapati wrote:
> > >  SearX currently doesn't start up when run with Python 3 as it tries
> > >  to parse the settings.yml file with ASCII codecs.
> Johannes Schauer wrote:
> > Please provide more support for your theory.
> I am encountering what is possibly the same bug here. I will just
> provide the error message rather than making up a theory of why it
> happens.
> 
> When I run `searx-run`, I get this error:
> ```
> Traceback (most recent call last):
>   File "/usr/bin/searx-run", line 11, in <module>
>     load_entry_point('searx==0.14.0', 'console_scripts', 'searx-run')()
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 572, 
> in load_entry_point
>     return get_distribution(dist).load_entry_point(group, name)
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2755, 
> in load_entry_point
>     return ep.load()
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2408, 
> in load
>     return self.resolve()
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2414, 
> in resolve
>     module = __import__(self.module_name, fromlist=['__name__'], level=0)
>   File "/usr/lib/python3/dist-packages/searx/__init__.py", line 51, in 
> <module>
>     raise Exception('settings.yml not found')
> Exception: settings.yml not found
> ```

This does not indicate that it's the same bug. This bug is about settings.yml
not being parsed. This bug is not about settings.yml not being found.

> I also tried copying the default settings.yml to the folder I run searx
> in, like this:
> ```
> 7z x /usr/share/doc/searx/examples/settings.yml.gz
> ```
> but I get the same error.

Does reading /usr/share/doc/python3-searx/README.Debian fix your issue?

Specifically, take care that you choose the right path for your settings.yml

Attachment: signature.asc
Description: signature

Reply via email to