fix(docs): consolidate style documentation

- consistently use uv to install and test
- avoid legacy naming for pytest
- remove some outdated ignores

Author: nijel

AGENTS.md

@@ -27,7 +27,8 @@ For application-developer workflows and broader product integration guidance, us
   `<type>(<optional scope>): <description>`. Common types include `feat`,
   `fix`, `docs`, `refactor`, `test`, `ci`, and `chore`. Example:
   `fix(translations): handle empty component slug`.
-- Include the GPL-3.0-or-later license header in new Python files.
+- Keep new project code under GPL-3.0-or-later and include the repository's
+  usual copyright and SPDX license header in new Python files.
 
 ## Documentation expectations
 
@@ -72,15 +73,18 @@ For application-developer workflows and broader product integration guidance, us
 - After syncing, prefer `uv run ...` for subsequent commands so they use the
   virtual environment created in `.venv`. If needed, you can also activate it
   with `source .venv/bin/activate` or invoke tools from `.venv/bin/`.
-- Prefer `prek run --all-files` as the primary linting/formatting command because
+- Prefer `uv run prek run --all-files` as the primary linting/formatting command because
   it runs the repository's configured pre-commit framework checks.
 - `prek` is a third-party reimplementation of the `pre-commit` tool.
-- Use `pytest` to run the test suite: `pytest weblate`. On a fresh checkout,
+- Use `pytest` to run the test suite: `uv run pytest`. On a fresh checkout,
   first follow the local test setup in `docs/contributing/tests.rst`
   (`DJANGO_SETTINGS_MODULE=weblate.settings_test`, `collectstatic`, and test
   database prerequisites). `scripts/test-database.sh` can be sourced to set up
   the database connection variables such as `CI_DB_USER`, `CI_DB_PASSWORD`,
   `CI_DB_HOST`, and `CI_DB_PORT`.
-- Use `pylint` to lint the Python code: `pylint weblate/`
-- Use `mypy` to type check the code: `mypy weblate/`
-- All mentioned linting tools MUST pass.
+- Use `pylint` to lint the Python code: `uv run pylint weblate/ scripts/`
+- Use `mypy` to type check with the same command as CI:
+  `uv run mypy --show-column-numbers weblate scripts/*.py ./*.py | ./scripts/filter-mypy.sh`.
+- New or changed code should not introduce new mypy failures where current
+  Django typing support makes that practical. Existing non-enforced mypy
+  findings should not be worsened.

docs/admin/install/source.rst

@@ -24,8 +24,9 @@ Installing from sources
 
         . ~/weblate-env/bin/activate
         uv pip install -e 'weblate-src[all]'
-        # In case you intentd to run testsuite, install test deps as well:
-        uv pip install -e 'weblate-src[all,test]'
+
+   If you intend to run the testsuite from the source checkout, install the
+   development dependencies as described in :ref:`local-tests`.
 
 #. Copy :file:`weblate/settings_example.py` to :file:`weblate/settings.py`.
 

docs/contributing/frontend.rst

@@ -28,10 +28,10 @@ Prerequisites
 
 Before proceeding with an installation, make sure you have the following prerequisites:
 
-- ``Nodejs`` version 14 or higher.
+- A supported ``Node.js`` release.
 - The ``yarn`` package manager is installed on your system.
 - Run ``cd client``.
-- Run ``yarn install``.
+- Run ``yarn install --check-files``.
 
 Installation
 ++++++++++++
@@ -88,7 +88,9 @@ Now the library is built and ready for use. To include it follow these steps:
 Coding style
 ------------
 
-Weblate relies on `Biome`_ for formatting and linting the JavaScript and CSS code.
+Weblate relies on `Biome`_ for formatting and linting the JavaScript and CSS
+code. Django templates are formatted and linted separately by :program:`djade`
+and :program:`djlint`.
 
 .. _Biome: https://biomejs.dev/
 
