pyproject.toml [tool.pytest.ini_options] have no effect in uv run pytest

[MrMegaMango]

uv run pytest services/api/core/tasks/tests/test_notifications.py

[The-Compiler]

You'll need to say a bit more than just the equivalent of "it doesn't work", as it seems to work just fine:

pyproject.toml (from uv init and uv add --dev pytest pytest-env):

[project]
name = "env-uv"
version = "0.1.0"
description = "Add your description here"
readme = "README.md"
requires-python = ">=3.13"
dependencies = []

[dependency-groups]
dev = [
    "pytest>=8.3.4",
    "pytest-env>=1.1.5",
]

[tool.pytest.ini_options]
env = [
    "ENVVAR=test",
]

test_x.py:

import os

def test_var():
    assert os.environ["ENVVAR"] == "test"

result:

$ uv run pytest --no-header
============================= test session starts ==============================
collected 1 item                                                               

test_x.py .                                                              [100%]

============================== 1 passed in 0.00s ===============================

[MrMegaMango]

Thanks for the response, I'll dig on my end

[MrMegaMango]

I updated the initial post

[The-Compiler]

Please show the full output of the pytest run.

[MrMegaMango]

[RonnyPfannschmidt]

Please use copy of the text instead of Screenshots

[MrMegaMango]

(karmacode) ➜  karmacode git:(zuo/speed-up-github-action) ✗ uv run pytest services/api/core/tasks/tests/test_notifications.py
/Users/zuowang/Code/fresh/karmacode/.venv/lib/python3.11/site-packages/pytest_asyncio/plugin.py:207: PytestDeprecationWarning: The configuration option "asyncio_default_fixture_loop_scope" is unset.
The event loop scope for asynchronous fixtures will default to the fixture caching scope. Future versions of pytest-asyncio will default the loop scope for asynchronous fixtures to function scope. Set the default fixture loop scope explicitly in order to avoid unexpected behavior in the future. Valid fixture loop scopes are: "function", "class", "module", "package", "session"

  warnings.warn(PytestDeprecationWarning(_DEFAULT_FIXTURE_LOOP_SCOPE_UNSET))
========================================================================================================== test session starts ===========================================================================================================
platform darwin -- Python 3.11.10, pytest-8.3.3, pluggy-1.5.0
django: version: 5.1.4, settings: samaya_api.settings (from ini)
rootdir: /Users/zuowang/Code/fresh/karmacode/services/api
configfile: pyproject.toml
plugins: respx-0.20.2, env-1.1.5, Faker-15.0.0, django-4.9.0, asyncio-0.25.0, anyio-3.6.2, xdist-3.6.1
asyncio: mode=Mode.STRICT, asyncio_default_fixture_loop_scope=None
collected 2 items                                                                                                                                                                                                                        

services/api/core/tasks/tests/test_notifications.py .F                                                                                                                                                                             [100%]

================================================================================================================ FAILURES ================================================================================================================
______________________________________________________________________________________ TestSendNotificationsTask.test_send_notifications_for_search ______________________________________________________________________________________

self = <services.api.core.tasks.tests.test_notifications.TestSendNotificationsTask testMethod=test_send_notifications_for_search>

    def test_send_notifications_for_search(self):
        print("enable?", os.environ["TRACER_ENABLE"])
>       self.assertEqual(True, False)
E       AssertionError: True != False

