searxng/.git - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2025-10-22	[fix] Installation Script install fails (msgspec) (#5353)	Markus Heiser
	Since #5280 has been merged, msgspec, like yaml, is a fixed part of the SearXNG settings framework and therefore, like yaml, must be installed in the virtual environment before installing SearXNG (``searx``). The actual reason is that in SearXNG we store settings in the configuration that are required for the installation of the ``searx`` package. This means that these settings (from settings.yml) are read in during the installation, and all the necessary tools for this (pyyaml, msgspec, setuptools, etc.) must be installed beforehand (chicken or the egg dilemma). Related: - https://github.com/searxng/searxng/pull/5346 - https://github.com/searxng/searxng/pull/5280 - https://github.com/searxng/searxng/pull/5254 Closes: https://github.com/searxng/searxng/issues/5352
2024-10-03	[mod] py3.8 EOL / upgrade to actions/setup-python@v5	Markus Heiser
	Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
2024-08-21	[fix] pip install -e: legacy editable install (setup.py develop) is deprecated	Markus Heiser
	From [1]: There is now a standardized mechanism [2] for an installer like pip to request an editable install of a project. pip is transitioning to using this standard only instead of invoking the deprecated `setup.py develop` command. For backward compatibility, we can use switches: --use-pep517 https://pip.pypa.io/en/stable/cli/pip_install/#cmdoption-use-pep517 --no-build-isolation https://pip.pypa.io/en/stable/cli/pip_install/#cmdoption-no-build-isolation - [1] https://github.com/pypa/pip/issues/11457 - [2] https://peps.python.org/pep-0660/ Closes: https://github.com/searxng/searxng/issues/3701 Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
2022-07-30	[doc] update documentation of the installation procedures	Markus Heiser
	Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>