-
Notifications
You must be signed in to change notification settings - Fork 5
Description
Hello,
The Celery project has a remote debbuger called rdb. It was working fine with pdbpp up to 0.10.3. 0.11.5 (the next available release on pypi), breaks with the following exception:
Traceback (most recent call last):
File "/path/to/src/replicate_rdb_init_error/main.py", line 8, in
main()
~~~~^^
File "/path/to/src/replicate_rdb_init_error/main.py", line 4, in main
rdb.set_trace()
~~~~~~~~~~~~~^^
File "/path/to/lib/python3.13/site-packages/celery/contrib/rdb.py", line 187, in set_trace
return debugger().set_trace(frame)
~~~~~~~~^^
File "/path/to/lib/python3.13/site-packages/celery/contrib/rdb.py", line 179, in debugger
rdb = _current[0] = Rdb()
~~~^^
File "/path/to/lib/python3.13/site-packages/pdbpp.py", line 279, in call
obj.init(*args, **kwargs)
~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
TypeError: Rdb.init() got an unexpected keyword argument 'start_filename'
A minimal reproducible example is available here: https://github.com/Hugo-C/replicate-rdb-init-error
It boils down to:
from celery.contrib import rdb
def main():
rdb.set_trace()
print('hello')Is it something you consider like a bug on your side ? Or would you rather see it fixed in Celery ?