services/api/core/tasks/tests/test_notifications.py:25: AssertionError
---------------------------------------------------------------------------------------------------------- Captured stdout call ----------------------------------------------------------------------------------------------------------
enable? True
============================================================================================================ warnings summary ============================================================================================================
.venv/lib/python3.11/site-packages/pythonjsonlogger/jsonlogger.py:11
  /Users/zuowang/Code/fresh/karmacode/.venv/lib/python3.11/site-packages/pythonjsonlogger/jsonlogger.py:11: DeprecationWarning: pythonjsonlogger.jsonlogger has been moved to pythonjsonlogger.json
    warnings.warn(

.venv/lib/python3.11/site-packages/pydantic/_internal/_config.py:295: 15 warnings
  /Users/zuowang/Code/fresh/karmacode/.venv/lib/python3.11/site-packages/pydantic/_internal/_config.py:295: PydanticDeprecatedSince20: Support for class-based `config` is deprecated, use ConfigDict instead. Deprecated in Pydantic V2.0 to be removed in V3.0. See Pydantic V2 Migration Guide at https://errors.pydantic.dev/2.10/migration/
    warnings.warn(DEPRECATION_MESSAGE, DeprecationWarning)

karmacode/datamodels/data_sources.py:73
  /Users/zuowang/Code/fresh/karmacode/karmacode/datamodels/data_sources.py:73: PydanticDeprecatedSince20: Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details. Deprecated in Pydantic V2.0 to be removed in V3.0. See Pydantic V2 Migration Guide at https://errors.pydantic.dev/2.10/migration/
    @validator("kms_key", pre=True, always=True)

karmacode/datamodels/dto/document_service/document_metadata.py:132
  /Users/zuowang/Code/fresh/karmacode/karmacode/datamodels/dto/document_service/document_metadata.py:132: PydanticDeprecatedSince20: Pydantic V1 style `@root_validator` validators are deprecated. You should migrate to Pydantic V2 style `@model_validator` validators, see the migration guide for more details. Deprecated in Pydantic V2.0 to be removed in V3.0. See Pydantic V2 Migration Guide at https://errors.pydantic.dev/2.10/migration/
    @root_validator(pre=True)

services/api/graphql_api/company_groupings_data.py:673: 11 warnings
  /Users/zuowang/Code/fresh/karmacode/services/api/graphql_api/company_groupings_data.py:673: PydanticDeprecatedSince20: The `parse_obj` method is deprecated; use `model_validate` instead. Deprecated in Pydantic V2.0 to be removed in V3.0. See Pydantic V2 Migration Guide at https://errors.pydantic.dev/2.10/migration/
    HardcodedSectors: list[NamedGroupOfCompanies] = list(

services/api/graphql_api/company_groupings_data.py:1756: 17 warnings
  /Users/zuowang/Code/fresh/karmacode/services/api/graphql_api/company_groupings_data.py:1756: PydanticDeprecatedSince20: The `parse_obj` method is deprecated; use `model_validate` instead. Deprecated in Pydantic V2.0 to be removed in V3.0. See Pydantic V2 Migration Guide at https://errors.pydantic.dev/2.10/migration/
    HardcodedSubIndustries: list[NamedGroupOfCompanies] = list(

.venv/lib/python3.11/site-packages/pydantic/fields.py:1042
  /Users/zuowang/Code/fresh/karmacode/.venv/lib/python3.11/site-packages/pydantic/fields.py:1042: PydanticDeprecatedSince20: Using extra keyword arguments on `Field` is deprecated and will be removed. Use `json_schema_extra` instead. (Extra keys: 'descriptions'). Deprecated in Pydantic V2.0 to be removed in V3.0. See Pydantic V2 Migration Guide at https://errors.pydantic.dev/2.10/migration/
    warn(

karmacode/datamodels/dto/document_service/document_search.py:185
  /Users/zuowang/Code/fresh/karmacode/karmacode/datamodels/dto/document_service/document_search.py:185: PydanticDeprecatedSince20: Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details. Deprecated in Pydantic V2.0 to be removed in V3.0. See Pydantic V2 Migration Guide at https://errors.pydantic.dev/2.10/migration/
    @validator("date_range_start", "date_range_end")

karmacode/datamodels/dto/document_service/document_search.py:195
  /Users/zuowang/Code/fresh/karmacode/karmacode/datamodels/dto/document_service/document_search.py:195: PydanticDeprecatedSince20: Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details. Deprecated in Pydantic V2.0 to be removed in V3.0. See Pydantic V2 Migration Guide at https://errors.pydantic.dev/2.10/migration/
    @validator("document_type")

karmacode/datamodels/query_prep.py:418
  /Users/zuowang/Code/fresh/karmacode/karmacode/datamodels/query_prep.py:418: PydanticDeprecatedSince20: Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details. Deprecated in Pydantic V2.0 to be removed in V3.0. See Pydantic V2 Migration Guide at https://errors.pydantic.dev/2.10/migration/
    @validator("mentions")

karmacode/datamodels/query_prep.py:426
  /Users/zuowang/Code/fresh/karmacode/karmacode/datamodels/query_prep.py:426: PydanticDeprecatedSince20: Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details. Deprecated in Pydantic V2.0 to be removed in V3.0. See Pydantic V2 Migration Guide at https://errors.pydantic.dev/2.10/migration/
    @validator("templates")

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
======================================================================================================== short test summary info =========================================================================================================
FAILED services/api/core/tasks/tests/test_notifications.py::TestSendNotificationsTask::test_send_notifications_for_search - AssertionError: True != False
================================================================================================ 1 failed, 1 passed, 51 warnings in 2.77s ================================================================================================

[The-Compiler]

If the setting had no effect, then you would get a KeyError in the test because the environment variable isn't set. What happens however is that it is set to another value. The only way this could have happened is because your code overrides the value that's been set by pytest-env somewhere.

[MrMegaMango]

Can I set pytest-env to override existing env var?

➜ echo $TRACER_ENABLE       
True
➜  unset TRACER_ENABLE                                              
➜  echo $TRACER_ENABLE
➜  uv run pytest services/api/core/tasks/tests/test_notifications.py
_________________________________________________________________________________________ TestSendNotificationsTask.test_send_notifications_for_search __________________________________________________________________________________________

self = <services.api.core.tasks.tests.test_notifications.TestSendNotificationsTask testMethod=test_send_notifications_for_search>

    def test_send_notifications_for_search(self):
>       print("enable?", os.environ["TRACER_ENABLE"])

services/api/core/tasks/tests/test_notifications.py:24: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = environ({'AMPLITUDE_API_KEY': 'e0cd62fc9a72ae14949f8cb86f9f1778', 'API_LOC': 'local', 'AWS_ACCESS_KEY': 'AKIAUDEXEBPEI...TEST': 'core/tasks/tests/test_notifications.py::TestSendNotificationsTask::test_send_notifications_for_search (call)'})
key = 'TRACER_ENABLE'

>   ???
E   KeyError: 'TRACER_ENABLE'

<frozen os>:679: KeyError

[MrMegaMango]

should I create a minimal reproducible example?

[gaborbernat]

Definitely.