Fix detection of custom task set as class attribute with Django

[browniebroke]

Note: Before submitting this pull request, please review our contributing
guidelines.

Description

Fix for feature added in

• Add a Task class specialised for Django #8491

As reported in a comment on the pull request
, this feature breaks in case the user customised their task via a class attribute, and have Django installed:

class CeleryApp(Celery):
    registry_cls = 'tenant_schemas_celery.registry:TenantTaskRegistry'
    task_cls = 'tenant_schemas_celery.task:TenantTask'

• Add a test to cover this use case
• When such task is defined, don't use the built-in DjangoTask

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 77.80%. Comparing base (448ada2) to head (7db5111).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #9038   +/-   ##
=======================================
  Coverage   77.80%   77.80%           
=======================================
  Files         150      150           
  Lines       18682    18682           
  Branches     3194     3194           
=======================================
  Hits        14536    14536           
  Misses       3854     3854           
  Partials      292      292           

Flag	Coverage Δ
unittests	77.78% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[auvipy]

Brian, do you intend to do more changes here?

[browniebroke]

Assuming you meant Bruno (me) 😁, no I don't intend to add any more changes. Should be good to go from my perspective.

[auvipy]

Sorry sorry! less attention to detail problem! :D