... ix are available in the history of the 1.0.X branch , but here are some of the highlights: Several fixes in django.contrib.comments , pertaining to RSS feeds of comments, default ordering of comments and the XHTML and internationalization of the default ... templates for comments. Multiple fixes for Django's support of Oracle databases, including pagination support for GIS QuerySets, more efficient s ... ngo 1.0.1 前のトピックへ Django 1.0.2 リリースノート 次のトピックへ Django 1.0 リリースノート 関連キーワード fixes support comments automatically strings improvements default Multiple including forms literal passed join were codebase contains compatibili ... ... ix are available in the history of the 1.0.X branch , but here are some of the highlights: Several fixes in django.contrib.comments , pertaining to RSS feeds of comments, default ordering of comments and the XHTML and internationalization of the default ... templates for comments. Multiple fixes for Django's support of Oracle databases, including pagination support for GIS QuerySets, more efficient s ... .1 前のトピックへ Django 1.0.2 リリースノート 次のトピックへ Django 1.0 リリースノート 関連キーワード Django fixes support comments automatically strings but improvements default Multiple including forms literal passed join were codebase contains new com ... ... ault=False in the field definition, or ensure the field is set to True or False before saving the object. Translations and comments in templates ¶ Extraction of translations after comments ¶ Extraction of translatable literals from templates with the mak ... he same line. E.g.: {# A comment #} {% trans "This literal was incorrectly ignored. Not anymore" %} Location of translator comments ¶ テンプレートにおける翻訳者のためのコメント specified using {# / #} need to be at the end of a line. If they are not, the ... comments are ignored and makemessages will generate a warning. For example: {# Translators: This is ignored #} {% trans "Translate ... ... ault=False in the field definition, or ensure the field is set to True or False before saving the object. Translations and comments in templates ¶ Extraction of translations after comments ¶ Extraction of translatable literals from templates with the mak ... he same line. E.g.: {# A comment #} {% trans "This literal was incorrectly ignored. Not anymore" %} Location of translator comments ¶ テンプレートにおける翻訳者のためのコメント specified using {# / #} need to be at the end of a line. If they are not, the ... comments are ignored and makemessages will generate a warning. For example: {# Translators: This is ignored #} {% trans "Translate ... ... fill in a form generated by the pre-upgrade Django instance and try to submit it to the upgraded Django instance: contrib.comments form security hash Consequences: The user will see the validation error "Security hash failed." Time period: The amount of ... backend. Concurrency behavior is defined by the underlying backend implementation. Check their documentation for details. COMMENTS_BANNED_USERS_GROUP setting ¶ Django's comments has historically supported excluding the comments of a special user group, ... a custom comment model manager to exclude the user group, like this: from django.conf import settings from django.contrib.comments.managers import CommentManager class BanningCommentManager ( CommentManager ): def get_query_set ( self ): qs = super () . ... ... fill in a form generated by the pre-upgrade Django instance and try to submit it to the upgraded Django instance: contrib.comments form security hash Consequences: The user will see the validation error "Security hash failed." Time period: The amount of ... backend. Concurrency behavior is defined by the underlying backend implementation. Check their documentation for details. COMMENTS_BANNED_USERS_GROUP setting ¶ Django's comments has historically supported excluding the comments of a special user group, ... a custom comment model manager to exclude the user group, like this: from django.conf import settings from django.contrib.comments.managers import CommentManager class BanningCommentManager ( CommentManager ): def get_query_set ( self ): qs = super () . ... ... e for every item in the feed. """ item_copyright = "Copyright (c) 2007, Sally Smith" # Hard-coded copyright notice. # ITEM COMMENTS URL -- It's optional to use one of these three. This is # a hook that specifies how to get the URL of a page for comments ... for a # given item. def item_comments ( self , obj ): """ Takes an item, as returned by items(), and returns the item's comments URL as a normal Python string. ... """ def item_comments ( self ): """ Returns the comments URL for every item in the feed. """ item_comments = "https://www.example.com/comments" ... ... e for every item in the feed. """ item_copyright = "Copyright (c) 2007, Sally Smith" # Hard-coded copyright notice. # ITEM COMMENTS URL -- It's optional to use one of these three. This is # a hook that specifies how to get the URL of a page for comments ... for a # given item. def item_comments ( self , obj ): """ Takes an item, as returned by items(), and returns the item's comments URL as a normal Python string. ... """ def item_comments ( self ): """ Returns the comments URL for every item in the feed. """ item_comments = "https://www.example.com/comments" ... ... our rules on line lengths. We allow up to 88 characters in code, as this is the line length used by black . Documentation, comments, and docstrings should be wrapped at 79 characters. These limits are checked when flake8 is run. String variable interpola ... erred. Don't waste time doing unrelated refactoring of existing code to adjust the formatting method. Avoid use of "we" in comments, e.g. "Loop over" rather than "We loop over". Use underscores, not camelCase, for variable, function and method names (i.e ... cket references for obscure issues where the ticket has additional details that can't be easily described in docstrings or comments. Include the ticket number at the end of a sentence like this: def test_foo (): """ A test docstring looks like this (#123 ... ... our rules on line lengths. We allow up to 88 characters in code, as this is the line length used by black . Documentation, comments, and docstrings should be wrapped at 79 characters. These limits are checked when flake8 is run. String variable interpola ... erred. Don't waste time doing unrelated refactoring of existing code to adjust the formatting method. Avoid use of "we" in comments, e.g. "Loop over" rather than "We loop over". Use underscores, not camelCase, for variable, function and method names (i.e ... cket references for obscure issues where the ticket has additional details that can't be easily described in docstrings or comments. Include the ticket number at the end of a sentence like this: def test_foo (): """ A test docstring looks like this (#123 ... 2026年10月08日