file and line ending

Author: trbs

.tx/config

@@ -5,4 +5,3 @@ source_lang = en
 
 [main]
 host = https://www.transifex.com
-

LICENSE

@@ -16,4 +16,4 @@ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
 AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.
+THE SOFTWARE.

django_extensions/locale/fr/LC_MESSAGES/django.po

@@ -1,7 +1,7 @@
 # SOME DESCRIPTIVE TITLE.
 # Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
 # This file is distributed under the same license as the PACKAGE package.
-# 
+#
 # Translators:
 # mathiasuk, 2014
 # mathiasuk, 2014

django_extensions/templates/django_extensions/graph_models/relation.dot

@@ -7,4 +7,4 @@
   >]{% endif %}
   {{ model.app_name }}_{{ model.name }} -> {{ relation.target_app }}_{{ relation.target }}
   [label="{{ relation.label }}"] {{ relation.arrows }};
-{% endfor %}{% endfor %}
+{% endfor %}{% endfor %}

docs/AUTHORS

@@ -24,4 +24,4 @@ Marc Tudurí (marctc)
 Rick van Hattem (WoLpH)
 Rodolphe Quiédeville (rodo)
 Nik Nyby (nikolas)
-Joshua Miller (thecardcheat)
+Joshua Miller (thecardcheat)

docs/admin_extensions.rst

@@ -10,7 +10,7 @@ Current Admin Extensions
   to do configurable autocompletion.
 
 * *ForeignKeyAutocompleteStackedInline*, *ForeignKeyAutocompleteTabularInline* -
-  in the same fashion of the *ForeignKeyAutocompleteAdmin* these two classes 
+  in the same fashion of the *ForeignKeyAutocompleteAdmin* these two classes
   enable a search input field for ForeginKey fields in AdminInline classes.
 
 

docs/command_extensions.rst

@@ -8,7 +8,7 @@ Current Command Extensions
 
 * *admin_generator* - Generate automatic Django Admin classes by providing an app name. Outputs
   source code at STDOUT.
-  
+
 * *clean_pyc* - Remove all python bytecode compiled files from the project
 
 * `create_app`_ - Creates an application directory structure for the specified
@@ -44,7 +44,7 @@ Current Command Extensions
 * `export_emails`_ - export the email addresses for your
   users in one of many formats.  Currently supports Address, Google, Outlook,
   LinkedIn, and VCard formats.
-  
+
 * *find_template* - Finds the location of the given template by resolving its path
 
 * *generate_secret_key* - Creates a new secret key that you can put in your
@@ -56,7 +56,7 @@ Current Command Extensions
 
 * *mail_debug* - Starts a mail server which echos out the contents of the email
   instead of sending it.
-  
+
 * *notes* - Show all annotations like TODO, FIXME, BUG, HACK, WARNING, NOTE or XXX in your py and HTML files.
 
 * *passwd* - Makes it easy to reset a user's password.
@@ -115,7 +115,7 @@ Current Command Extensions
   Optionally can also gzip CSS and Javascript files and set the
   Content-Encoding header, and also set a far future expires header for browser
   caching.
-  
+
 * *syncdata* - Makes the current database have the same data as the fixture(s), no more, no less.
 
 * *unreferenced_files* - Prints a list of all files in MEDIA_ROOT that are not referenced in the database.

docs/command_signals.rst

@@ -3,7 +3,7 @@ Command Signals
 
 :synopsis: Signals fired before and after a command is executed.
 
-A signal is thrown pre/post each management command allowing your application 
+A signal is thrown pre/post each management command allowing your application
 to hook into each commands execution.
 
 
@@ -16,48 +16,48 @@ An example hooking into show_template_tags:
 
   from django_extensions.management.signals import pre_command, post_command
   from django_extensions.management.commands.show_template_tags import Command
-  
+
   def pre_receiver(sender, args, kwargs):
     # I'm executed prior to the management command
-  
+
   def post_receiver(sender, args, kwargs, outcome):
     # I'm executed after the management command
-  
+
   pre_command.connect(pre_receiver, Command)
   post_command.connect(post_receiver, Command)
 
 
 Custom Permissions For All Models
 ---------------------------------
- 
-You can use the post signal to hook into the ``update_permissions`` command so that 
+
+You can use the post signal to hook into the ``update_permissions`` command so that
 you can add your own permissions to each model.
- 
-For instance, lets say you want to add ``list`` and ``view`` permissions to 
+
+For instance, lets say you want to add ``list`` and ``view`` permissions to
 each model. You could do this by adding them to the ``permissions`` tuple inside
 your models ``Meta`` class but this gets pretty tedious.
- 
+
 An easier solution is to hook into the ``update_permissions`` call, as follows;
- 
+
 ::
 
   from django.db.models.signals import post_syncdb
   from django.contrib.contenttypes.models import ContentType
   from django.contrib.auth.models import Permission
   from django_extensions.management.signals import post_command
   from django_extensions.management.commands.update_permissions import Command as UpdatePermissionsCommand
-  
+
   def add_permissions(sender, **kwargs):
     """
     Add view and list permissions to all content types.
     """
     # for each of our content types
     for content_type in ContentType.objects.all():
-      
+
       for action in ['view', 'list']:
         # build our permission slug
         codename = "%s_%s" % (action, content_type.model)
-        
+
         try:
           Permission.objects.get(content_type=content_type, codename=codename)
           # Already exists, ignore
@@ -68,23 +68,23 @@ An easier solution is to hook into the ``update_permissions`` call, as follows;
                         name="Can %s %s" % (action, content_type.name))
           print "Added %s permission for %s" % (action, content_type.name)
   post_command.connect(add_permissions, UpdatePermissionsCommand)
- 
-Each time ``update_permissions`` is called ``add_permissions`` will be called which 
+
+Each time ``update_permissions`` is called ``add_permissions`` will be called which
 ensures there are view and list permissions to all content types.
 
 
 Using pre/post signals on your own commands
 -------------------------------------------
- 
-The signals are implemented using a decorator on the handle method of a management command, 
+
+The signals are implemented using a decorator on the handle method of a management command,
 thus using this functionality in your own application is trivial:
 
 ::
 
   from django_extensions.management.utils import signalcommand
-   
+
   class Command(BaseCommand):
-   
+
     @signalcommand
     def handle(self, *args, **kwargs):
       ...

docs/dumpscript.rst

@@ -72,19 +72,16 @@ Naming conflicts
 
 Please take care that when naming the output files these filenames do not
 clash with other names in your import path. For instance, if the appname is
-the same as the script name, an importerror can occur because rather than importing 
+the same as the script name, an importerror can occur because rather than importing
 the application modules it tries to load the modules from the dumpscript file itself.
 
 Examples::
 
   # Wrong
   $ ./manage.py dumpscript appname > dumps/appname.py
-  
+
   # Right
   $ ./manage.py dumpscript appname > dumps/appname_all.py
-  
+
   # Right
   $ ./manage.py dumpscript appname.Somemodel > dumps/appname_somemodel.py
-
-
-

docs/installation_instructions.rst

@@ -27,7 +27,7 @@ Tracking the development version of *django command extensions* should be
 pretty stable and will keep you up-to-date with the latests fixes.
 
   $ pip install -e git+https://github.com/django-extensions/django-extensions.git#egg=django-extensions
-  
+
 You find the sources in src/django-extensions now.
 
 You can verify that the application is available on your PYTHONPATH by opening a python interpreter and entering the following commands:
@@ -70,4 +70,3 @@ for example:
 If the given application or python library is not installed on your system (or
 not in the python path) the executed command will raise an exception and inform
 you of the missing dependency.
-