Your message dated Thu, 10 May 2018 07:46:26 +0200
with message-id <152593118694.8897.12543814977938294682@localhost>
and subject line Re: python3-searx: searx fails to import
has caused the Debian Bug report #896270,
regarding python3-searx: searx fails to import
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
896270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896270
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python3-searx
Version: 0.14.0+dfsg1-2
Severity: serious
User: [email protected]
Usertags: python-import
After installing python3-searx importing the module searx
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/usr/lib/python3/dist-packages/searx/__init__.py", line 51, in <module>
raise Exception('settings.yml not found')
Exception: settings.yml not found
The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.
Helmut
--- End Message ---
--- Begin Message ---
On Fri, 20 Apr 2018 22:01:34 +0200 Helmut Grohne <[email protected]> wrote:
> After installing python3-searx importing the module searx
> into a python interpreter fails with the following error:
>
> Traceback (most recent call last):
> File "<string>", line 1, in <module>
> File "/usr/lib/python3/dist-packages/searx/__init__.py", line 51, in
> <module>
> raise Exception('settings.yml not found')
> Exception: settings.yml not found
>
> The vast majority of import failures is attributed to missing dependencies.
> Often times that manifests as an ImportError or ModuleNotFoundError.
> Typically, dependencies should be inserted by dh-python via ${python:Depends}
> or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
> install_requires in setup.py. Sometimes a missing dependency of a dependency
> is the cause, in such cases this bug should be reassigned.
Yes, this is expected because the Python module is useless without the
settings.yml. The user has to put the file either under the same path as the
script itself or under /etc/searx/settings.yml or provide the path via
$SEARX_SETTINGS_PATH. There is currently no support for this module to work
without settings.yml. Additionally, there is also no Debian package that ships
/etc/searx/settings.yml, so a dependency cannot be added to fix this issue.
Thus, closing this bug.
Thanks!
cheers, josch
signature.asc
Description: signature
--- End Message ---
