It’s not just about completeness but whether it’s largely bug free. Are there likely to be lots of edge-cases that haven’t been exposed yet, requiring numerous/rapid fixes? (IDK but we’re talking about browsers here right?)
Maybe the inclusion of this is a good reason for us to revive the experimental DEP?
The experimental APIs DEP allowed only changes without deprecation at the next .0 release. (So something introduced in 6.0 could be changed in 7.0.) It’s not experimental in the sense that might be needed here. (Two years to make an API change because we realised it was wrong isn’t going to fly.)
To quote that DEP:
… to have got as far as an experimental feature in the main codebase it should have passed a certain quality threshold and the DEP process and already be somewhat fully-formed.
It’s not a licence to include WIP experiments as part of Django itself.[1]
I don’t see this doing well as a separate package and would need to be adopted to help shift community opinion.
Bar adoption, the only rational given for needing this in core is potential template blocks needed to be added. Well, blocks can be added.
In reference to adoption, this looks like the perfect test case for solving the How do we promote a package without it having to be merged to core? that we bang our head on again and again and again. I’d suggest we take the opportunity to address it, rather than sidestep it. (We need to do so at some point.)
Of course, that whole discussion is conditional on the assumption that the package is essentially not battle tested. The repo has this warning…
…very hacky and really just a proof of concept…
Which implies that it would be a concern.
On the positive side, if it’s a young idea, it wants to be free of the eight-month release cycle and stability policy so that it can evolve. This is something to embrace.
The experimental APIs DEP would be perfect for django-tasks though. We’re pretty sure the API for deferring tasks is correct, but who’s to say we won’t want to bring in a change once real-world usage scales up? ↩︎