Merge pull request #641 from jdufresne/ws

Trim trailing white space throughout the project
django-mptt · Apr 15, 2018 · 0a292c8 · 0a292c8
2 parents d8b954e + cec6cab
commit 0a292c8
Show file tree

Hide file tree

Showing 17 changed files with 122 additions and 127 deletions.
diff --git a/NOTES b/NOTES
@@ -14,9 +14,9 @@ Reparenting
 
 Since it's not unreasonable to assume a good percentage of the people
 who use this application will also be using the ``django.contrib.admin``
-application or ``forms.ModelForm`` to edit their data, and since in these 
-cases only the parent field will be editable if users have allowed 
-``mptt.register`` to create tree fields for them, it would be nice if 
+application or ``forms.ModelForm`` to edit their data, and since in these
+cases only the parent field will be editable if users have allowed
+``mptt.register`` to create tree fields for them, it would be nice if
 Django MPTT automatically took care of the tree when a ``Model`` instance
 has its parent changed.
 

diff --git a/docs/admin.rst b/docs/admin.rst
@@ -191,4 +191,3 @@ to ``10``)::
     class MyTreeRelatedFieldListFilter(TreeRelatedFieldListFilter):
     mptt_level_indent = 20
     # ...
-
diff --git a/docs/autogenerated.rst b/docs/autogenerated.rst
@@ -1,4 +1,3 @@
-
 Autogenerated documentation
 ===========================
 

diff --git a/docs/install.rst b/docs/install.rst
@@ -31,7 +31,7 @@ Alternatively, you can get the latest source from our `git`_ repository::
    git clone git://github.com/django-mptt/django-mptt.git django-mptt
 
 Add the resulting folder to your `PYTHONPATH`_ or symlink the ``mptt`` directory
-inside it into a directory which is on your PYTHONPATH, such as your Python 
+inside it into a directory which is on your PYTHONPATH, such as your Python
 installation's ``site-packages`` directory.
 
 You can verify that the application is available on your PYTHONPATH by
@@ -49,7 +49,7 @@ from within the ``django-mptt`` directory.
    The development version may contain bugs which are not present in the
    release version and introduce backwards-incompatible changes.
 
-   If you're tracking master, keep an eye on the recent `Commit History`_ 
+   If you're tracking master, keep an eye on the recent `Commit History`_
    before you update your copy of the source code.
 
 .. _`git`: https://git-scm.com/

diff --git a/docs/models.rst b/docs/models.rst
@@ -404,33 +404,33 @@ Example usage in the admin
 
     class CategoryAdmin(DraggableMPTTAdmin):
         mptt_indent_field = "name"
