Re: [Django] #14861: Importing settings in a module that contains a logging Handler causes circular import.

[Django]

#14861: Importing settings in a module that contains a logging Handler causes
circular import.
--+
 Reporter:  donspaulding  |Owner:
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by simonpercivall):

 * cc: percivall@… (added)


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18907: Documentation regarding population of backrefs is incorrect

[Django]

#18907: Documentation regarding population of backrefs is incorrect
+
 Reporter:  simonpercivall  |Owner:  nobody
 Type:  Uncategorized   |   Status:  new
Component:  Documentation   |  Version:  1.4
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by simonpercivall):

 * cc: percivall@… (added)


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16671: 5th tutorial on turning Polls into a reusable app

[Django]

#16671: 5th tutorial on turning Polls into a reusable app
---+
 Reporter:  stumbles   |Owner:  ben@…
 Type:  New feature|   Status:  new
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by stumbles):

 Replying to answer my own question - the following looks like a neater
 approach:


 {{{
 from distutils.core import setup

 setup(
 name='django-polls',
 version='0.1',
 packages=['polls'],
 package_data={'polls': ['templates/polls/*']},
 license='',
 long_description=open('README.txt').read(),
 url='http://www.example.com/',
 author='Your Name',
 author_email='yourn...@example.com',
 )
 }}}

 Please let me know if there's a better approach.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #8851: Please add a default option to list_filter in the admin interface

[Django]

#8851: Please add a default option to list_filter in the admin interface
-+-
 Reporter:  Riskable |Owner:  nobody
 |   Status:  reopened
 Type:  New feature  |  Version:  master
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  admin, list_filter,  |  Needs documentation:  0
  default|  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by net147):

 * cc: net147 (added)


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18932: Buildin template tags seem to break i18n

[Django]

#18932: Buildin template tags seem to break i18n
-+-
 Reporter:  houmie   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:   |  Version:
  Internationalization   |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  i18n |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by houmie):

 * version:  1.4 =>
 * type:  Bug => New feature


Comment:

 Thanks for your feedback.

 Well I have already overridden the formats.py for both American and
 British (you can see that in the attached demo). Therefore upon changing
 the language, the best would be if the current language's formatting is
 picked up from formats.py.

 Otherwise if I had to pass a format string to the template it will be
 hardcoded in the template and the whole purpose of formats.py is gone
 through the wind. Since the moment the user changes the language, the
 formatting would change accordingly and hence the latter can't be
 hardcoded into the template.

 |date and |time are very useful to extract the data from a single date
 time field in the template.  Therefore shouldn't they respect localization
 and timezones respectively?

 If you agree to this I have changed the type of this ticket to 'New
 Feature'.
 Hopefully this can be implemented, as its very useful to have.

 Many Thanks,

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18920: Regresssiontests.template tests fail on windows due to expected '\n'

[Django]

#18920: Regresssiontests.template tests fail on windows due to expected '\n'
---+
 Reporter:  manfre |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+

Comment (by kmtracey):

 Which, now that you mention it, is another reason to not change the tests.
 If we change the tests to expect CRLF line endings when running on Windows
 then people who download the tarball to Windows and run tests from that
 install will see errors, because going that route doesn't auto-convert
 line endings to CRLF.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18920: Regresssiontests.template tests fail on windows due to expected '\n'

[Django]

#18920: Regresssiontests.template tests fail on windows due to expected '\n'
---+
 Reporter:  manfre |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+

Comment (by kmtracey):

 Those don't have any problem...the problem is introduced by git
 configurations which change LF in the files in the repo to CRLF on
 Windows.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18239: Only use custom subclass of HTMLParser for Python versions with buggy stdlib HTMLParser

[Django]

#18239: Only use custom subclass of HTMLParser for Python versions with buggy
stdlib HTMLParser
-+
 Reporter:  carljm   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Other) |  Version:  1.3
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by claudep):

 Applied to all Python 2.6 in [fcec904e4f3582a45d4d8e309e71e9f0c4d79a0c]

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18920: Regresssiontests.template tests fail on windows due to expected '\n'

[Django]

#18920: Regresssiontests.template tests fail on windows due to expected '\n'
---+
 Reporter:  manfre |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+

Comment (by claudep):

 What about tests run not from git checkout but with a downloaded tarball?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #14861: Importing settings in a module that contains a logging Handler causes circular import.

