Added buildout stuff and made changes accordingly

--HG--
rename : profile/management/__init__.py => eggs/djangorecipe-0.20-py2.6.egg/EGG-INFO/dependency_links.txt
rename : profile/management/__init__.py => eggs/djangorecipe-0.20-py2.6.egg/EGG-INFO/not-zip-safe
rename : profile/management/__init__.py => eggs/infrae.subversion-1.4.5-py2.6.egg/EGG-INFO/dependency_links.txt
rename : profile/management/__init__.py => eggs/infrae.subversion-1.4.5-py2.6.egg/EGG-INFO/not-zip-safe
rename : profile/management/__init__.py => eggs/mercurial-1.7.3-py2.6-linux-x86_64.egg/EGG-INFO/dependency_links.txt
rename : profile/management/__init__.py => eggs/mercurial-1.7.3-py2.6-linux-x86_64.egg/EGG-INFO/not-zip-safe
rename : profile/management/__init__.py => eggs/py-1.4.0-py2.6.egg/EGG-INFO/dependency_links.txt
rename : profile/management/__init__.py => eggs/py-1.4.0-py2.6.egg/EGG-INFO/not-zip-safe
rename : profile/management/__init__.py => eggs/zc.buildout-1.5.2-py2.6.egg/EGG-INFO/dependency_links.txt
rename : profile/management/__init__.py => eggs/zc.buildout-1.5.2-py2.6.egg/EGG-INFO/not-zip-safe
rename : profile/management/__init__.py => eggs/zc.recipe.egg-1.3.2-py2.6.egg/EGG-INFO/dependency_links.txt
rename : profile/management/__init__.py => eggs/zc.recipe.egg-1.3.2-py2.6.egg/EGG-INFO/not-zip-safe
rename : profile/management/__init__.py => parts/django/Django.egg-info/dependency_links.txt
rename : taskapp/models.py => parts/django/django/conf/app_template/models.py
rename : taskapp/tests.py => parts/django/django/conf/app_template/tests.py
rename : taskapp/views.py => parts/django/django/conf/app_template/views.py
rename : taskapp/views.py => parts/django/django/contrib/gis/tests/geo3d/views.py
rename : profile/management/__init__.py => parts/django/tests/modeltests/delete/__init__.py
rename : profile/management/__init__.py => parts/django/tests/modeltests/files/__init__.py
rename : profile/management/__init__.py => parts/django/tests/modeltests/invalid_models/__init__.py
rename : profile/management/__init__.py => parts/django/tests/modeltests/m2m_signals/__init__.py
rename : profile/management/__init__.py => parts/django/tests/modeltests/model_package/__init__.py
rename : profile/management/__init__.py => parts/django/tests/regressiontests/bash_completion/__init__.py
rename : profile/management/__init__.py => parts/django/tests/regressiontests/bash_completion/management/__init__.py
rename : profile/management/__init__.py => parts/django/tests/regressiontests/bash_completion/management/commands/__init__.py
rename : profile/management/__init__.py => parts/django/tests/regressiontests/bash_completion/models.py
rename : profile/management/__init__.py => parts/django/tests/regressiontests/delete_regress/__init__.py
rename : profile/management/__init__.py => parts/django/tests/regressiontests/file_storage/__init__.py
rename : profile/management/__init__.py => parts/django/tests/regressiontests/max_lengths/__init__.py
rename : profile/forms.py => pytask/profile/forms.py
rename : profile/management/__init__.py => pytask/profile/management/__init__.py
rename : profile/management/commands/seed_db.py => pytask/profile/management/commands/seed_db.py
rename : profile/models.py => pytask/profile/models.py
rename : profile/templatetags/user_tags.py => pytask/profile/templatetags/user_tags.py
rename : taskapp/tests.py => pytask/profile/tests.py
rename : profile/urls.py => pytask/profile/urls.py
rename : profile/utils.py => pytask/profile/utils.py
rename : profile/views.py => pytask/profile/views.py
rename : static/css/base.css => pytask/static/css/base.css
rename : taskapp/tests.py => pytask/taskapp/tests.py
rename : taskapp/views.py => pytask/taskapp/views.py
rename : templates/base.html => pytask/templates/base.html
rename : templates/profile/browse_notifications.html => pytask/templates/profile/browse_notifications.html
rename : templates/profile/edit.html => pytask/templates/profile/edit.html
rename : templates/profile/view.html => pytask/templates/profile/view.html
rename : templates/profile/view_notification.html => pytask/templates/profile/view_notification.html
rename : templates/registration/activate.html => pytask/templates/registration/activate.html
rename : templates/registration/activation_email.txt => pytask/templates/registration/activation_email.txt
rename : templates/registration/activation_email_subject.txt => pytask/templates/registration/activation_email_subject.txt
rename : templates/registration/logged_out.html => pytask/templates/registration/logged_out.html
rename : templates/registration/login.html => pytask/templates/registration/login.html
rename : templates/registration/logout.html => pytask/templates/registration/logout.html
rename : templates/registration/password_change_done.html => pytask/templates/registration/password_change_done.html
rename : templates/registration/password_change_form.html => pytask/templates/registration/password_change_form.html
rename : templates/registration/password_reset_complete.html => pytask/templates/registration/password_reset_complete.html
rename : templates/registration/password_reset_confirm.html => pytask/templates/registration/password_reset_confirm.html
rename : templates/registration/password_reset_done.html => pytask/templates/registration/password_reset_done.html
rename : templates/registration/password_reset_email.html => pytask/templates/registration/password_reset_email.html
rename : templates/registration/password_reset_form.html => pytask/templates/registration/password_reset_form.html
rename : templates/registration/registration_complete.html => pytask/templates/registration/registration_complete.html
rename : templates/registration/registration_form.html => pytask/templates/registration/registration_form.html
rename : utils.py => pytask/utils.py

