pydantic2's validate_call with celery tasks

[PHvL]

Since this is about the interaction of two libraries, I'm not sure, where this should be asked. I've already posted a version of this question in the pydantic discussions.

In pydantic v1 we used the validate_arguments decorator for many functions, including our celery tasks. To transition to pydantic v2, we replaced it with validate_call, which works fine, if not all arguments are given as keyword arguments.

import time
from pydantic import validate_call
from celery import Celery

celery_app = Celery()

@celery_app.task
@validate_call
def wait(seconds:int=60) -> str:
	time.sleep(seconds)
	return f'Waited {seconds} seconds.'

Now wait(2), wait('2'), wait(seconds=2), and wait.delay(2) work as expected, but

>>> wait.delay(seconds=2)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "...\site-packages\celery\app\task.py", line 444, in delay
    return self.apply_async(args, kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "...\site-packages\celery\app\task.py", line 559, in apply_async
    check_arguments(*(args or ()), **(kwargs or {}))
TypeError: ValidateCallWrapper() missing 1 required positional argument: 'self'

Am I doing something wrong? I've tried pydantic 2.2.1 and 2.3.0, 2.4.0, celery 5.3.1 and 5.3.4 on python 3.11.5.

EDIT: The problem can be avoided by defining the task as bound:

@celery_app.task(bind=True)
@validate_call
def wait(self, seconds:int=60) -> str:
	time.sleep(seconds)
	return f'Waited {seconds} seconds.'

Do we have to define all our tasks as bound? Are there any negative consequences of bound tasks?