-        list_display = ('tree_actions', 'indented_title', 
+        list_display = ('tree_actions', 'indented_title',
                         'related_products_count', 'related_products_cumulative_count')
         list_display_links = ('indented_title',)
-    
+
         def get_queryset(self, request):
             qs = super().get_queryset(request)
-    
+
             # Add cumulative product count
             qs = Category.objects.add_related_count(
                     qs,
                     Product,
                     'category',
                     'products_cumulative_count',
                     cumulative=True)
-    
+
             # Add non cumulative product count
             qs = Category.objects.add_related_count(qs,
                      Product,
                      'categories',
                      'products_count',
                      cumulative=False)
             return qs
-    
+
         def related_products_count(self, instance):
             return instance.products_count
         related_product_count.short_description = 'Related products (for this specific category)'
-    
+
         def related_products_cumulative_count(self, instance):
             return instance.products_cumulative_count
         related_products_cumulative_count.short_description = 'Related products (in tree)'

diff --git a/docs/mptt.fields.rst b/docs/mptt.fields.rst
@@ -1,7 +1,7 @@
 ===============
 ``mptt.fields``
 ===============
-    
+
 .. automodule:: mptt.fields
     :members:
     :undoc-members:
diff --git a/docs/mptt.forms.rst b/docs/mptt.forms.rst
@@ -1,7 +1,7 @@
 ==============
 ``mptt.forms``
 ==============
-    
+
 .. automodule:: mptt.forms
     :members:
     :undoc-members:
diff --git a/docs/overview.rst b/docs/overview.rst
@@ -22,7 +22,7 @@ details about how the technique itself works:
     * `Trees in SQL`_
     * `Storing Hierarchical Data in a Database`_
     * `Managing Hierarchical Data in MySQL`_
-    
+
 .. _`Trees in SQL`: https://www.ibase.ru/files/articles/programming/dbmstrees/sqltrees.html
 .. _`Storing Hierarchical Data in a Database`: https://www.sitepoint.com/hierarchical-data-database/
 .. _`Managing Hierarchical Data in MySQL`: http://mikehillyer.com/articles/managing-hierarchical-data-in-mysql/
@@ -31,7 +31,7 @@ details about how the technique itself works:
 What is ``django-mptt``?
 ========================
 
-``django-mptt`` is a reusable Django app which aims to make it easy for you 
+``django-mptt`` is a reusable Django app which aims to make it easy for you
 to use MPTT with your own Django models.
 
 It takes care of the details of managing a database table as a tree
@@ -58,7 +58,7 @@ Feature overview
 
 * A ``TreeManager`` manager is added to all registered models. This provides
   methods to:
-  
+
   * move nodes around a tree, or into a different tree
   * insert a node anywhere in a tree
   * rebuild the MPTT fields for the tree (useful when you do bulk updates

diff --git a/docs/technical_details.rst b/docs/technical_details.rst
@@ -98,7 +98,7 @@ Note: In the above paragraph 'client code' means any django app that uses mptt b
 
 .. _`LOCK/UNLOCK statements are not transaction safe`: https://dev.mysql.com/doc/refman/5.7/en/lock-tables-and-transactions.html
 
- 
+
 
 
 Running the test suite

diff --git a/docs/templates.rst b/docs/templates.rst
@@ -51,11 +51,11 @@ These are magically inserted into your context while you're inside the
 
   ``node`` is an instance of your MPTT model.
 
-  ``children`` : This variable holds the rendered HTML for the children of 
+  ``children`` : This variable holds the rendered HTML for the children of
   ``node``.
 
 .. note::
-    If you already have variables called ``node`` or ``children`` in your 
+    If you already have variables called ``node`` or ``children`` in your
     template, and you need to access them inside the ``recursetree`` block,
     you'll need to alias them to some other name first::
 
@@ -202,7 +202,7 @@ Example::
 Examples
 ========
 
-Using ``drilldown_tree_for_node`` and ``tree_info`` together to render a 
+Using ``drilldown_tree_for_node`` and ``tree_info`` together to render a
 drilldown menu for a node, with cumulative counts of related items for the node's
 children::
 
@@ -218,7 +218,7 @@ children::
         {% for level in structure.closed_levels %}</li></ul>{% endfor %}
     {% endfor %}
 
-Using ``tree_info`` (with its optional argument) and ``tree_path`` together 
+Using ``tree_info`` (with its optional argument) and ``tree_path`` together
 to create a multiple-select, which:
 
 * doesn't contain root nodes

diff --git a/docs/tutorial.rst b/docs/tutorial.rst
@@ -1,4 +1,3 @@
-
 ========
 Tutorial
 ========

diff --git a/mptt/models.py b/mptt/models.py
@@ -326,9 +326,9 @@ def register(meta, cls, **kwargs):
 
                 bases.insert(0, MPTTModel)
                 cls.__bases__ = tuple(bases)
-                
+
             is_cls_tree_model = _get_tree_model(cls) is cls
-            
+
             if is_cls_tree_model:
                 # HACK: _meta.get_field() doesn't work before AppCache.ready in Django>=1.8
                 # ( see https://code.djangoproject.com/ticket/24231 )

diff --git a/tests/myapp/doctests.txt b/tests/myapp/doctests.txt
@@ -1477,4 +1477,3 @@ ValueError: Cannot insert a node which has already been saved.
 <Person: Jess>
 >>> list(jane.get_ancestors())
 [<Person: Jess>, <Person: Jeff>]
-