:py:mod:`oioioi.contestlogo.models`
===================================

.. py:module:: oioioi.contestlogo.models


Module Contents
---------------

Classes
~~~~~~~

.. autoapisummary::

   oioioi.contestlogo.models.ContestLogo
   oioioi.contestlogo.models.ContestIcon



Functions
~~~~~~~~~

.. autoapisummary::

   oioioi.contestlogo.models.make_logo_filename
   oioioi.contestlogo.models.make_icon_filename



.. py:function:: make_logo_filename(instance, filename)


.. py:class:: ContestLogo(*args, **kwargs)

   Bases: :py:obj:`django.db.models.Model`

   Make subclasses preserve the alters_data attribute on overridden methods.

   .. py:class:: Meta

      Bases: :py:obj:`object`

      .. py:attribute:: verbose_name
         

         

      .. py:attribute:: verbose_name_plural
         

         


   .. py:property:: filename


   .. py:attribute:: contest
      

      

   .. py:attribute:: image
      

      

   .. py:attribute:: updated_at
      

      

   .. py:attribute:: link
      

      

   .. py:method:: save(*args, **kwargs)

      Save the current instance. Override this in a subclass if you want to
      control the saving process.

      The 'force_insert' and 'force_update' parameters can be used to insist
      that the "save" must be an SQL insert or update (or equivalent for
      non-SQL backends), respectively. Normally, they should not be set.



.. py:function:: make_icon_filename(instance, filename)


.. py:class:: ContestIcon(*args, **kwargs)

   Bases: :py:obj:`django.db.models.Model`

   Make subclasses preserve the alters_data attribute on overridden methods.

   .. py:class:: Meta

      Bases: :py:obj:`object`

      .. py:attribute:: verbose_name
         

         

      .. py:attribute:: verbose_name_plural
         

         


   .. py:property:: filename


   .. py:attribute:: contest
      

      

   .. py:attribute:: image
      

      

   .. py:attribute:: updated_at
      

      

   .. py:method:: save(*args, **kwargs)

      Save the current instance. Override this in a subclass if you want to
      control the saving process.

      The 'force_insert' and 'force_update' parameters can be used to insist
      that the "save" must be an SQL insert or update (or equivalent for
      non-SQL backends), respectively. Normally, they should not be set.