              return context
  
  .. method:: WizardView.get_wizard_name()
  
      This method can be used to change the wizard's internal name.
  
      Default implementation::
  
          def get_wizard_name(self):
              return normalize_name(self.__class__.__name__)
  
  .. method:: WizardView.get_prefix()
  
      This method returns a prefix for the storage backends. These backends use
      the prefix to fetch the correct data for the wizard. (Multiple wizards
      could save their data in one session)
  
      You can change this method to make the wizard data prefix more unique to,
      e.g. have multiple instances of one wizard in one session.
  
      Default implementation::
 
</s> remove .. method:: WizardView.get_wizard_name()
 </s> add .. method:: WizardView.get_prefix(*args, **kwargs) </s> remove         def get_prefix(self):
            return self.wizard_name
 </s> add         def get_prefix(self, *args, **kwargs):
            # use the lowercase underscore version of the class name
            return normalize_name(self.__class__.__name__) </s> remove         return self.wizard_name
 </s> add         return normalize_name(self.__class__.__name__) </s> remove     def get_wizard_name(self):
        return normalize_name(self.__class__.__name__)

    def get_prefix(self):
 </s> add     def get_prefix(self, *args, **kwargs): </s> remove         self.wizard_name = self.get_wizard_name()
        self.prefix = self.get_prefix()
 </s> add         self.prefix = self.get_prefix(*args, **kwargs)
    This method returns a prefix for use by the storage backends. Backends use
    the prefix as a mechanism to allow data to be stored separately for each
    wizard. This allows wizards to store their data in a single backend
    without overwriting each other.
              return context
  
  .. method:: WizardView.get_wizard_name()
  
    This method returns a prefix for use by the storage backends. Backends use
    the prefix as a mechanism to allow data to be stored separately for each
    wizard. This allows wizards to store their data in a single backend
    without overwriting each other.
    This method returns a prefix for use by the storage backends. Backends use
    the prefix as a mechanism to allow data to be stored separately for each
    wizard. This allows wizards to store their data in a single backend
    without overwriting each other.
    This method returns a prefix for use by the storage backends. Backends use
    the prefix as a mechanism to allow data to be stored separately for each
    wizard. This allows wizards to store their data in a single backend
    without overwriting each other.
    This method returns a prefix for use by the storage backends. Backends use
    the prefix as a mechanism to allow data to be stored separately for each
    wizard. This allows wizards to store their data in a single backend
    without overwriting each other.
    This method returns a prefix for use by the storage backends. Backends use
    the prefix as a mechanism to allow data to be stored separately for each
    wizard. This allows wizards to store their data in a single backend
    without overwriting each other.
    This method returns a prefix for use by the storage backends. Backends use
    the prefix as a mechanism to allow data to be stored separately for each
    wizard. This allows wizards to store their data in a single backend
    without overwriting each other.
    This method returns a prefix for use by the storage backends. Backends use
    the prefix as a mechanism to allow data to be stored separately for each
    wizard. This allows wizards to store their data in a single backend
    without overwriting each other.
    This method returns a prefix for use by the storage backends. Backends use
    the prefix as a mechanism to allow data to be stored separately for each
    wizard. This allows wizards to store their data in a single backend
    without overwriting each other.
    This method returns a prefix for use by the storage backends. Backends use
    the prefix as a mechanism to allow data to be stored separately for each
    wizard. This allows wizards to store their data in a single backend
    without overwriting each other.
    This method returns a prefix for use by the storage backends. Backends use
    the prefix as a mechanism to allow data to be stored separately for each
    wizard. This allows wizards to store their data in a single backend
    without overwriting each other.
    This method returns a prefix for use by the storage backends. Backends use
    the prefix as a mechanism to allow data to be stored separately for each
    wizard. This allows wizards to store their data in a single backend
    without overwriting each other.
    This method returns a prefix for use by the storage backends. Backends use
    the prefix as a mechanism to allow data to be stored separately for each
    wizard. This allows wizards to store their data in a single backend
    without overwriting each other.
  
      You can change this method to make the wizard data prefix more unique to,
      e.g. have multiple instances of one wizard in one session.
  
      Default implementation::
keep keep keep keep replace replace replace replace replace replace replace replace replace replace replace replace keep keep keep keep keep
 Fixed #17162 -- Removed the useless `WizardView.get_wizard_name()` method. Thanks, Bradley Ayers and Stephan Jaekel.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@17234 bcc190cf-cafb-0310-a4f2-bffc1f526a37 
docs/ref/contrib/formtools/form-wizard.txt