@@ -102,16 +104,16 @@ function, but there are more complex features available:
 
 .. code-block:: javascript
 
-    document.write(gettext('this is to be translated'));
+    document.write(gettext("this is to be translated"));
 
     var object_count = 1 // or 0, or 2, or 3, ...
-    s = ngettext('literal for the singular case',
-            'literal for the plural case', object_count);
+    s = ngettext("literal for the singular case",
+            "literal for the plural case", object_count);
 
-    fmts = ngettext('There is %s object. Remaining: %s',
-            'There are %s objects. Remaining: %s', 11);
+    fmts = ngettext("There is %s object. Remaining: %s",
+            "There are %s objects. Remaining: %s", 11);
     s = interpolate(fmts, [11, 20]);
-    // s is 'There are 11 objects. Remaining: 20'
+    // s is "There are 11 objects. Remaining: 20"
 
 .. seealso::
 

docs/contributing/snippets/code-guide.rst

@@ -2,9 +2,14 @@
 License and copyright
 ---------------------
 
-When contributing code, you agree to put your changes and new code under the
-same license as the repository is already using, unless stated and agreed
-otherwise.
+When contributing project code, you agree to put your changes and new code
+under the repository license, :abbr:`GPL-3.0-or-later (GNU General Public
+License v3.0 or later)`, unless stated and agreed otherwise. New source files
+should follow the existing copyright and :abbr:`SPDX (Software Package Data
+Exchange)` license header style.
+
+Use a different license only when there is a deliberate reason, such as files
+shared with repositories using more permissive licenses.
 
 .. seealso::
 
@@ -66,11 +71,14 @@ Type checking
 ~~~~~~~~~~~~~
 
 Any new code should utilize :pep:`484` type hints. We are using :program:`mypy`
-to check (because it has a Django plugin that makes type checking of Django
-apps doable).
+to check them because it has a Django plugin that makes type checking of Django
+apps practical.
 
-The code base is not yet completely covered by type annotations, but some
-modules are already enforced for type checking in the CI.
+New and changed code should not introduce new :program:`mypy` failures where
+current Django typing support makes that practical. The code base is not yet
+completely covered by type annotations, and some Django constructs are
+difficult to annotate precisely. CI therefore enforces :program:`mypy` only for
+selected modules and reports other findings separately.
 
 Coding standard and linting the code
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -90,7 +98,7 @@ To check all files manually, run:
 
 .. code-block:: sh
 
-    prek run --all-files
+    uv run prek run --all-files
 
 If you prefer the original :program:`pre-commit` client, it uses the same
 configuration from :file:`.pre-commit-config.yaml`.

docs/contributing/start.rst

@@ -27,37 +27,30 @@ sources.
       git clone https://github.com/WeblateOrg/weblate.git
       cd weblate
 
-2. Create a Python environment:
+2. Install Weblate and all dependencies useful for development:
 
    .. code-block:: sh
 
-      uv venv .venv
-      source .venv/bin/activate
-
-3. Install Weblate (for this you need some system dependencies, see :doc:`../admin/install/source`) and all dependencies useful for development:
-
-   .. code-block:: sh
-
-      uv pip install -e '.[dev]'
+      uv sync --all-extras --dev
 
 3. Start a development server:
 
    .. code-block:: sh
 
-      weblate runserver
+      uv run weblate runserver
 
 4. Depending on your configuration, you might also want to start Celery workers:
 
    .. code-block:: sh
 
-      ./weblate/examples/celery start
+      uv run ./weblate/examples/celery start
 
-5. To run a test (see :ref:`local-tests` for more details):
+5. To run tests (see :ref:`local-tests` for more details):
 
    .. code-block:: sh
 
       . scripts/test-database.sh
-      pytest
+      uv run pytest
 
 .. seealso::
 
@@ -143,15 +136,15 @@ to use:
 
 .. image:: /images/pycharm-1.png
 
