mirror of
https://github.com/django/django.git
synced 2025-10-24 14:16:09 +00:00
Capitalized "Python" in docs and comments.
This commit is contained in:
@@ -621,7 +621,7 @@ start and end timestamps of an event, or the range of ages an activity is
|
||||
suitable for.
|
||||
|
||||
All of the range fields translate to :ref:`psycopg2 Range objects
|
||||
<psycopg2:adapt-range>` in python, but also accept tuples as input if no bounds
|
||||
<psycopg2:adapt-range>` in Python, but also accept tuples as input if no bounds
|
||||
information is necessary. The default is lower bound included, upper bound
|
||||
excluded; that is, ``[)``.
|
||||
|
||||
|
||||
@@ -668,7 +668,7 @@ Miscellaneous
|
||||
* :func:`~django.utils.http.int_to_base36` properly raises a
|
||||
:exc:`TypeError` instead of :exc:`ValueError` for non-integer inputs.
|
||||
|
||||
* The ``slugify`` template filter is now available as a standard python
|
||||
* The ``slugify`` template filter is now available as a standard Python
|
||||
function at :func:`django.utils.text.slugify`. Similarly, ``remove_tags`` is
|
||||
available at ``django.utils.html.remove_tags()``.
|
||||
|
||||
|
||||
@@ -148,7 +148,7 @@ by a name. This name is used to identify the logger for configuration
|
||||
purposes.
|
||||
|
||||
By convention, the logger name is usually ``__name__``, the name of
|
||||
the python module that contains the logger. This allows you to filter
|
||||
the Python module that contains the logger. This allows you to filter
|
||||
and handle logging calls on a per-module basis. However, if you have
|
||||
some other way of organizing your logging messages, you can provide
|
||||
any dot-separated name to identify your logger::
|
||||
|
||||
Reference in New Issue
Block a user