conftest - auto-debug

The conftest.py file has been missing - this is an old project, and almost all the scaffolding is done by setup and teardown methods.  This commit does not do anything with that, but if pytest is run with the --pdb flag, then enable some  debug-on-assert hook in the code

Author: tobixen

CHANGELOG.md

@@ -14,10 +14,19 @@ This project should adhere to [Semantic Versioning](https://semver.org/spec/v2.0
 
 ## [Unreleased]
 
+### Added
+
+* **OX App Suite** compatibility hints added; the library is now tested against OX App Suite via a new Docker test server (`tests/docker-test-servers/ox/`).
+* New `search.unlimited-time-range` feature flag with a workaround in `search.py` that injects a broad time range (1970–2126) for servers that return an empty result set when no time range is specified.
+
 ### Fixed
 
 * `AsyncDAVClient` failed to initialize when using httpx < 0.23.0 because `proxy=None` was unconditionally passed to `httpx.AsyncClient` which did not accept a `proxy` keyword argument in older releases.  Fixes https://github.com/python-caldav/caldav/issues/632
 
+### Potentially Breaking Changes
+
+* The compatibility-hint key `search.comp-type-optional` has been renamed to `search.comp-type.optional` for consistency with the dotted-key naming convention used elsewhere.  If you have this key set in a local server configuration, update it accordingly.
+
 ## [3.0.0] - 2026-03-03
 
 Version 3.0 should be fully backward-compatible with version 2.x - but there are massive code changes in version 3.0, so if you're using the Python CalDAV client library in some sharp production environment, I would recommend to wait for two months before upgrading.

docs/design/RELEASE-HOWTO.md

@@ -8,7 +8,7 @@ I have no clue on the proper procedures for doing releases, and I keep on doing
 
 * Go through changes since last release and compare it with the `CHANGELOG.md`.  Any change should be logged.
 * Run tests towards as many servers as possible
-  * Use the `PYTHON_CALDAV_DEBUGMODE=pdb` environment variable!  Should do some research if we hit any "soft asserts" or "weirdness".
+  * Use the `PYTHON_CALDAV_DEBUGMODE=DEBUG_PDB` environment variable (or simply pass `--pdb` to pytest, which sets this automatically)!  Should do some research if we hit any "soft asserts" or "weirdness".
   * Do research on breakages.  If the test breaks also for the previous release of the caldav library, then it's likely to be due to some regression on the server side.  For patch-level releases we don't care about such breakages, for minor-level releases we should try to work around problems
   * It's proper to document somewhere (TODO: where?  how?) what servers have been tested
 * Does any of the changes require documentation to be rewritten?  The documentation should ideally be in sync with the code upon release time.

tests/conftest.py

@@ -0,0 +1,11 @@
+import os
+
+
+def pytest_configure(config):
+    """Set PYTHON_CALDAV_DEBUGMODE=DEBUG_PDB automatically when --pdb is passed.
+
+    This must happen in pytest_configure (before test collection) because
+    caldav.lib.error reads the env var at module import time.
+    """
+    if config.option.usepdb and "PYTHON_CALDAV_DEBUGMODE" not in os.environ:
+        os.environ["PYTHON_CALDAV_DEBUGMODE"] = "DEBUG_PDB"