[Django]

#14861: Importing settings in a module that contains a logging Handler causes
circular import.
--+
 Reporter:  donspaulding  |Owner:
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by claudep):

 * owner:  nobody =>
 * status:  reopened => new
 * type:  Uncategorized => Bug


Comment:

 OK, no need for any more examples, I've been able to create a test case to
 reproduce the issue. I will propose a patch soon (including yours).

 > I thought I would get notified by just commenting. Apparently not.
 You need to put yourself in the cc field to get notified.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17869: With RemoteUserMiddleware, users keep being logged in after web server stops sending REMOTE_USER headers

[Django]

#17869: With RemoteUserMiddleware, users keep being logged in after web server
stops sending REMOTE_USER headers
-+---
 Reporter:  lamby|Owner:  bouchardsyl
 Type:  Bug  |   Status:  reopened
Component:  contrib.auth |  Version:  1.3
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+---

Comment (by bouchardsyl):

 After 3 months, I just stumbled upon my un-pulled commits regarding this
 issue.
 Time and commits have passed since, so I made a brand new pull request
 that works with today's fork of Django (Sept 9, 2012)
 Please see https://github.com/django/django/pull/365

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 2e9285: Fixed a couple of test failures on Windows.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2e928583861bc35f1ea137cb6f3353867f160bdb
  
https://github.com/django/django/commit/2e928583861bc35f1ea137cb6f3353867f160bdb
  Author: Karen Tracey 
  Date:   2012-09-09 (Sun, 09 Sep 2012)

  Changed paths:
M tests/regressiontests/utils/os_utils.py

  Log Message:
  ---
  Fixed a couple of test failures on Windows.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18932: Buildin template tags seem to break i18n

[Django]

#18932: Buildin template tags seem to break i18n
-+-
 Reporter:  houmie   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  1.4
  Internationalization   |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  i18n |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by claudep):

 Isn't this documented?:
 https://docs.djangoproject.com/en/dev/ref/templates/builtins/#date

 Quoted:
 {{{
 When used without a format string:

 {{ value|date }}

 ...the formatting string defined in the DATE_FORMAT setting will be used,
 without applying any localization.
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] fcec90: Fix an HTML-parser test that's failed in Python 2....

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: fcec904e4f3582a45d4d8e309e71e9f0c4d79a0c
  
https://github.com/django/django/commit/fcec904e4f3582a45d4d8e309e71e9f0c4d79a0c
  Author: Carl Meyer 
  Date:   2012-09-09 (Sun, 09 Sep 2012)

  Changed paths:
M django/utils/html_parser.py

  Log Message:
  ---
  Fix an HTML-parser test that's failed in Python 2.6.8 since 5c79dd58.

The problem description in #18239 asserted that
http://bugs.python.org/issue670664 was fixed in Python 2.6.8, but based on
http://bugs.python.org/issue670664#msg146770 it appears that's not correct; the
fix was only applied in 2.7, 3.2, and Python trunk. Therefore we must use our
patched HTMLParser subclass in all Python 2.6 versions.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18920: Regresssiontests.template tests fail on windows due to expected '\n'

[Django]

#18920: Regresssiontests.template tests fail on windows due to expected '\n'
---+
 Reporter:  manfre |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+

Comment (by kmtracey):

 I do run the test suite on Windows, and have not run into this issue.
 Apparently when I installed git on Windows (git --version reports for me
 `git version 1.7.10.msysgit.1`), it either defaulted to setting
 `core.autocrlf` to `input` or I told it to do so. Ultimately I think that
 is the right approach: tell git to NOT alter line endings. If the
 .gitattributes file can help with that, we should add that as well. I
 don't think we should change the tests to account for different line
 endings on !Windows/Linux/Mac (does Mac still have yet a different
 convention or have they changed to LF only?) because that is fragile:
 people will add new tests without remembering to account for line ending
 differences across platforms and those tests will break on non-Linux
 platforms. Instead we should document that if you are using git on Windows
 you should configure git to have `core.autocrlf` set to `input` and/or
 include a .gitattbutes file that prevents the "wrong" setting for this
 value from causing problems.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 75ef98: Fix Python 3 test failure introduced in a78dd109.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 75ef980e20fc0441aedb0645aa471c9fe606e3b0
  
https://github.com/django/django/commit/75ef980e20fc0441aedb0645aa471c9fe606e3b0
  Author: Carl Meyer 
  Date:   2012-09-09 (Sun, 09 Sep 2012)

  Changed paths:
M django/contrib/auth/decorators.py

  Log Message:
  ---
  Fix Python 3 test failure introduced in a78dd109.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] ffe8bc: Replaced backwards-incompatible changes reference

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ffe8bc00bf9b94a366ea3d1998a2712a908a9f1b
  
https://github.com/django/django/commit/ffe8bc00bf9b94a366ea3d1998a2712a908a9f1b
  Author: Karen Tracey 
  Date:   2012-09-09 (Sun, 09 Sep 2012)

  Changed paths:
M docs/releases/index.txt
M docs/topics/install.txt

  Log Message:
  ---
  Replaced backwards-incompatible changes reference

The previously-referenced wiki page documents backwards-incompatible
changes from .96 to 1.0. Changed that referece to point to current
in-development release notes, which is where such changes are now
documented.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18933: docstring for cycle templatetag method differs from documentation

[Django]

#18933: docstring for cycle templatetag method differs from documentation
-+-
 Reporter:  martey   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.4
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  cycle templatetag|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by mjtamlyn):

 * cc: marc.tamlyn@… (added)
 * has_patch:  0 => 1
 * stage:  Unreviewed => Ready for checkin


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #14861: Importing settings in a module that contains a logging Handler causes circular import.

