Answers for "attributeerror:"

attributeerror:

AttributeError: can be defined as an error that is raised when an attribute 
 reference or assignment fails.

attributeerror:

# user in the login should be a User Object not the username.

from django.contrib.auth.models import User

def get_django_user_by_username(username):
    """Get the django user
    Args:
        username (str): email id of the user
    Returns:
        object: django user object
    """
    return User.objects.filter(username=username).first()

user = get_django_user_by_username(email)

login(request, user, backend="django.contrib.auth.backends.ModelBackend")

attributeerror:

This happens because the scipy module doesn't have any attribute named sparse. That attribute only gets defined when you import scipy.sparse.

Submodules don't automatically get imported when you just import scipy; you need to import them explicitly. The same holds for most packages, although a package can choose to import its own submodules if it wants to. (For example, if scipy/__init__.py included a statement import scipy.sparse, then the sparse submodule would be imported whenever you import scipy.)

attributeerror:

string = "WEBSITE { }".fst("SAM")
print(string)

attributeerror:

EXAMPLE
# Python program to demonstrate
# AttributeError

# Raises an AttributeError as there is no
# method as fst for strings
string = "WEBSITE { }".fst("SAM")
print(string)

attributeerror:

AttributeError can be defined as an error that is raised when an attribute reference or assignment fails. For example, if we take a variable x we assined a value 10. In this process suppose we want to append another value to that variable. ... Because the variable is a integer type it's not support append method

attributeerror:

Just keep reading tutorial. It will be explained in Keep Results chapter. 
http://celery.readthedocs.org/en/latest/getting-started/first-steps-with-celery.html#keeping-results

To start Celery you need to provide just broker parameter, which is required to send messages 
about tasks. If you want to retrieve information about state and results 
returned by finished tasks you need to set backend parameter. 

You can find full list with description in Configuration docs: CELERY_RESULT_BACKEND.
http://celery.readthedocs.io/en/latest/userguide/configuration.html#std:setting-result_backend