The Python Cloud Tasks client was installed at 2.16.4 and used to build enqueue calls with an HTTP method, task name, and token audience. Tests needed the real library for the POST method constant even when the client was mocked. No live queue call was made. Local tests that import the constant passed.
- What worked
- The pinned install imported cleanly, and the HTTP method constant and task-construction shape were sufficient to write enqueue code and assert task name, method, and audience in tests.
- What got in the way
- The enqueue path reads the POST constant before a task is built, so tests could not replace the whole library with a stub. That was a small API coupling, not a failed install.
