searxng/searx/engines/init.py, branch master

[fix] engine: meilisearch - AttributeError: no attribute 'about' (#6626)

2026-09-02T12:26:22Z

- Closes: https://github.com/searxng/searxng/issues/6622 Signed-off-by: Markus Heiser

[fix] clarify the mess of Engine.setup and Engine.init (#6343)

2026-06-30T17:22:23Z

Signed-off-by: Markus Heiser

[chore] add DeprecationWarning for obsolete engine.about.language property (#6265)

2026-06-16T08:31:21Z

The old property should still be supported for a transitional period; the reasons for this can be seen from the discussion in [1] / the further procedure is also discussed there. [1] https://github.com/searxng/searxng/issues/6261 Signed-off-by: Markus Heiser

[fix] set language_support for engines with languages in traits (#6258)

2026-06-15T08:52:00Z

In the past, the engine option ``language_support`` was not consistently maintained; with this patch, a ValueError is now thrown if an engine has languages in its traits but language_support is not set to True. Signed-off-by: Markus Heiser

[chore] complete and normalize the attributes of engine objects (#6258)

2026-06-15T08:52:00Z

Drop outdated engine attributes: supported_languages, language_aliases Complete, normalize and document the type definitions for the engine-module and engine-class. For the ``engine.about`` section of the configuration, a type check is performed based on structure ``searx.enginelib.EngineAbout``. The property ``engine.about.language`` no longer exists; existing values have been migrated to ``engine.language``. Signed-off-by: Markus Heiser

[fix] sqlitedb: create DB Schema (DDL) during app initialization (hardening) (#6187)

2026-06-10T13:48:49Z

The initialization of the DB schema ("base schema") has so far been done on demand, which causes race conditions with competing threads and processes. The DDL statements for creating the "base schema" are now executed as part of the initialization of the app. Further improvements were made to harden the database applications: - Wikidata & Radio-Browser engine perform their initialization only once (so far the initialization was carried out in each thread/process). - If multiple processes try to set DB's WAL mode when opening the DB at the same time, this usually leads to another race condition, which is now also caught. Related: - https://github.com/searxng/searxng/issues/6181#issuecomment-4586705 Closes: #6181 Signed-off-by: Markus Heiser

[mod] online engines - set common HTTP headers

2026-02-22T08:30:16Z

The online engines emulate a request as it would come from a web browser, which is why the HTTP headers in the default settings should also be set the way a standard web browser would set them. Signed-off-by: Markus Heiser

[fix] engines initialization - if engine load fails, set to inactive

2025-11-25T05:25:45Z

- if engine load fails, set the engine to inactive - dont' load a engine, when the config says its inactive Signed-off-by: Markus Heiser

[mod] addition of various type hints / engine processors

2025-09-18T17:40:03Z

Continuation of #5147 .. typification of the engine processors. BTW: - removed obsolete engine property https_support - fixed & improved currency_convert - engine instances can now implement a engine.setup method [#5147] https://github.com/searxng/searxng/pull/5147 Signed-off-by: Markus Heiser

[mod] drop: from future import annotations

2025-09-03T11:37:36Z