-You can either choose to let PyCharm create the Python environment for you, or select an already
-existing one:
+Select the :file:`.venv` environment created by ``uv sync --all-extras --dev``
+to match the command-line development setup. You can also let PyCharm create a
+Python environment for you, but the uv-managed environment is preferred:
 
 .. image:: /images/pycharm-2.png
 
-Don't forget to install the dependencies once the interpreter is set:
-Either through the console (the console from the IDE will directly use your
-Python environment by default), or through the interface when you get a warning about missing
-dependencies.
+Don't forget to install the dependencies once the interpreter is set. When
+using the preferred uv-managed environment, run ``uv sync --all-extras --dev``
+from the console.
 
 The second step is to set the right info to use Django natively inside PyCharm:
 The idea is to be able to immediately trigger the unit tests in the IDE.

docs/contributing/tests.rst

@@ -53,7 +53,11 @@ The simple execution can look like:
 Local testing of Weblate
 +++++++++++++++++++++++++
 
-Before running test, please ensure test dependencies are installed. This can be done by ``pip install -e .[test]``.
+Before running tests, please ensure development dependencies are installed:
+
+.. code-block:: sh
+
+   uv sync --all-extras --dev
 
 Testing using pytest
 ~~~~~~~~~~~~~~~~~~~~
@@ -62,19 +66,19 @@ Prior to running tests you should collect static files as some tests rely on the
 
 .. code-block:: sh
 
-    DJANGO_SETTINGS_MODULE=weblate.settings_test ./manage.py collectstatic
+    DJANGO_SETTINGS_MODULE=weblate.settings_test uv run ./manage.py collectstatic --noinput
 
-You can use `pytest` to run a testsuite locally:
+You can use `pytest` to run the test suite locally:
 
 .. code-block:: sh
 
-   pytest weblate
+   uv run pytest
 
 Running an individual test file:
 
 .. code-block:: sh
 
-   pytest weblate/utils/tests/test_search.py
+   uv run pytest weblate/utils/tests/test_search.py
 
 .. hint::
 
@@ -108,17 +112,17 @@ The :file:`weblate/settings_test.py` is used in CI environment as well (see
 Local testing of Weblate modules
 --------------------------------
 
-The tests are executed using :program:`py.test`. First you need to install test requirements:
+The tests are executed using :program:`pytest`. First you need to install development dependencies:
 
 .. code-block:: sh
 
-   uv pip install -e '.[dev]'
+   uv sync --all-extras --dev
 
 You can then execute the testsuite in the repository checkout:
 
 .. code-block:: sh
 
-   py.test
+   uv run pytest
 
 .. _test-data:
 

pyproject.toml

@@ -295,7 +295,6 @@ ignore = [
   ".gitmodules",
   ".imgbotconfig",
   ".reuse/dep5",
-  ".stylelintrc",
   ".weblate",
   ".well-known/*",
   ".yamllint.yml",
@@ -592,13 +591,13 @@ ignore = [
   "DOC402",  # CONFIG: `yield` is not documented in docstring
   "DOC501",  # TODO: Raised exception missing from docstring
   "E203",  # CONFIG: formatter
-  "E501",  # WONTFIX: we accept long strings (rest is formatted by black)
+  "E501",  # WONTFIX: we accept long strings (rest is formatted by Ruff)
   "FBT",  # TODO: Boolean in function definition
   "FIX002",  # CONFIG: we use TODO
   "PLR2004",  # TODO: Magic value used in comparison, consider replacing 201 with a constant variable
   "PLR6301",  # TODO: Method could be a function, class method, or static method
   "PLW2901",  # TODO: overwriting variables inside loop
-  "PT",  # CONFIG: Not using pytest
+  "PT",  # CONFIG: pytest-style rules are not enforced
   "PTH",  # TODO: Not using pathlib
   "RUF001",  # WONTFIX: String contains ambiguous unicode character, we are using Unicode
   "TD002",  # CONFIG: no detailed TODO documentation is required