o

ʎ�_|�@sdZGd
d�d�Z
dS)zBase email backend class.c@sBeZ
dZd
Zddd�
Zdd�Zdd�Zd	d
�Zdd�Zd
d�Z	dS)�BaseEmailBackenda3

    Base class for email backend implementations.

    Subclasses must at least overwrite send_messages().

    open() and close() can be called indirectly by using a backend object as a
    context manager:

       with backend as connection:
           # do something with connection
           pass
    FcKs
|
|_dS�
N)
�
fail_silently)�selfr�kwargs�r�@/usr/lib/python3/dist-packages/django/core/mail/backends/base.py�__init__s

zBaseEmailBackend.__init__c


C�d
S)a+
        Open a network connection.

        This method can be overwritten by backend implementations to
        open a network connection.

        It's up to the backend implementation to track the status of
        a network connection if it's needed by the backend.

        This method can be called by applications to force a single
        network connection to be used when sending mails. See the
        send_messages() method of the SMTP backend for a reference
        implementation.

        The default implementation does nothing.
        Nr�
rrrr�openszBaseEmailBackend.openc


Cr	)zClose a network connection.Nrr
rrr�close'szBaseEmailBackend.closec

Cs(z|��
W|St
y


|��
�wr)r�	Exceptionrr
rrr�	__enter__+s


�

�zBaseEmailBackend.__enter__cCs|��
dSr)
r)r�exc_type�	exc_value�	tracebackrrr�__exit__3s
zBaseEmailBackend.__exit__cCstd
�
�
)zm
        Send one or more EmailMessage objects and return the number of email
        messages sent.
        zCsubclasses of BaseEmailBackend must override send_messages() method)
�NotImplementedError)r�email_messagesrrr�
send_messages6szBaseEmailBackend.send_messagesN)
F)
�__name__�
__module__�__qualname__�__doc__rrrrrrrrrrr
s

r
N)rr
rrrr�<module>
s