Add pluggy as a dependency

[LilyFirefly]

Code of Conduct

• I agree to follow Django's Code of Conduct

Feature Description

Enable the third-party ecosystem to plug into core Django features in a more flexible and powerful way by adding pluggy as a dependency.

Problem

While the third-party ecosystem is one of Django's strengths, it is not always possible to plug into Django functionality without jumping through hoops (usually adding to settings.py). Adding pluggy would add more flexible entry points for plugins.

Request or proposal

proposal

Additional Details

When reviewing django/deps#98 (comment), the Steering Council had the idea of using pluggy to enable third-party packages to easily plug into the proposed django new command. We quickly realised that it would also enable adding plugin entry points when building other Django features.

There is some prior art for using pluggy with Django, for example:

• https://2024.djangocon.us/talks/how-to-design-and-implement-extensible-software-with-plugins/
• https://simonwillison.net/2024/Sep/25/djp-a-plugin-system-for-django/

pluggy is also a mature and stable package, that has been used by pytest for years.

Implementation Suggestions

No response

[github-actions]

Thank you LilyFirefly for sharing your idea! We have a lot of them so please be patient. You can see the current queue here.

Community instructions

For commenters, please use the emoji reactions on the issue to express support, and/or concern easily. Please use the comments to ask questions or contribute knowledge about the idea. It is unhelpful to post comments of "I'd love this" or "What's the state of this?"

Reaction Guide

• 👍 This is something I would use
• 👎 This is something that would cause problems for me or Django
• 😕 I’m indifferent to this
• 🎉 This is an easy win

[ehmatthes]

Hi, I'm really enjoying the fresh thinking around Django UX. I've been working on django-simple-deploy for a while, and in numerous demos the "Add django_simple_deploy to INSTALLED_APPS" step always feels a little awkward. It would be so nice to just install a package and then run the command that the package implements.

Is this a proposal to simply add pluggy as a dependency to Django, so that authors of templates for new could provide hooks?

[LilyFirefly]

Is this a proposal to simply add pluggy as a dependency to Django, so that authors of templates for new could provide hooks?

Yes, pretty much. Whether to use pluggy for other parts of Django is something that will still need deciding on a case-by-case basis.