1 files changed, 161 insertions, 0 deletions

diff --git a/parts/django/docs/ref/contrib/admin/admindocs.txt b/parts/django/docs/ref/contrib/admin/admindocs.txt
new file mode 100644
index 0000000..6743921
--- /dev/null
+++ b/parts/django/docs/ref/contrib/admin/admindocs.txt
@@ -0,0 +1,161 @@
+========================================

+The Django admin documentation generator

+========================================

+

+.. module:: django.contrib.admindocs

+    :synopsis: Django's admin documentation generator.

+

+.. currentmodule:: django.contrib.admindocs

+

+Django's :mod:`~django.contrib.admindocs` app pulls documentation from the

+docstrings of models, views, template tags, and template filters for any app in

+:setting:`INSTALLED_APPS` and makes that documentation available from the

+:mod:`Django admin <django.contrib.admin>`.

+

+In addition to providing offline documentation for all template tags and

+template filters that ship with Django, you may utilize admindocs to quickly

+document your own code.

+

+Overview

+========

+

+To activate the :mod:`~django.contrib.admindocs`, you will need to do

+the following:

+

+    * Add :mod:`django.contrib.admindocs` to your :setting:`INSTALLED_APPS`.

+    * Add ``(r'^admin/doc/', include('django.contrib.admindocs.urls'))`` to

+      your :data:`urlpatterns`. Make sure it's included *before* the

+      ``r'^admin/'`` entry, so that requests to ``/admin/doc/`` don't get

+      handled by the latter entry.

