V 3.0-dev - async support and misc

.github/workflows/linkcheck.yml

@@ -0,0 +1,18 @@
+name: Link check
+
+on: [push, pull_request]
+
+jobs:
+  linkcheck:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v4
+    - name: Check links with Lychee
+      uses: lycheeverse/lychee-action@v2
+      with:
+        fail: true
+        args: >-
+          --timeout 10
+          --max-retries 2
+          '**/*.md'
+          '**/*.rst'

.github/workflows/tests.yaml

@@ -14,7 +14,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        python: ${{ github.event_name == 'pull_request' && fromJSON('["3.9", "3.14"]') || fromJSON('["3.9", "3.10", "3.11", "3.12", "3.13", "3.14"]') }}
+        python: ${{ github.event_name == 'pull_request' && fromJSON('["3.10", "3.14"]') || fromJSON('["3.10", "3.11", "3.12", "3.13", "3.14"]') }}
     services:
       baikal:
         image: ckulka/baikal:nginx
@@ -144,7 +144,7 @@ jobs:
           docker exec ${{ job.services.nextcloud.id }} php occ app:disable password_policy || true
 
           # Create test user
-          docker exec -e OC_PASS="TestPassword123!" ${{ job.services.nextcloud.id }} php occ user:add --password-from-env --display-name="Test User" testuser || echo "User may already exist"
+          docker exec -e OC_PASS="testpass" ${{ job.services.nextcloud.id }} php occ user:add --password-from-env --display-name="Test User" testuser || echo "User may already exist"
 
           # Enable calendar and contacts apps
           docker exec ${{ job.services.nextcloud.id }} php occ app:enable calendar || true
@@ -326,3 +326,50 @@ jobs:
           key: pip|${{ hashFiles('setup.py') }}|${{ hashFiles('tox.ini') }}
       - run: pip install tox
       - run: tox -e deptry
+  async-niquests:
+    # Test that async code works with niquests when httpx is not installed
+    name: async (niquests fallback)
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - name: Install dependencies without httpx
+        run: |
+          pip install --editable .[test]
+          pip uninstall -y httpx
+      - name: Verify niquests is used
+        run: |
+          python -c "
+          from caldav.async_davclient import _USE_HTTPX, _USE_NIQUESTS
+          assert not _USE_HTTPX, 'httpx should not be available'
+          assert _USE_NIQUESTS, 'niquests should be used'
+          print('✓ Using niquests for async HTTP')
+          "
+      - name: Run async tests with niquests
+        run: pytest tests/test_async_davclient.py -v
+  sync-requests:
+    # Test that sync code works with requests when niquests is not installed
+    name: sync (requests fallback)
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - name: Install dependencies with requests instead of niquests
+        run: |
+          pip install --editable .[test]
+          pip uninstall -y niquests
+          pip install requests
+      - name: Verify requests is used
+        run: |
+          python -c "
+          from caldav.davclient import _USE_REQUESTS, _USE_NIQUESTS
+          assert _USE_REQUESTS, 'requests should be available'
+          assert not _USE_NIQUESTS, 'niquests should not be available'
+          print('✓ Using requests for sync HTTP')
+          "
+      - name: Run sync tests with requests
+        run: pytest tests/test_caldav.py -v -k "Radicale" --ignore=tests/test_async_integration.py

.lycheeignore

@@ -0,0 +1,20 @@
+# Example domains that don't resolve
+https?://your\.server\.example\.com/.*
+https?://.*\.example\.com/.*
+
+# Localhost URLs for test servers (not accessible in CI)
+http://localhost:\d+/.*
+
+# CalDAV endpoints that require authentication (401/403 expected)
+https://caldav\.fastmail\.com/.*
+https://caldav\.gmx\.net/.*
+https://caldav\.icloud\.com/.*
+https://p\d+-caldav\.icloud\.com/.*
+https://posteo\.de:\d+/.*
+https://purelymail\.com/.*
+https://webmail\.all-inkl\.com/.*
+https://www\.google\.com/calendar/dav/.*
+https://caldav-jp\.larksuite\.com/.*
+
+# Apple namespace URL (returns 404 but is a valid XML namespace reference)
+http://apple\.com/ns/ical/

.pre-commit-config.yaml

@@ -1,16 +1,23 @@
 ---
 repos:
-  - repo: https://github.com/asottile/reorder_python_imports
-    rev: v3.12.0
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.9.4
     hooks:
-      - id: reorder-python-imports
-  - repo: https://github.com/psf/black
-    rev: 23.12.0
-    hooks:
-      - id: black
+      - id: ruff
+        args: [--fix]
+      - id: ruff-format
+
   - repo: https://github.com/pre-commit/pre-commit-hooks
