Skip to content

test: restore tilia.constants after re-importing it #622

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
azfoo merged 1 commit into from
Oct 2, 2026
Merged

test: restore tilia.constants after re-importing it #622

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions tests/test_constants.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,24 @@
import sys
from unittest.mock import patch

import pytest

import tilia
import tilia.constants


@pytest.fixture(autouse=True)
def restore_constants_module(monkeypatch):
"""
These tests import tilia.constants afresh, which leaves the new module
in sys.modules and on the tilia package. Other code reads it through
both (`from tilia.constants import APP_NAME`, `tilia.constants.APP_NAME`),
so a copy built with mocked metadata would leak into every later test
in the same process. Put the original back afterwards.
"""
monkeypatch.setitem(sys.modules, "tilia.constants", tilia.constants)
monkeypatch.setattr(tilia, "constants", tilia.constants)


def test_tilia_metadata_not_found():
# If tilia.constants was already imported, we must remove it from sys.modules
Expand Down
Loading