[Django]

#14861: Importing settings in a module that contains a logging Handler causes
circular import.
---+
 Reporter:  donspaulding   |Owner:  nobody
 Type:  Uncategorized  |   Status:  reopened
Component:  Core (Other)   |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by simonpercivall):

 I thought I would get notified by just commenting. Apparently not.

 It's still reproducible with 1.5 HEAD.

 A sample project? How? A zip? Sure, if it's necessary.

 It's pretty easy to see, however, by just looking at the code, that
 referencing settings from the logging config, directly or by importing a
 module that does, ''before'' _wrapped is set will cause infinite
 recursion. And since my patch moves logging setup to ''after'' _wrapped is
 set, the issue is resolved.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18907: Documentation regarding population of backrefs is incorrect

[Django]

#18907: Documentation regarding population of backrefs is incorrect
+
 Reporter:  simonpercivall  |Owner:  nobody
 Type:  Uncategorized   |   Status:  new
Component:  Documentation   |  Version:  1.4
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by simonpercivall):

 When running Django in a larger project, with something like mod_wsgi or
 gunicorn instead of runserver, and with Celery or other jobs doing
 background processing, models are also not auto-loaded, unless, as you
 say, they're loaded as a side-effect of other operations.

 Changing the text to say "under normal operation", therefore, is deeply
 misleading.

 I hesitated whether to submit this as a documentation issue or as a core
 bug. It might be argued that population of backrefs is a guarantee that
 Django actually ''should'' make. From my perspective, that would probably
 be the preferred solution.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 9ca17f: Replace nested try/finally try/except with try/exc...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 9ca17f883d7a637581befe8092120242d0534673
  
https://github.com/django/django/commit/9ca17f883d7a637581befe8092120242d0534673
  Author: Florian Apolloner 
  Date:   2012-09-09 (Sun, 09 Sep 2012)

  Changed paths:
M django/core/handlers/wsgi.py

  Log Message:
  ---
  Replace nested try/finally try/except with try/except/finally.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #18934: Remove versionadded/versionchanged annotations for Django 1.3

[Django]

#18934: Remove versionadded/versionchanged annotations for Django 1.3
--+
 Reporter:  timo  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Per what we have done in previous releases, we should remove the
 annotations for Django 1.3 in master since it will be unsupported when
 Django 1.5 is released.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18766: Models with datetime fields fail to save when date is below 1900 and USE_TZ is True

[Django]

#18766: Models with datetime fields fail to save when date is below 1900 and 
USE_TZ
is True
-+-
 Reporter:  void |Owner:  aaugustin
 Type:   |   Status:  reopened
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  timezone, tz |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * status:  closed => reopened
 * component:  Uncategorized => Documentation
 * type:  Bug => Cleanup/optimization
 * resolution:  needsinfo =>
 * stage:  Unreviewed => Accepted


Comment:

 I'm accepting the ticket primarily as a documentation issue. This is
 related to #17262. I still have to decide how to deal with this.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.