+    * Install the docutils Python module (http://docutils.sf.net/).

+    * **Optional:** Linking to templates requires the :setting:`ADMIN_FOR`

+      setting to be configured.

+    * **Optional:** Using the admindocs bookmarklets requires the

+      :mod:`XViewMiddleware<django.middleware.doc>` to be installed.

+

+Once those steps are complete, you can start browsing the documentation by

+going to your admin interface and clicking the "Documentation" link in the

+upper right of the page.

+

+Documentation helpers

+=====================

+

+The following special markup can be used in your docstrings to easily create

+hyperlinks to other components:

+

+=================   =======================

+Django Component    reStructuredText roles

+=================   =======================

+Models              ``:model:`appname.ModelName```

+Views               ``:view:`appname.view_name```

+Template tags       ``:tag:`tagname```

+Template filters    ``:filter:`filtername```

+Templates           ``:template:`path/to/template.html```

+=================   =======================

+

+Model reference

+===============

+

+The **models** section of the ``admindocs`` page describes each model in the

+system along with all the fields and methods available on it. Relationships to

+other models appear as hyperlinks. Descriptions are pulled from ``help_text``

+attributes on fields or from docstrings on model methods.

+

+A model with useful documentation might look like this::

+

+    class BlogEntry(models.Model):

+        """

+        Stores a single blog entry, related to :model:`blog.Blog` and

+        :model:`auth.User`.

+

+        """

+        slug = models.SlugField(help_text="A short label, generally used in URLs.")

+        author = models.ForeignKey(User)

+        blog = models.ForeignKey(Blog)

+        ...

+

+        def publish(self):

+            """Makes the blog entry live on the site."""

+            ...

+

+View reference

+==============

+

+Each URL in your site has a separate entry in the ``admindocs`` page, and

+clicking on a given URL will show you the corresponding view. Helpful things

+you can document in your view function docstrings include:

+

+    * A short description of what the view does.

+    * The **context**, or a list of variables available in the view's template.

+    * The name of the template or templates that are used for that view.

+

+For example::

+

+    from myapp.models import MyModel

+

+    def my_view(request, slug):

+        """

+        Display an individual :model:`myapp.MyModel`.

+

+        **Context**

+

+        ``RequestContext``

+

+        ``mymodel``

+            An instance of :model:`myapp.MyModel`.

+

+        **Template:**

+

+        :template:`myapp/my_template.html`

+

+        """

+        return render_to_response('myapp/my_template.html', {

+            'mymodel': MyModel.objects.get(slug=slug)

+        }, context_instance=RequestContext(request))

+

+

+Template tags and filters reference

+===================================

+

+The **tags** and **filters** ``admindocs`` sections describe all the tags and

+filters that come with Django (in fact, the :ref:`built-in tag reference

+<ref-templates-builtins-tags>` and :ref:`built-in filter reference

+<ref-templates-builtins-filters>` documentation come directly from those

+pages). Any tags or filters that you create or are added by a third-party app

+will show up in these sections as well.

+

+

+Template reference

+==================

+

+While ``admindocs`` does not include a place to document templates by

+themselves, if you use the ``:template:`path/to/template.html``` syntax in a

+docstring the resulting page will verify the path of that template with

+Django's :ref:`template loaders <template-loaders>`. This can be a handy way to

+check if the specified template exists and to show where on the filesystem that

+template is stored.

+

+

+Included Bookmarklets

+=====================

+

+Several useful bookmarklets are available from the ``admindocs`` page:

+

+    Documentation for this page

+        Jumps you from any page to the documentation for the view that generates

+        that page.

+

+    Show object ID

+        Shows the content-type and unique ID for pages that represent a single

+        object.

+

+    Edit this object

+        Jumps to the admin page for pages that represent a single object.

+

+Using these bookmarklets requires that you are either logged into the

+:mod:`Django admin <django.contrib.admin>` as a

+:class:`~django.contrib.auth.models.User` with

+:attr:`~django.contrib.auth.models.User.is_staff` set to `True`, or

+that the :mod:`django.middleware.doc` middleware and

+:mod:`XViewMiddleware <django.middleware.doc>` are installed and you

+are accessing the site from an IP address listed in :setting:`INTERNAL_IPS`.