-    rev: v4.5.0
+    rev: v5.0.0
     hooks:
       - id: check-byte-order-marker
       - id: trailing-whitespace
       - id: end-of-file-fixer
+
+  - repo: https://github.com/lycheeverse/lychee
+    rev: lychee-v0.22.0
+    hooks:
+      - id: lychee
+        args: ["--no-progress", "--timeout", "10"]
+        types: [markdown, rst]
+        stages: [manual]  # Run with: pre-commit run lychee --hook-stage manual

AI_POLICY.md → AI-POLICY.md

@@ -12,15 +12,15 @@ started receiving pull requests with code changes generated by AI (and
 I've seen people posting screenshots of simple questions and answers
 from ChatGPT in forum discussions, without contributing anything else).
 
-As of 2025-12, I've spent some time testing Claude.  I'm actually
+Starting in 2025-11, I've spent quite some time testing Claude.  I'm
 positively surprised, it's doing a much better job than what I had
-expected.  The AI may do things faster, smarter and better than a good
-coder.  Sometimes.  Other times it may spend a lot of "tokens" and a
-long time coming up with sub-optimal solutions, or even solutions that
-doesn't work at all.  Perhaps at some time in the near future the AI
-will do the developer profession obsoleted - but as of 2025-11, my
-experiences is that the AI performs best when being "supervised" and
-"guided" by a good coder knowing the project.
+expected.  The AI may do things a lot faster, smarter and better than
+a good coder.  Sometimes.  Other times it may spend a lot of "tokens"
+and a long time coming up with sub-optimal solutions, or even
+solutions that doesn't work at all.  Perhaps at some time in the near
+future the AI will do the developer profession completely obsoleted -
+but as of 2026-02, my experiences is that the AI performs best when
+being "supervised" and "guided" by a good coder knowing the project.
 
 ## The rules
 
@@ -48,28 +48,30 @@ experiences is that the AI performs best when being "supervised" and
   proposing.
 
 * **Transparency** is important.  Ok, so a lot of tools may have been
-  used while writing the pull request, I don't need to know all the
-  details, but if a significant part of the changes was generated by
-  some tool or by some AI, then that should be informed about.
-  I.e. if your job was to run `ruff` on the code and found some
-  imporant things that should be changed, then don't write "I found
-  this issue and here is a fix", but rather "I ran the ruff tool on
-  the code, found this issue, and here is the fix".  If some AI was
-  used for generating significant parts of the code changs, then it
-  should be informed about both in the pull request itself and in the
-  git commit message.  The most common way to do this is to add
-  "Assisted-by: (name of AI-tool)" at the end of the message.  Claude
-  seems to sign off with `Co-Authored-By: Claude
-  <noreply@anthropic.com>` when it's doing commits, that's also OK.
+  used while writing the pull request. I don't need to know what
+  editor you're using, the version of git or the color of the T-shirt
+  you're wearing.  However, if significant part of the changes (and/or
+  value of the pull request) was generated by some tool or by some AI,
+  then that should be informed about.  Say, you ran `ruff` on the code
+  and found some imporant things that should be changed, even if those
+  things are manually changed significant parts of the value of the
+  pull request comes from ruff.  Do not write "I found this issue and
+  here is a fix", but rather "I ran the ruff tool on the code, found
+  this issue, and here is the fix".  If some AI was used for
+  generating significant parts of the code changs, then it should be
+  informed about both in the pull request itself and in the git commit
+  message.  The most common way to do this is to add "Assisted-by:
+  (name of AI-tool)" at the end of the message.  Claude seems to sign
+  off with `Co-Authored-By: Claude <noreply@anthropic.com>` when it's
+  doing commits, that's also OK.
 
 * **YOU** should be ready to follow up and respond to feedback and
-  questions on the contribution.  If all you do is to relay it to the
-  AI and relaying the AI output back to the pull request, then
-  you're not adding value to the project and you're not transparent
-  and honest.  You should at least do a quick QA on the AI-answer and
-  acknowledge that it was generated by the AI.
+  questions on the contribution.  If you're letting the AI do this for
+  you, then you're neither honest nor adding value to the project.
+  You should at least do a quick QA on the AI-answer and acknowledge
+  that it was generated by the AI.
 
 * The Contributors Guidelines aren't strongly enforced on this project
-  as of 2025-12, and I can hardly see cases where the AI would break
-  the Code of Conduct, but at the end of the day **YOU** should take
-  care to ensure the contribution follows those guidelines.
+  as of 2026-02, and I can hardly see cases where the AI would break
+  the Code of Conduct, but at the end of the day, it's **YOUR**
+  responsibility that the contribution follows those guidelines.