Upgrade to Django 3.2 (#2056)

2021-05-07 12:00:30 +02:00
parent 0a7a3537eb
commit 403b8191e4
120 changed files with 1994 additions and 1555 deletions
--- a/src/pretix/control/signals.py
+++ b/src/pretix/control/signals.py
@@ -36,9 +36,7 @@ from django.dispatch import Signal

 from pretix.base.signals import DeprecatedSignal, EventPluginSignal

-html_page_start = Signal(
-    providing_args=[]
-)
+html_page_start = Signal()
 """
 This signal allows you to put code in the beginning of the main page for every
 page in the backend. You are expected to return HTML.
@@ -46,10 +44,10 @@ page in the backend. You are expected to return HTML.
 The ``sender`` keyword argument will contain the request.
 """

-html_head = EventPluginSignal(
-    providing_args=["request"]
-)
+html_head = EventPluginSignal()
 """
+Arguments: ``request``
+
 This signal allows you to put code inside the HTML ``<head>`` tag
 of every page in the backend. You will get the request as the keyword argument
 ``request`` and are expected to return plain HTML.
@@ -57,10 +55,10 @@ of every page in the backend. You will get the request as the keyword argument
 As with all plugin signals, the ``sender`` keyword argument will contain the event.
 """

-nav_event = EventPluginSignal(
-    providing_args=["request"]
-)
+nav_event = EventPluginSignal()
 """
+Arguments: ``request``
+
 This signal allows you to add additional views to the admin panel
 navigation. You will get the request as a keyword argument ``request``.
 Receivers are expected to return a list of dictionaries. The dictionaries
@@ -82,10 +80,10 @@ in pretix.
 As with all plugin signals, the ``sender`` keyword argument will contain the event.
 """

-nav_topbar = Signal(
-    providing_args=["request"]
-)
+nav_topbar = Signal()
 """
+Arguments: ``request``
+
 This signal allows you to add additional views to the top navigation bar.
 You will get the request as a keyword argument ``request``.
 Receivers are expected to return a list of dictionaries. The dictionaries
@@ -101,10 +99,10 @@ This is no ``EventPluginSignal``, so you do not get the event in the ``sender``
 and you may get the signal regardless of whether your plugin is active.
 """

-nav_global = Signal(
-    providing_args=["request"]
-)
+nav_global = Signal()
 """
+Arguments: ``request``
+
 This signal allows you to add additional views to the navigation bar when no event is
 selected. You will get the request as a keyword argument ``request``.
 Receivers are expected to return a list of dictionaries. The dictionaries
@@ -126,10 +124,10 @@ This is no ``EventPluginSignal``, so you do not get the event in the ``sender``
 and you may get the signal regardless of whether your plugin is active.
 """

-event_dashboard_top = EventPluginSignal(
-    providing_args=['request']
-)
+event_dashboard_top = EventPluginSignal()
 """
+Arguments: 'request'
+
 This signal is sent out to include custom HTML in the top part of the the event dashboard.
 Receivers should return HTML.

@@ -137,9 +135,7 @@ As with all plugin signals, the ``sender`` keyword argument will contain the eve
 An additional keyword argument ``subevent`` *can* contain a sub-event.
 """

-event_dashboard_widgets = EventPluginSignal(
-    providing_args=[]
-)
+event_dashboard_widgets = EventPluginSignal()
 """
 This signal is sent out to include widgets in the event dashboard. Receivers
 should return a list of dictionaries, where each dictionary can have the keys:
@@ -154,10 +150,10 @@ As with all plugin signals, the ``sender`` keyword argument will contain the eve
 An additional keyword argument ``subevent`` *can* contain a sub-event.
 """

-user_dashboard_widgets = Signal(
-    providing_args=['user']
-)
+user_dashboard_widgets = Signal()
 """
+Arguments: 'user'
+
 This signal is sent out to include widgets in the personal user dashboard. Receivers
 should return a list of dictionaries, where each dictionary can have the keys:

@@ -170,20 +166,20 @@ should return a list of dictionaries, where each dictionary can have the keys:
 This is a regular django signal (no pretix event signal).
 """

-voucher_form_html = EventPluginSignal(
-    providing_args=['form']
-)
+voucher_form_html = EventPluginSignal()
 """
+Arguments: 'form'
+
 This signal allows you to add additional HTML to the form that is used for modifying vouchers.
 You receive the form object in the ``form`` keyword argument.

 As with all plugin signals, the ``sender`` keyword argument will contain the event.
 """

-voucher_form_class = EventPluginSignal(
-    providing_args=['cls']
-)
+voucher_form_class = EventPluginSignal()
 """
+Arguments: ``cls``
+
 This signal allows you to replace the form class that is used for modifying vouchers.
 You will receive the default form class (or the class set by a previous plugin) in the
 ``cls`` argument so that you can inherit from it.
@@ -196,10 +192,10 @@ for every batch persisted to the database.
 As with all plugin signals, the ``sender`` keyword argument will contain the event.
 """

-voucher_form_validation = EventPluginSignal(
-    providing_args=['form']
-)
+voucher_form_validation = EventPluginSignal()
 """
+Arguments: 'form'
+
 This signal allows you to add additional validation to the form that is used for
 creating and modifying vouchers. You will receive the form instance in the ``form``
 argument and the current data state in the ``data`` argument.
@@ -207,28 +203,28 @@ argument and the current data state in the ``data`` argument.
 As with all plugin signals, the ``sender`` keyword argument will contain the event.
 """

-quota_detail_html = EventPluginSignal(
-    providing_args=['quota']
-)
+quota_detail_html = EventPluginSignal()
 """
+Arguments: 'quota'
+
 This signal allows you to append HTML to a Quota's detail view. You receive the
 quota as argument in the ``quota`` keyword argument.

 As with all plugin signals, the ``sender`` keyword argument will contain the event.
 """

-organizer_edit_tabs = DeprecatedSignal(
-    providing_args=['organizer', 'request']
-)
+organizer_edit_tabs = DeprecatedSignal()
 """
+Arguments: 'organizer', 'request'
+
 Deprecated signal, no longer works. We just keep the definition so old plugins don't
 break the installation.
 """

-nav_organizer = Signal(
-    providing_args=['organizer', 'request']
-)
+nav_organizer = Signal()
 """
+Arguments: 'organizer', 'request'
+
 This signal is sent out to include tab links on the detail page of an organizer.
 Receivers are expected to return a list of dictionaries. The dictionaries
 should contain at least the keys ``label`` and ``url``. You should also return
@@ -249,30 +245,30 @@ This is a regular django signal (no pretix event signal). Receivers will be pass
 the keyword arguments ``organizer`` and ``request``.
 """

-order_info = EventPluginSignal(
-    providing_args=["order", "request"]
-)
+order_info = EventPluginSignal()
 """
+Arguments: ``order``, ``request``
+
 This signal is sent out to display additional information on the order detail page

 As with all plugin signals, the ``sender`` keyword argument will contain the event.
 Additionally, the argument ``order`` and ``request`` are available.
 """

-order_position_buttons = EventPluginSignal(
-    providing_args=["order", "position", "request"]
-)
+order_position_buttons = EventPluginSignal()
 """
+Arguments: ``order``, ``position``, ``request``
+
 This signal is sent out to display additional buttons for a single position of an order.

 As with all plugin signals, the ``sender`` keyword argument will contain the event.
 Additionally, the argument ``order`` and ``request`` are available.
 """

-nav_event_settings = EventPluginSignal(
-    providing_args=['request']
-)
+nav_event_settings = EventPluginSignal()
 """
+Arguments: 'request'
+
 This signal is sent out to include tab links on the settings page of an event.
 Receivers are expected to return a list of dictionaries. The dictionaries
 should contain at least the keys ``label`` and ``url``. You should also return
@@ -287,10 +283,10 @@ As with all plugin signals, the ``sender`` keyword argument will contain the eve
 A second keyword argument ``request`` will contain the request object.
 """

-event_settings_widget = EventPluginSignal(
-    providing_args=['request']
-)
+event_settings_widget = EventPluginSignal()
 """
+Arguments: 'request'
+
 This signal is sent out to include template snippets on the settings page of an event
 that allows generating a pretix Widget code.

@@ -298,10 +294,10 @@ As with all plugin signals, the ``sender`` keyword argument will contain the eve
 A second keyword argument ``request`` will contain the request object.
 """

-item_forms = EventPluginSignal(
-    providing_args=['request', 'item']
-)
+item_forms = EventPluginSignal()
 """
+Arguments: 'request', 'item'
+
 This signal allows you to return additional forms that should be rendered on the product
 modification page. You are passed ``request`` and ``item`` arguments and are expected to return
 an instance of a form class that you bind yourself when appropriate. Your form will be executed
@@ -311,10 +307,10 @@ styles. It is advisable to set a prefix for your form to avoid clashes with othe
 As with all plugin signals, the ``sender`` keyword argument will contain the event.
 """

-item_formsets = EventPluginSignal(
-    providing_args=['request', 'item']
-)
+item_formsets = EventPluginSignal()
 """
+Arguments: 'request', 'item'
+
 This signal allows you to return additional formsets that should be rendered on the product
 modification page. You are passed ``request`` and ``item`` arguments and are expected to return
 an instance of a formset class that you bind yourself when appropriate. Your formset will be
@@ -329,10 +325,10 @@ will be passed a ``formset`` variable with your formset.
 As with all plugin signals, the ``sender`` keyword argument will contain the event.
 """

-subevent_forms = EventPluginSignal(
-    providing_args=['request', 'subevent', 'copy_from']
-)
+subevent_forms = EventPluginSignal()
 """
+Arguments: 'request', 'subevent', 'copy_from'
+
 This signal allows you to return additional forms that should be rendered on the subevent creation
 or modification page. You are passed ``request`` and ``subevent`` arguments and are expected to return
 an instance of a form class that you bind yourself when appropriate. Your form will be executed
@@ -346,17 +342,17 @@ creation, ``copy_from`` can be a subevent that is being copied from.
 As with all plugin signals, the ``sender`` keyword argument will contain the event.
 """

-oauth_application_registered = Signal(
-    providing_args=["user", "application"]
-)
+oauth_application_registered = Signal()
 """
+Arguments: ``user``, ``application``
+
 This signal will be called whenever a user registers a new OAuth application.
 """

-order_search_filter_q = Signal(
-    providing_args=["query"]
-)
+order_search_filter_q = Signal()
 """
+Arguments: ``query``
+
 This signal will be called whenever a free-text order search is performed. You are expected to return one
 Q object that will be OR-ed with existing search queries. As order search exists on a global level as well,
 this is not an Event signal and will be called even if your plugin is not active. ``sender`` will contain the
@@ -364,10 +360,10 @@ event if the search is performed within an event, and ``None`` otherwise. The se
 ``query``.
 """

-order_search_forms = EventPluginSignal(
-    providing_args=['request']
-)
+order_search_forms = EventPluginSignal()
 """
+Arguments: 'request'
+
 This signal allows you to return additional forms that should be rendered in the advanced order search.
 You are passed ``request`` argument and are expected to return an instance of a form class that you bind
 yourself when appropriate. Your form will be executed as part of the standard validation and rendering