Re: [Django] #15619: Logout link should be protected

[Django]

#15619: Logout link should be protected
---+--
 Reporter:  void   |Owner:  ashchristopher
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by ashchristopher):

 Talking to julienphalip on #django-dev - we are going to look at getting
 ModelAdmin.media() to return only the js files needed for a given view.
 This may require changing ModelAdmin.media() to be a method that takes
 arguments, rather than staying as a property.

-- 
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] #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:
 Keywords:  cycle templatetag|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Martey Dodoo ):

 * needs_docs:   => 0
 * needs_tests:   => 0
 * needs_better_patch:   => 0


Comment:

 I have added a fix for this on
 [https://github.com/martey/django/tree/ticket_18933 a branch on Github]
 and submitted a pull request.

-- 
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] #18933: docstring for cycle templatetag method differs from documentation

[Django]

#18933: docstring for cycle templatetag method differs from documentation
--+---
 Reporter:  martey|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.4
 Severity:  Normal|   Keywords:  cycle templatetag
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+---
 A code example in the docstring in the cycle method in
 django.template.defaulttags for the silent option of the cycle templatetag
 differs from the example in the actual documentation.

 
[https://github.com/django/django/blob/759ae3c2dafe149485a15d9a3bc97527c1ac1163/django/template/defaulttags.py#L536
 Line 536 of defaulttags.py] contains "{% cycle rowcolors %}" when it
 should be "{{ rowcolors }}". The documentation was changed in
 
[https://github.com/django/django/commit/c260c533e1f1553548fc98f24820805af87f72bf
 a commit fixing ticket #15570].

-- 
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] 5e99a3: Adjust d7853c5 to not show ignorable warnings when...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 5e99a3d41b5d7b7d8d135283fd25262fdcb1b7fd
  
https://github.com/django/django/commit/5e99a3d41b5d7b7d8d135283fd25262fdcb1b7fd
  Author: Malcolm Tredinnick 
  Date:   2012-09-08 (Sat, 08 Sep 2012)

  Changed paths:
M django/contrib/sessions/tests.py

  Log Message:
  ---
  Adjust d7853c5 to not show ignorable warnings when running tests.



-- 
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:  Bug|   Status:  closed
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:  needsinfo
 Keywords:  timezone, tz   | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by void):

 Sorry, that was me, was logged out somehow.

-- 
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:  Bug|   Status:  closed
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:  needsinfo
 Keywords:  timezone, tz   | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by anonymous):

 Yes, installing pytz resolves the problem.

-- 
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] a3b213: Remove an outdated import inadvertently introduced...

[GitHub]

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

  Changed paths:
M tests/regressiontests/comment_tests/urls_default.py

  Log Message:
  ---
  Remove an outdated import inadvertently introduced in tests.



-- 
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] #18715: Tutorial Page 3 Refactor

[Django]

#18715: Tutorial Page 3 Refactor
--+
 Reporter:  pydanny   |Owner:  pydanny
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.4
 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 pydanny):

 What should I do to move this ticket forward?

-- 
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] c4aa26: Internal refactoring; moving LOOKUP_SEP up one lev...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c4aa26a983c91b1ec015fe0552077847116dfab7
  
https://github.com/django/django/commit/c4aa26a983c91b1ec015fe0552077847116dfab7
  Author: Malcolm Tredinnick 
  Date:   2012-09-08 (Sat, 08 Sep 2012)

  Changed paths:
M django/contrib/admin/options.py
M django/contrib/admin/util.py
M django/contrib/gis/db/models/sql/where.py
A django/db/models/constants.py
M django/db/models/query.py
M django/db/models/sql/compiler.py
M django/db/models/sql/constants.py
M django/db/models/sql/expressions.py
M django/db/models/sql/query.py
M django/db/models/sql/subqueries.py

  Log Message:
  ---
  Internal refactoring; moving LOOKUP_SEP up one level.

In an ideal world, nothing except django.db.models.query should have to
import stuff from django.models.sql.*. A few things were needing to get
hold of sql.constants.LOOKUP_SEP, so this commit moves it up to
django.db.models.constants.LOOKUP_SEP.

There are still a couple of places (admin) poking into sql.* to get
QUERY_TERMS, which is unfortunate, but a slightly different issue and
harder to adjust.



-- 
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 houmie):

 In the demo, simply change the Language to British English, and you would
 see right away, that the latter two fields change the date format, while
 the former two fields with |date tag, stay as nothing had changed...

-- 
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:  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
-+-
Changes (by houmie):

 * needs_better_patch:   => 0
 * type:  Uncategorized => Bug
 * component:  Uncategorized => Internationalization
 * needs_tests:   => 0
 * needs_docs:   => 0


-- 
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] #18932: Buildin template tags seem to break i18n

[Django]

#18932: Buildin template tags seem to break i18n
---+
 Reporter:  houmie |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.4
 Severity:  Normal |   Keywords:  i18n
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 Within my template as long as I have the following, the template
 automatically converts the datetime from UTC into my currently selected
 timezone. And I can also switch to a different culture (US to UK format)
 and the date and time format do change accordingly.


 {{{
 {% load l10n %}
 {% for item in calls %}
  {{ item.conversation_datetime }}
  {{ item.conversation_datetime }}
 {% endfor %}
 }}}


 Now all I need to do is to extract the localized date for the former and
 localized time for the latter. So I thought lets bang a template tag in
 there and life is good.


 {{{
 {% load l10n %}
 {% for item in calls %}
  {{ item.conversation_datetime|date }}
  {{ item.conversation_datetime|time }}
 {% endfor %}
 }}}


 But if life was good, I wouldn't be sitting here and writing this would I?
 ;) The moment these filters are set, the format for these two fields seems
 to be fixed to the US culture. Date format is mm/dd/ and time is 12
 hrs am/pm.

 Selecting the British language as I did before successfully has no longer
 any effect.

 Please see a demo attached to this ticket.

-- 
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] #15552: LOGIN_URL should allow named urls

[Django]

#15552: LOGIN_URL should allow named urls
-+-
 Reporter:  WoLpH|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  contrib.auth |  Version:  1.2
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  login_url| Triage Stage:  Accepted
  logout_url login_redirect_url  |  Needs documentation:  0
  named_url url_tag dceu2011 |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by Carl Meyer ):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [a78dd109e6c81c49e90e36e9b793bad67c46c23c]:
 {{{
 #!CommitTicketReference repository=""
 revision="a78dd109e6c81c49e90e36e9b793bad67c46c23c"
 Fixed #15552 -- LOGIN_URL and LOGIN_REDIRECT_URL can take URLpattern
 names.

 Thanks UloPe and Eric Florenzano for the patch, and Malcolm Tredinnick for
 review.
 }}}

-- 
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] a78dd1: Fixed #15552 -- LOGIN_URL and LOGIN_REDIRECT_URL c...

[GitHub]

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

  Changed paths:
M django/contrib/auth/decorators.py
M django/contrib/auth/tests/decorators.py
M django/contrib/auth/views.py
M django/shortcuts/__init__.py
M docs/ref/settings.txt
M docs/releases/1.5.txt
M docs/topics/auth.txt
M tests/regressiontests/comment_tests/tests/__init__.py
A tests/regressiontests/comment_tests/urls_default.py
A tests/regressiontests/resolve_url/__init__.py
A tests/regressiontests/resolve_url/models.py
A tests/regressiontests/resolve_url/tests.py
M tests/runtests.py

  Log Message:
  ---
  Fixed #15552 -- LOGIN_URL and LOGIN_REDIRECT_URL can take URLpattern names.

Thanks UloPe and Eric Florenzano for the patch, and Malcolm Tredinnick for
review.



-- 
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] #15906: New head method needs documentation

[Django]

#15906: New head method needs documentation
---+
 Reporter:  jezdez |Owner:  zsiciarz
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.3
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  1  |UI/UX:  0
---+
Changes (by Tim Graham ):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [518c58296667ffc36f90b873eb97aa99fa00eb1e]:
 {{{
 #!CommitTicketReference repository=""
 revision="518c58296667ffc36f90b873eb97aa99fa00eb1e"
 Fixed #15906 - Documented HEAD method in CBVs; thanks zsiciarz for the
 patch.
 }}}

-- 
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] 518c58: Fixed #15906 - Documented HEAD method in CBVs; tha...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 518c58296667ffc36f90b873eb97aa99fa00eb1e
  
https://github.com/django/django/commit/518c58296667ffc36f90b873eb97aa99fa00eb1e
  Author: Tim Graham 
  Date:   2012-09-08 (Sat, 08 Sep 2012)

  Changed paths:
M docs/ref/class-based-views/base.txt
M docs/topics/class-based-views/index.txt

  Log Message:
  ---
  Fixed #15906 - Documented HEAD method in CBVs; thanks zsiciarz for the patch.



-- 
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] #15906: New head method needs documentation

[Django]

#15906: New head method needs documentation
---+
 Reporter:  jezdez |Owner:  zsiciarz
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.3
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  1  |UI/UX:  0
---+

Comment (by timo):

 Consulted with Malcolm on IRC -- didn't seem like using last_modified is
 viable so going to commit this as is.

  malcolmt: the code in that comment looks essentially correct. Have you
 tried it and does it work?
  malcolmt: That's what method_decorator() is for.
  me: the issue with the code as I posted it is that latest_entry needs to
 be called with "self" (exception is: latest_entry() takes exactly 2
 arguments (1 given))
  malcolmt: oooh.
  malcolmt: That old chestnut: functions != methods. again. :-(
  malcolmt: and you need "self" in that function, so you can't make it
 @classmethod.
  malcolmt: bummer :(
  me: do you think the answer is "it's not possible" then?
  malcolmt: Probably "not possible yet". It *might* be worth changing the
 signature on last_modified and etag to make them able to handle methods.
 I'm waiting for carljm to provide a consult.
  malcolmt: It's almost unnecessarily fiddly sometimes in Python to make
 things that work with both functions and methods, it seems.
  me: sounds good, thanks for the assist.  I'll go ahead and commit the doc
 and we can revise it to use last_modified if that works out
  malcolmt: I think you're using last_modified poorly in that example,
 since it's meant to be computed based on the request and the URL params.
 "self" really has no role there except as a way to avoid having to pull
 out the object again.
  malcolmt: What's really need is a last_modified_for_methods() function
 that understands how to work with class methods.
  malcolmt: I don't think there's an easy soln in the current setup. I also
 have trouble caring much about class-based views, so it's not something
 I'm likely to spend time on fixing. Sorry.

-- 
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] #18657: Inconsistent db names in example

[Django]

#18657: Inconsistent db names in example
---+
 Reporter:  msb@…  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by mjtamlyn):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Fixed in
 
https://github.com/django/django/commit/c26dd4f154fe9d7aedeb28b0de4bb8cca85b55f9

-- 
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] #18931: Add predicate functionality to Q objects

[Django]

#18931: Add predicate functionality to Q objects
--+
 Reporter:  ptone |  Owner:  ptone
 Type:  New feature   | Status:  new
Component:  Database layer (models, ORM)  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 A predicate is condition that can be matched against some item to
 determine whether that item meets the condition.

 Django has a relatively rich set of lookup terms that can be used in
 filtering a queryset.

 What is proposed is a new behavior of a Q object, that allows the
 conditions described in the formation of a Q instance, to be tested agains
 a model instance.

 The initial implementation of this was released separately:

 https://github.com/ptone/django-predicate

 Current work-in-progress to bring this into Django is here:

 https://github.com/ptone/django/compare/master...q-predicate

-- 
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] 72ca53: Fixed typo in commit for #15730; thanks Bruno Reni...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 72ca530af5e85bef6292bb1a16f3d9062f172f63
  
https://github.com/django/django/commit/72ca530af5e85bef6292bb1a16f3d9062f172f63
  Author: Tim Graham 
  Date:   2012-09-08 (Sat, 08 Sep 2012)

  Changed paths:
M docs/ref/class-based-views/base.txt

  Log Message:
  ---
  Fixed typo in commit for #15730; thanks Bruno Renié for the catch.



-- 
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] #17787: Clear setting-dependant caches when settings are overridden (in tests)

[Django]

#17787: Clear setting-dependant caches when settings are overridden (in tests)
---+--
 Reporter:  aaugustin  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.4-beta-1
 Severity:  Release blocker|   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):

 * has_patch:  0 => 1


Comment:

 Replying to [comment:12 aaugustin]:
 > We're in an inconsistent state right now. Some settings are properly
 reset and others aren't;

 Let's create tickets for each setting unproperly reset. But auditing the
 code to relate settings with global cached variables might be something
 hard. I'm afraid only bugs will reveal those.

 > the docs still say that the signal isn't used.
 >
 > We still have to document the new behavior before the next release. At
 worst, open django/tests/signals.py, make a list of settings that are
 reset, and put that in the docs...

 I'm attaching a patch for updating the docs.

-- 
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] 67dcee: Remove a couple unused imports.

[GitHub]

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

  Changed paths:
M django/conf/__init__.py
M django/contrib/sessions/tests.py

  Log Message:
  ---
  Remove a couple unused imports.



-- 
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] #18545: Improve the error message when the implicit settings configuration fails

[Django]

#18545: Improve the error message when the implicit settings configuration fails
--+
 Reporter:  ncoghlan  |Owner:  carljm
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (Other)  |  Version:  1.4
 Severity:  Normal|   Resolution:  fixed
 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 Carl Meyer ):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [307706d082d20ac868654ccbaee18879db5197db]:
 {{{
 #!CommitTicketReference repository=""
 revision="307706d082d20ac868654ccbaee18879db5197db"
 Fixed #18545 -- Make the 'no DJANGO_SETTINGS_MODULE' error message more
 useful.Thanks Nick Coghlan for the report, and Malcolm Tredinnick for
 review.
 }}}

-- 
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] 307706: Fixed #18545 -- Make the 'no DJANGO_SETTINGS_MODUL...

[GitHub]

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

  Changed paths:
M django/conf/__init__.py
M django/core/management/__init__.py
M tests/regressiontests/admin_scripts/tests.py

  Log Message:
  ---
  Fixed #18545 -- Make the 'no DJANGO_SETTINGS_MODULE' error message more 
useful.Thanks Nick Coghlan for the report, and Malcolm Tredinnick for review.



-- 
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] 5d1f09: Ticket 18657: Fix inconsistent DB names in router ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 5d1f09f450686c53ead6f2784ba5c94ea6dccf36
  
https://github.com/django/django/commit/5d1f09f450686c53ead6f2784ba5c94ea6dccf36
  Author: James Bennett 
  Date:   2012-09-08 (Sat, 08 Sep 2012)

  Changed paths:
M docs/topics/db/multi-db.txt

  Log Message:
  ---
  Ticket 18657: Fix inconsistent DB names in router example.

This rewrites the entire example to use the same DB names throughout,
and also is hopefully a bit more sensibly described. Additionally, the
missing import of the random module for choosing a read slave is
included in the example now.


  Commit: 408c10e541440b078ccf5d6fcb3f344b7a94d048
  
https://github.com/django/django/commit/408c10e541440b078ccf5d6fcb3f344b7a94d048
  Author: James Bennett 
  Date:   2012-09-08 (Sat, 08 Sep 2012)

  Changed paths:
M docs/topics/db/multi-db.txt

  Log Message:
  ---
  Untabify multi-db docs.


  Commit: 5c5226a52029ae75a27d6006528163a699ed0617
  
https://github.com/django/django/commit/5c5226a52029ae75a27d6006528163a699ed0617
  Author: James Bennett 
  Date:   2012-09-08 (Sat, 08 Sep 2012)

  Changed paths:
M docs/topics/db/multi-db.txt

  Log Message:
  ---
  Fix typo: Non -> None


  Commit: c26dd4f154fe9d7aedeb28b0de4bb8cca85b55f9
  
https://github.com/django/django/commit/c26dd4f154fe9d7aedeb28b0de4bb8cca85b55f9
  Author: James Bennett 
  Date:   2012-09-08 (Sat, 08 Sep 2012)

  Changed paths:
M docs/topics/db/multi-db.txt

  Log Message:
  ---
  Merge pull request #363 from ubernostrum/multidb-examples-18657

Ticket 18657: Fix inconsistent DB names in router example.


Compare: https://github.com/django/django/compare/d7853c55ed02...c26dd4f154fe

-- 
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] #18545: Improve the error message when the implicit settings configuration fails

[Django]

#18545: Improve the error message when the implicit settings configuration fails
--+
 Reporter:  ncoghlan  |Owner:  carljm
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  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 carljm):

 * owner:  nobody => carljm
 * component:  Uncategorized => Core (Other)
 * type:  Uncategorized => Cleanup/optimization


Comment:

 Replying to [comment:2 anonymous]:
 > Russell Keith-Magee and I were able to discuss this briefly at PyConAU.
 For the second part, it may be worth pursuing that as a general
 improvement to LazyObject. The trick is to avoid losing existing debugging
 data in the Python 2 case - in Python 3, it would be possible to just do
 "raise X from Y" when the init call fails to add the extra info about
 which attribute was being looked up without losing the original traceback,
 but in Python 2, raising a new exception means losing the original
 traceback. Perhaps it would be enough to just preserve the original error
 message? Is gaining the attribute name worth losing the inner part of the
 traceback?

 I don't understand the necessity for `raise X from Y` in this case, or any
 of the associated Python 2 difficulty. All that's necessary is for
 `LazySettings` to override `__getattr__` to pass the requested attribute
 name into `_setup`. I have this implemented at
 https://github.com/carljm/django/compare/ticket_18545

 Worth noting this doesn't really help with *incrementally* figuring out
 the settings you need, it only helps with the very first one, since you
 only see this error if you've done nothing at all settings-related. Once
 you've called `settings.configure()`, if there's an additional setting you
 haven't set, you'll get a setting-specific error message from some other
 part of Django (e.g. the ORM will complain if you don't have `DATABASES`,
 the URL-resolver will complain if you have no `ROOT_URLCONF`, etc). But
 it's still marginally useful that initial time, and there's little cost,
 so going ahead and adding it.

 Mentioning `settings.configure()` is of course a great idea, thanks for
 suggesting it.

-- 
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] #18699: Branch Policy documentation needs updating

[Django]

#18699: Branch Policy documentation needs updating
--+
 Reporter:  DrMeers   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.4
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by ubernostrum):

 Old documentation display issue tracking in #18930.

-- 
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] #18930: Website docs builder should clean to get rid of old docs

[Django]

#18930: Website docs builder should clean to get rid of old docs
-+-
   Reporter: |  Owner:  nobody
  ubernostrum| Status:  new
   Type:  Bug|Version:  1.4
  Component: |   Keywords:
  Djangoproject.com Web site |  Has patch:  0
   Severity:  Normal |Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 Currently it doesn't, which is why we got ticket #18699, and why
 [https://docs.djangoproject.com/en/dev/internals/contributing/writing-code
 /branch-policy/ this document] still exists on-site even though it was
 removed from the docs months ago.

 A step should be added to clean out old generated HTML, so we don't run
 into this again.

-- 
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] #18699: Branch Policy documentation needs updating

[Django]

#18699: Branch Policy documentation needs updating
--+
 Reporter:  DrMeers   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.4
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by ubernostrum):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 File was removed:
 
https://github.com/django/django/commit/90fb6a46485d4f3c70d3864ab0a0e2f619449d31

 A separate issue causes it to still be displayed on-site.

-- 
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] d7853c: Removed warning check in test_load_overlong_key

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: d7853c55ed027cdffcda88205b9d5c16861a5bcb
  
https://github.com/django/django/commit/d7853c55ed027cdffcda88205b9d5c16861a5bcb
  Author: Claude Paroz 
  Date:   2012-09-08 (Sat, 08 Sep 2012)

  Changed paths:
M django/contrib/sessions/tests.py

  Log Message:
  ---
  Removed warning check in test_load_overlong_key

Some backends issue a warning here, others not. This is not the primary
goal of the test, so the assertion about the warning has been removed.
Thanks Carl Meyer for noticing the issue and suggesting the fix.



-- 
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] 7c6630: [1.4.x] Fixed some broken links in 1.4 docs

[GitHub]

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: 7c6630920eb5a755ad1c12ea999f729cc7d9b7d0
  
https://github.com/django/django/commit/7c6630920eb5a755ad1c12ea999f729cc7d9b7d0
  Author: Tim Graham 
  Date:   2012-09-08 (Sat, 08 Sep 2012)

  Changed paths:
M docs/intro/whatsnext.txt
M docs/ref/forms/validation.txt
M docs/topics/auth.txt
M docs/topics/db/transactions.txt

  Log Message:
  ---
  [1.4.x] Fixed some broken links in 1.4 docs



-- 
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] 3bdb65: Updated print statements to work with py3; thanks ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 3bdb65dc5959b62f910ca498cce19682e2db6308
  
https://github.com/django/django/commit/3bdb65dc5959b62f910ca498cce19682e2db6308
  Author: Tim Graham 
  Date:   2012-09-08 (Sat, 08 Sep 2012)

  Changed paths:
M docs/ref/models/querysets.txt

  Log Message:
  ---
  Updated print statements to work with py3; thanks Claude Paroz noting this.



-- 
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] 4754f1: Moved the admin inline JS to new JS files for clea...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 4754f122dd9b41fc9b2dee3fa74e19fc384237ab
  
https://github.com/django/django/commit/4754f122dd9b41fc9b2dee3fa74e19fc384237ab
  Author: Travis Swicegood 
  Date:   2012-09-08 (Sat, 08 Sep 2012)

  Changed paths:
M AUTHORS
M django/contrib/admin/options.py
M django/contrib/admin/static/admin/js/inlines.js
M django/contrib/admin/static/admin/js/inlines.min.js
M django/contrib/admin/templates/admin/edit_inline/stacked.html
M django/contrib/admin/templates/admin/edit_inline/tabular.html
M tests/regressiontests/admin_inlines/tests.py

  Log Message:
  ---
  Moved the admin inline JS to new JS files for cleanliness.



-- 
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] #16455: Postgis 2.0 Compatibility

[Django]

#16455: Postgis 2.0 Compatibility
-+
 Reporter:  ckarrie  |Owner:  jbronn
 Type:  New feature  |   Status:  assigned
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  postgis 2.0  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by fcurella):

 * needs_tests:  1 => 0


Comment:

 I've fixed the test and run them using postgres9.1 + postgis 1.5. I would
 love if some could run the tests under postgres 8 and report if
 `django.contrib.gis.gdal.tests.test_ds.DataSourceTest.test05_geometries`
 passes.

-- 
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] #16218: Class-based month archive doesn't behave like previous generic view

[Django]

#16218: Class-based month archive doesn't behave like previous generic view
---+-
 Reporter:  nnrcschmdt |Owner:  aaugustin
 Type:  Bug|   Status:  new
Component:  Generic views  |  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 aaugustin):

 * needs_better_patch:  1 => 0


Comment:

 I just reviewed the history of this ticket and updated the patch. Pull
 request: https://github.com/django/django/pull/362

 The documented order seems much more logical to me than the implemented
 order. Like nnrcschmdt and bpeschier, I'd prefer to restore the documented
 order, even though it introduces a backwards incompatibility.

 As an unscientific datapoint, I always reverse `date_list` in year and
 month views in my templates; when we fix this ticket I'll be able to
 remove that code.

-- 
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] #18478: Field.get_default will stringify everything that isn't a callable

[Django]

#18478: Field.get_default will stringify everything that isn't a callable
--+
 Reporter:  enrico|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.4
 Severity:  Normal|   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 Tim Graham ):

 In [cd5181f84c7d4f2002efb777b6cf042771135f7a]:
 {{{
 #!CommitTicketReference repository=""
 revision="cd5181f84c7d4f2002efb777b6cf042771135f7a"
 [1.4.X] Fixed #18478 - Documented how to use a mutable default in a model
 field.

 Backport of 6e2bb344e4 from master
 }}}

-- 
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] cd5181: [1.4.X] Fixed #18478 - Documented how to use a mut...

[GitHub]

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: cd5181f84c7d4f2002efb777b6cf042771135f7a
  
https://github.com/django/django/commit/cd5181f84c7d4f2002efb777b6cf042771135f7a
  Author: Tim Graham 
  Date:   2012-09-08 (Sat, 08 Sep 2012)

  Changed paths:
M docs/ref/models/fields.txt

  Log Message:
  ---
  [1.4.X] Fixed #18478 - Documented how to use a mutable default in a model 
field.

Backport of 6e2bb344e4 from master



-- 
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] #18478: Field.get_default will stringify everything that isn't a callable

[Django]

#18478: Field.get_default will stringify everything that isn't a callable
--+
 Reporter:  enrico|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.4
 Severity:  Normal|   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
--+
Changes (by Tim Graham ):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 In [6e2bb344e40dafdf462f6fb660837fa061faf549]:
 {{{
 #!CommitTicketReference repository=""
 revision="6e2bb344e40dafdf462f6fb660837fa061faf549"
 Fixed #18478 - Documented how to use a mutable default in a model field.
 }}}

-- 
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] 6e2bb3: Fixed #18478 - Documented how to use a mutable def...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 6e2bb344e40dafdf462f6fb660837fa061faf549
  
https://github.com/django/django/commit/6e2bb344e40dafdf462f6fb660837fa061faf549
  Author: Tim Graham 
  Date:   2012-09-08 (Sat, 08 Sep 2012)

  Changed paths:
M docs/ref/models/fields.txt

  Log Message:
  ---
  Fixed #18478 - Documented how to use a mutable default in a model field.



-- 
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] #9962: Add a tutorial for the testing framework

[Django]

#9962: Add a tutorial for the testing framework
---+
 Reporter:  russellm   |Owner:
 Type:  New feature|   Status:  new
Component:  Documentation  |  Version:  1.0
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by holdenweb):

 Please note that http://djangotesting.com/ is currently unavailable due to
 expiry of the domain name registration.

-- 
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] #10317: New Feature: django.contrib.markup.fields.MarkupField

[Django]

#10317: New Feature: django.contrib.markup.fields.MarkupField
+-
 Reporter:  jamesturk   |Owner:  jamesturk
 Type:  New feature |   Status:  closed
Component:  contrib.markup  |  Version:  master
 Severity:  Normal  |   Resolution:  wontfix
 Keywords:  markup forms| Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  1
  Needs tests:  1   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+-
Changes (by claudep):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 contrib.markup has been deprecated (#18504) and will be removed in Django
 1.6. Closing as obsolete.

-- 
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] #10146: Support for contrib/markdown extension_configs in settings.py

[Django]

#10146: Support for contrib/markdown extension_configs in settings.py
-+-
 Reporter:  bdejong  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  contrib.markup   |  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  markdown config  | Triage Stage:  Accepted
  extensions extension_configs   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by claudep):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 contrib.markup has been deprecated (#18504) and will be removed in Django
 1.6. Closing as obsolete.

-- 
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] #13997: multiwidget needs better docs

[Django]

#13997: multiwidget needs better docs
---+
 Reporter:  cuci   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Documentation  |  Version:  1.4
 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 timo):

 * needs_docs:  1 => 0
 * has_patch:  0 => 1


-- 
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] #6526: Add remove/escape/replace functions to markdown filter

[Django]

#6526: Add remove/escape/replace functions to markdown filter
-+-
 Reporter:  taojian  |Owner:  thomaspurchas
 Type:  New feature  |   Status:  closed
Component:  contrib.markup   |  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  markup markdown  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

 * status:  assigned => closed
 * resolution:   => wontfix


Comment:

 contrib.markup has been deprecated (#18504) and will be removed in Django
 1.6. We won't add any new feature to it, and we encourage users to create
 external apps or contribute to an existing one. Closing as obsolete.

-- 
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] #6182: python-markdown2 support in markup

[Django]

#6182: python-markdown2 support in markup
-+-
 Reporter:  John Downey  |Owner:  nobody
  |   Status:  closed
 Type:  New feature  |  Version:  master
Component:  contrib.markup   |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  markdown markup  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by claudep):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 contrib.markup has been deprecated (#18504) and will be removed in Django
 1.6. Closing as obsolete.

-- 
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] #16439: select_related does not work with nullable fields unless field is specified.

[Django]

#16439: select_related does not work with nullable fields unless field is
specified.
---+
 Reporter:  dloewenherz|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.3
 Severity:  Normal |   Resolution:  fixed
 Keywords:  db | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by mtredinnick):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Quoting from the current documentation
 
(https://docs.djangoproject.com/en/dev/ref/models/querysets/#django.db.models.query.QuerySet.select_related):

Note that, by default, select_related() does not follow foreign keys
 that have null=True.

 So no documentation patch required. The reason it's like this is because
 nullable joins require an outer join between tables and is sufficiently
 performance impacting to not do by default.

-- 
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] #18628: Adding methods/attributes to display views

[Django]

#18628: Adding methods/attributes to display views
--+
 Reporter:  pydanny   |Owner:  pydanny
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.4
 Severity:  Normal|   Resolution:  fixed
 Keywords:  cbv   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham ):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [20ee727ac9e0a374401473d90f055393944f197e]:
 {{{
 #!CommitTicketReference repository=""
 revision="20ee727ac9e0a374401473d90f055393944f197e"
 Fixed #18628 - Added methods/attributes to CBV docs.  Thanks Daniel
 Greenfeld!
 }}}

-- 
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] 20ee72: Fixed #18628 - Added methods/attributes to CBV doc...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 20ee727ac9e0a374401473d90f055393944f197e
  
https://github.com/django/django/commit/20ee727ac9e0a374401473d90f055393944f197e
  Author: Tim Graham 
  Date:   2012-09-08 (Sat, 08 Sep 2012)

  Changed paths:
M docs/ref/class-based-views/base.txt
M docs/ref/class-based-views/generic-display.txt
M docs/ref/class-based-views/mixins-multiple-object.txt
M docs/ref/class-based-views/mixins-simple.txt

  Log Message:
  ---
  Fixed #18628 - Added methods/attributes to CBV docs.  Thanks Daniel Greenfeld!



-- 
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] #17261: Refactor parsing of date and times

[Django]

#17261: Refactor parsing of date and times
-+-
 Reporter:  aaugustin|Owner:  aaugustin
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Core (Other) |   Resolution:
 Severity:  Normal   |  worksforme
 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 aaugustin):

 * status:  new => closed
 * resolution:   => worksforme


Comment:

 If it ain't broken don't fix it...

-- 
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] #16502: CreateView useless error message when template_name is not specified

[Django]

#16502: CreateView useless error message when template_name is not specified
-+-
 Reporter:  silverghost3@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Generic views|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  CreateView "generic  | Triage Stage:  Accepted
  view"  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by aaugustin):

 * owner:  aaugustin => nobody


-- 
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] #18832: The example for excluding field from forms uses the wrong field.

[Django]

#18832: The example for excluding field from forms uses the wrong field.
---+---
 Reporter:  nedbatchelder  |Owner:  nickmartini
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   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
---+---
Changes (by Tim Graham ):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [76bd33539f8a188c4b1770babe6d2b55e5030c68]:
 {{{
 #!CommitTicketReference repository=""
 revision="76bd33539f8a188c4b1770babe6d2b55e5030c68"
 Merge pull request #359 from nmartini/ticket_18832

 Fixed #18832 - Updated ModelForm example fields to match note below
 }}}

-- 
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] 571698: fixing modelforms example code, ticket #18832

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 571698997f0ce3f362ee684754447e2e8a177863
  
https://github.com/django/django/commit/571698997f0ce3f362ee684754447e2e8a177863
  Author: Nick Martini 
  Date:   2012-09-08 (Sat, 08 Sep 2012)

  Changed paths:
M docs/topics/forms/modelforms.txt

  Log Message:
  ---
  fixing modelforms example code, ticket #18832


  Commit: 76bd33539f8a188c4b1770babe6d2b55e5030c68
  
https://github.com/django/django/commit/76bd33539f8a188c4b1770babe6d2b55e5030c68
  Author: Tim Graham 
  Date:   2012-09-08 (Sat, 08 Sep 2012)

  Changed paths:
M docs/topics/forms/modelforms.txt

  Log Message:
  ---
  Merge pull request #359 from nmartini/ticket_18832

Fixed #18832 - Updated ModelForm example fields to match note below


Compare: https://github.com/django/django/compare/b139cfc0f7e7...76bd33539f8a

-- 
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] #13614: Back button breaks many to many widget

[Django]

#13614: Back button breaks many to many widget
---+
 Reporter:  minarets   |Owner:  julien
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.3
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  1
---+

Comment (by julien):

 Quick note: the Webkit bug has been fixed:
 https://bugs.webkit.org/show_bug.cgi?id=89409
 http://trac.webkit.org/changeset/120895

 It might take a little while before it gets deployed in the public
 versions of Safari and Chrome, so some tests should still be run before we
 can close this ticket.

 @KyleMac: Thank you for your work. I'm in favour of rewriting this widget
 in jQuery, so if you're interested in working on that, you may take a look
 at ticket #15220.

-- 
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] #15730: RequestFactory Example Doesn't Address Class-Based Views

[Django]

#15730: RequestFactory Example Doesn't Address Class-Based Views
---+
 Reporter:  bryanveloso|Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Documentation  |  Version:  1.3
 Severity:  Normal |   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
---+
Changes (by Tim Graham ):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [b139cfc0f7e70e37b9a31e9931c6b03b8a68e918]:
 {{{
 #!CommitTicketReference repository=""
 revision="b139cfc0f7e70e37b9a31e9931c6b03b8a68e918"
 Fixed #15730 - Documented the as_view() method for CBVs.
 }}}

-- 
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] b139cf: Fixed #15730 - Documented the as_view() method for...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b139cfc0f7e70e37b9a31e9931c6b03b8a68e918
  
https://github.com/django/django/commit/b139cfc0f7e70e37b9a31e9931c6b03b8a68e918
  Author: Tim Graham 
  Date:   2012-09-08 (Sat, 08 Sep 2012)

  Changed paths:
M docs/ref/class-based-views/base.txt
M docs/ref/class-based-views/index.txt

  Log Message:
  ---
  Fixed #15730 - Documented the as_view() method for CBVs.



-- 
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] 86e149: Fixed a typo in the Python 3 compatibility docs.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 86e149ae055872fae0c2646cdfb002af287376d7
  
https://github.com/django/django/commit/86e149ae055872fae0c2646cdfb002af287376d7
  Author: Michal Petrucha 
  Date:   2012-09-08 (Sat, 08 Sep 2012)

  Changed paths:
M docs/topics/python3.txt

  Log Message:
  ---
  Fixed a typo in the Python 3 compatibility docs.


  Commit: 3c27344b45d6ae249c39e602556f2f7483df1403
  
https://github.com/django/django/commit/3c27344b45d6ae249c39e602556f2f7483df1403
  Author: Carl Meyer 
  Date:   2012-09-08 (Sat, 08 Sep 2012)

  Changed paths:
M docs/topics/python3.txt

  Log Message:
  ---
  Merge pull request #361 from konk/py3kdoc

Fixed a typo in the Python 3 compatibility docs.


Compare: https://github.com/django/django/compare/7207327dd313...3c27344b45d6

-- 
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] #12836: Model.get_absolute_url lose method attributes

[Django]

#12836: Model.get_absolute_url lose method attributes
-+-
 Reporter:  minmax   |Owner:  minmax
 Type:  Bug  |   Status:  reopened
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by caleb.smithnc@…):

 * needs_tests:  1 => 0


Comment:

 I added a pull request that adds the test here:
 https://github.com/django/django/pull/360
 The fix.diff at the top was already applied, but the doc test in test.diff
 isn't. I simply rewrote it as a unit test.

-- 
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] #18832: The example for excluding field from forms uses the wrong field.

[Django]

#18832: The example for excluding field from forms uses the wrong field.
---+---
 Reporter:  nedbatchelder  |Owner:  nickmartini
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.4
 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 nickmartini):

 * has_patch:  0 => 1


Comment:

 I noticed that in the example code in the docs, a non-required field
 (birth date) was excluded, and then the required 'title' field was
 manually added to the form even though it had not been excluded.  I chose
 to exclude the required field 'title' instead, leaving it manually added
 in the example.

 https://github.com/django/django/pull/359

-- 
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] #18800: Template cannot format integers bigger than maximum float

[Django]

#18800: Template cannot format integers bigger than maximum float
-+
 Reporter:  jbvsmo@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  float, long  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+
Changes (by bradpitcher):

 * cc: bradpitcher@… (added)
 * needs_better_patch:  1 => 0
 * status:  assigned => new
 * owner:  bradpitcher => nobody
 * needs_tests:  1 => 0


Comment:

 Pull request with tests here: https://github.com/django/django/pull/358

-- 
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:  Bug|   Status:  closed
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:  needsinfo
 Keywords:  timezone, tz   | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by aaugustin):

 * status:  new => closed
 * resolution:   => needsinfo


Comment:

 Waiting to know if installing pytz resolves the problem...

-- 
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] #18245: Error in documentation of date based generic views

[Django]

#18245: Error in documentation of date based generic views
---+-
 Reporter:  aaugustin  |Owner:  aaugustin
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   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
---+-
Changes (by Aymeric Augustin ):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [7207327dd313522954da167f9a41396b97354c78]:
 {{{
 #!CommitTicketReference repository=""
 revision="7207327dd313522954da167f9a41396b97354c78"
 Updated docs for dates generic views.

 Fixes #18245. Refs #3542.
 }}}

-- 
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] #3542: Allow month-based date_list on archive_index

[Django]

#3542: Allow month-based date_list on archive_index
-+-
 Reporter:  anonymous|Owner:  dtulig
 Type:  New feature  |   Status:  closed
Component:  Generic views|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  date_list month  | Triage Stage:  Accepted
  generic view   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Aymeric Augustin ):

 In [7207327dd313522954da167f9a41396b97354c78]:
 {{{
 #!CommitTicketReference repository=""
 revision="7207327dd313522954da167f9a41396b97354c78"
 Updated docs for dates generic views.

 Fixes #18245. Refs #3542.
 }}}

-- 
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] 720732: Updated docs for dates generic views.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 7207327dd313522954da167f9a41396b97354c78
  
https://github.com/django/django/commit/7207327dd313522954da167f9a41396b97354c78
  Author: Aymeric Augustin 
  Date:   2012-09-08 (Sat, 08 Sep 2012)

  Changed paths:
M django/views/generic/dates.py
M docs/ref/class-based-views/generic-date-based.txt
M docs/ref/class-based-views/mixins-date-based.txt

  Log Message:
  ---
  Updated docs for dates generic views.

Fixes #18245. Refs #3542.



-- 
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] #18054: deprecate contrib.markup

[Django]

#18054: deprecate contrib.markup
--+
 Reporter:  ptone |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  contrib.markup|  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Julien Phalip ):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [3da43c3e0ef109ffbecae528aef853879281]:
 {{{
 #!CommitTicketReference repository=""
 revision="3da43c3e0ef109ffbecae528aef853879281"
 Fixed #18054 -- Deprecated contrib.markup. Thanks to simukis for the
 initial patch.
 }}}

-- 
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] 3da43c: Fixed #18054 -- Deprecated contrib.markup. Thanks ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 3da43c3e0ef109ffbecae528aef853879281
  
https://github.com/django/django/commit/3da43c3e0ef109ffbecae528aef853879281
  Author: Preston Holmes 
  Date:   2012-09-08 (Sat, 08 Sep 2012)

  Changed paths:
M django/contrib/markup/templatetags/markup.py
M django/contrib/markup/tests.py
M docs/internals/deprecation.txt
M docs/ref/contrib/markup.txt
M docs/releases/1.5.txt

  Log Message:
  ---
  Fixed #18054 -- Deprecated contrib.markup. Thanks to simukis for the initial 
patch.



-- 
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] #18593: Admin change list swallows unrelated AttributeErrors from callable display fields

[Django]

#18593: Admin change list swallows unrelated AttributeErrors from callable 
display
fields
-+-
 Reporter:  pjdelport|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.4
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  admin, list_display  | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by aaugustin):

 Fixed in [617d077f].

-- 
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] #18747: Django admin list_display eats AttributeError by mistake

[Django]

#18747: Django admin list_display eats AttributeError by mistake
+--
 Reporter:  liu.dongyuan@…  |Owner:  tswicegood
 Type:  Bug |   Status:  closed
Component:  contrib.admin   |  Version:  1.4
 Severity:  Normal  |   Resolution:  duplicate
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+--

Comment (by aaugustin):

 Fixed in [617d077f].

-- 
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] #16655: Silent error in ModelAdmin.list_display callables...

[Django]

#16655: Silent error in ModelAdmin.list_display callables...
---+
 Reporter:  jedie  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  1.3
 Severity:  Normal |   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
---+
Changes (by aaugustin):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Fixed in [617d077f].

-- 
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] ccd1bb: Remove Admin's swallowing of AttributeError (#1665...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ccd1bb0d81381b5611fb5caf2c4ebe5927fe2095
  
https://github.com/django/django/commit/ccd1bb0d81381b5611fb5caf2c4ebe5927fe2095
  Author: Travis Swicegood 
  Date:   2012-09-08 (Sat, 08 Sep 2012)

  Changed paths:
M django/contrib/admin/templatetags/admin_list.py
M tests/regressiontests/admin_views/admin.py
M tests/regressiontests/admin_views/customadmin.py
M tests/regressiontests/admin_views/models.py
M tests/regressiontests/admin_views/tests.py

  Log Message:
  ---
  Remove Admin's swallowing of AttributeError (#16655, #18593, #18747)

During the new-admin changes, catching of AttributeError was added to
the admin.  This patch removes that as it's no longer possible to add a
value to a ModelAdmin that is not available.  Adding an attribute that
can not be called causes an ImproperlyConfigured exception to be raised.


  Commit: 617d077f1f5be6cfb67a1f4f9ab0334f3c793e4c
  
https://github.com/django/django/commit/617d077f1f5be6cfb67a1f4f9ab0334f3c793e4c
  Author: Aymeric Augustin 
  Date:   2012-09-08 (Sat, 08 Sep 2012)

  Changed paths:
M django/contrib/admin/templatetags/admin_list.py
M tests/regressiontests/admin_views/admin.py
M tests/regressiontests/admin_views/customadmin.py
M tests/regressiontests/admin_views/models.py
M tests/regressiontests/admin_views/tests.py

  Log Message:
  ---
  Merge pull request #357 from tswicegood/fix-list-attr

Removed admin's swallowing of AttributeError (#16655, #18593, #18747)


Compare: https://github.com/django/django/compare/d823bb790d3b...617d077f1f5b

-- 
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] #3542: Allow month-based date_list on archive_index

[Django]

#3542: Allow month-based date_list on archive_index
-+-
 Reporter:  anonymous|Owner:  dtulig
 Type:  New feature  |   Status:  closed
Component:  Generic views|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  date_list month  | Triage Stage:  Accepted
  generic view   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by aaugustin):

 This commit could have used more docs... I'm taking care of them now...

-- 
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] #17156: QuerySet.__contains__ needs documentation

[Django]

#17156: QuerySet.__contains__ needs documentation
--+
 Reporter:  guettli   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.3
 Severity:  Normal|   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
--+
Changes (by Tim Graham ):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [d823bb790d3b70e19e7f8bc7cfb11f3a1728a799]:
 {{{
 #!CommitTicketReference repository=""
 revision="d823bb790d3b70e19e7f8bc7cfb11f3a1728a799"
 Fixed #17156 -- Added documentation examples for exists()

 Thanks mrmagooey for the draft patch.
 }}}

-- 
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] d823bb: Fixed #17156 -- Added documentation examples for e...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: d823bb790d3b70e19e7f8bc7cfb11f3a1728a799
  
https://github.com/django/django/commit/d823bb790d3b70e19e7f8bc7cfb11f3a1728a799
  Author: Tim Graham 
  Date:   2012-09-08 (Sat, 08 Sep 2012)

  Changed paths:
M docs/ref/models/querysets.txt

  Log Message:
  ---
  Fixed #17156 -- Added documentation examples for exists()

Thanks mrmagooey for the draft patch.



-- 
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] #18800: Template cannot format integers bigger than maximum float

[Django]

#18800: Template cannot format integers bigger than maximum float
-+---
 Reporter:  jbvsmo@… |Owner:  bradpitcher
 Type:  Bug  |   Status:  assigned
Component:  Template system  |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  float, long  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+---
Changes (by bradpitcher):

 * owner:  nobody => bradpitcher
 * status:  new => assigned


-- 
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] #16023: Range query on a datetime is NOT inclusive with dates

[Django]

#16023: Range query on a datetime is NOT inclusive with dates
---+-
 Reporter:  jodym@…|Owner:  aaugustin
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:  invalid
 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 Aymeric Augustin ):

 In [e69348b4e7f07ef927edaecc7126901fc91c79d0]:
 {{{
 #!CommitTicketReference repository=""
 revision="e69348b4e7f07ef927edaecc7126901fc91c79d0"
 Avoided mixing dates and datetimes in the examples.

 Refs #16023.
 }}}

-- 
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] e69348: Avoided mixing dates and datetimes in the examples...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e69348b4e7f07ef927edaecc7126901fc91c79d0
  
https://github.com/django/django/commit/e69348b4e7f07ef927edaecc7126901fc91c79d0
  Author: Aymeric Augustin 
  Date:   2012-09-08 (Sat, 08 Sep 2012)

  Changed paths:
M docs/faq/models.txt
M docs/intro/overview.txt
M docs/ref/contrib/comments/moderation.txt
M docs/ref/models/fields.txt
M docs/ref/models/instances.txt
M docs/ref/models/querysets.txt
M docs/topics/db/examples/many_to_one.txt
M docs/topics/db/queries.txt

  Log Message:
  ---
  Avoided mixing dates and datetimes in the examples.

Refs #16023.



-- 
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] #18903: Add forms validation for GB telephone numbers.

[Django]

#18903: Add forms validation for GB telephone numbers.
-+-
 Reporter:  g1smd|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  Telephone Number | Triage Stage:
  Forms GB   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-
Changes (by bradpitcher):

 * cc: bradpitcher@… (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] #18616: New auth signal: user_login_failed

[Django]

#18616: New auth signal: user_login_failed
-+-
 Reporter:  micolous |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by bradpitcher):

 * cc: bradpitcher@… (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] #18903: Add forms validation for GB telephone numbers.

[Django]

#18903: Add forms validation for GB telephone numbers.
-+-
 Reporter:  g1smd|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  Telephone Number | Triage Stage:
  Forms GB   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-
Changes (by bradpitcher):

 * status:  assigned => new
 * needs_better_patch:  0 => 1
 * needs_tests:  1 => 0
 * owner:  bradpitcher => nobody
 * needs_docs:  1 => 0
 * has_patch:  0 => 1


Comment:

 A working patch can be found here:
 https://github.com/django/django/pull/356

 The patch still needs improvement, however the tests do pass.

 What format should `clean` return the number in? Now it is returning
 +44xxx. Should it be more like +44 xxx xxx ?

 Also, what's the best practice with long regular expressions? Really long
 single lines or multiple lines with indentation for structure?

-- 
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] #18747: Django admin list_display eats AttributeError by mistake

[Django]

#18747: Django admin list_display eats AttributeError by mistake
+--
 Reporter:  liu.dongyuan@…  |Owner:  tswicegood
 Type:  Bug |   Status:  closed
Component:  contrib.admin   |  Version:  1.4
 Severity:  Normal  |   Resolution:  duplicate
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+--
Changes (by tswicegood):

 * status:  new => closed
 * resolution:   => duplicate


Comment:

 There are actually a few older versions of this:

 * #18593
 * #16655

 Going to close as a duplicate.

-- 
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] #17156: QuerySet.__contains__ needs documentation

[Django]

#17156: QuerySet.__contains__ needs documentation
--+
 Reporter:  guettli   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.3
 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 timo):

 * has_patch:  0 => 1


Comment:

 https://github.com/django/django/pull/306

-- 
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] #16023: Range query on a datetime is NOT inclusive with dates

[Django]

#16023: Range query on a datetime is NOT inclusive with dates
---+-
 Reporter:  jodym@…|Owner:  aaugustin
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:  invalid
 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 aaugustin):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 Scrap my first comment -- `__range` translates to a SQL `BETWEEN`, which
 is inclusive.

 The real problem here is that you're mixing dates and datetimes. This is
 just asking for trouble. (It'll be even worse if you set `USE_TZ` to
 `True`.)

 If you want to use `range`, the correct idiom is:

 {{{
 start_date = datetime.date(2011, 4, 1)
 end_date = datetime.date(2011, 4, 30)
 Transaction.objects.filter(posted__range=(
 datetime.datetime.combine(start_date, datetime.time.min),
 datetime.datetime.combine(end_date, datetime.time.max),
 ))
 }}}

 I'd rather write that as:

 {{{
 start_dt = datetime.date(2011, 4, 1)
 end_dt = datetime.date(2011, 5, 1)
 Transaction.objects.filter(posted__gte=start_dt, posted__lt=end_dt)
 }}}

 Dates and datetimes aren't interchangeable. I [http://lanyrd.com/2012
 /djangocon-europe/srptc/ talked about this] a few months ago.

-- 
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] #11185: Document how to customize widgets

[Django]

#11185: Document how to customize widgets
--+
 Reporter:  bensmith  |Owner:  timo
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.0
 Severity:  Normal|   Resolution:
 Keywords:  widget| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timo):

 * needs_better_patch:  1 => 0


-- 
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] #18832: The example for excluding field from forms uses the wrong field.

[Django]

#18832: The example for excluding field from forms uses the wrong field.
---+---
 Reporter:  nedbatchelder  |Owner:  nickmartini
 Type:  Bug|   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 nickmartini):

 * owner:  nobody => nickmartini


-- 
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] #18054: deprecate contrib.markup

[Django]

#18054: deprecate contrib.markup
--+
 Reporter:  ptone |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.markup|  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by ptone):

 Here is an update to the patch

 https://github.com/ptone/django/compare/django:master...deprecate-
 markup-18054

-- 
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] #18747: Django admin list_display eats AttributeError by mistake

[Django]

#18747: Django admin list_display eats AttributeError by mistake
+--
 Reporter:  liu.dongyuan@…  |Owner:  tswicegood
 Type:  Bug |   Status:  new
Component:  contrib.admin   |  Version:  1.4
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+--
Changes (by tswicegood):

 * owner:  thikonom => tswicegood
 * needs_better_patch:  0 => 1
 * status:  assigned => new
 * needs_tests:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 Definitely something we should probably handle, though I think there's a
 better way to figure out where the exception came from.  Taking a stab at
 the patch.

-- 
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] #11185: Document how to customize widgets

[Django]

#11185: Document how to customize widgets
--+
 Reporter:  bensmith  |Owner:  timo
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.0
 Severity:  Normal|   Resolution:
 Keywords:  widget| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timo):

 * owner:  fadeev => timo
 * status:  reopened => new
 * cc: timograham@… (added)


Comment:

 I'm working on updating the patch from fadeev

-- 
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] #18767: Admin's calendar for datetime fields doesn't show right values with russian and some other locales

[Django]

#18767: Admin's calendar for datetime fields doesn't show right values with 
russian
and some other locales
---+
 Reporter:  void   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  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 tswicegood):

 * stage:  Unreviewed => Accepted


Comment:

 I was able to reproduce this.

 The issue is that the calendar should display for the month/year of the
 date that is set.  Steps to reproduce:

 * Set calendar date to February 1, 2000 (Russian date is 01.02.2000)
 * Click the calendar icon
 * Excepted behavior: Calendar is set to February 2000
 * Actual behavior: Calendar is set to whatever it last was

-- 
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] #17208: Dogfood class-based views in contrib.admin

[Django]

#17208: Dogfood class-based views in contrib.admin
-+-
 Reporter:  melinath |Owner:  julien
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  class-based views|  Needs documentation:  1
  admin  |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by tswicegood):

 * cc: travis@… (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):

 Also, I just noticed that while the templates directory is included in the
 package, it's not installed when I run `python setup.py install`.

 After some hunting, I learnt that one way to ensure the templates are
 installed is to use `packages=setuptools.find_packages()` and
 `include_package_data=True` in my setup.py file as follows:

 {{{
 from distutils.core import setup
 from setuptools import find_packages

 setup(
 name='django-polls',
 version='0.1',
 packages=find_packages(),
 license='',
 long_description=open('README.txt').read(),
 url='http://www.example.com/',
 author='Your Name',
 author_email='yourn...@example.com',
 include_package_data=True,
 )
 }}}

 Is this the approach you would recommend? I'm not very experienced with
 packaging and noticed that the install behaved differently using after
 making these changes -- the installed files ended up in
 `django_polls-0.1-py2.7.egg` and `easy-install.pth` rather than the
 previous `polls` and `django_polls-0.1.egg-info`.

-- 
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):

 Thanks for your notes Tim. Also looking forward to getting this in!

 Regarding 1: I've just run through the dev version tutorials 1-4 and
 didn't find I needed to modify `settings.TEMPLATE_DIRS`. If you have
 `'django.template.loaders.app_directories.Loader',` in your
 `settings.TEMPLATE_LOADERS` (the default), the templates should be found
 by Django when moved inside `polls/templates/polls`. Have I missed
 something?

 Regarding 2: I've added a note about the `docs` directory not being
 included if empty, thanks.

 Regarding 3: I've used the example you mentioned in comment 11 to describe
 how to find package files to delete.

-- 
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] #18911: Change or remove the example in "Outputting PDFs with Django"

[Django]

#18911: Change or remove the example in "Outputting PDFs with Django"
-+-
 Reporter:  shabda@… |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  Documentation|   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by timo):

 * status:  new => closed
 * needs_better_patch:   => 0
 * resolution:   => wontfix
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Thanks for the suggestion, but I think this is ok.

-- 
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] #15566: .update queries should affect Date*Field's with auto_now

[Django]

#15566: .update queries should affect Date*Field's with auto_now
---+
 Reporter:  jdunck |Owner:  agiliq
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.2
 Severity:  Normal |   Resolution:  fixed
 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 Tim Graham ):

 In [b0e2cb8e470acc552b4ed3fde3d5b1322b426bf2]:
 {{{
 #!CommitTicketReference repository=""
 revision="b0e2cb8e470acc552b4ed3fde3d5b1322b426bf2"
 [1.4.X] Fixed #15566 - Documented that update() doesn't honor
 DateField.auto_now

 Thanks Shabda Raaj for the draft patch.

 Backport of dc01e41d23 from master
 }}}

-- 
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] b0e2cb: [1.4.X] Fixed #15566 - Documented that update() do...

[GitHub]

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: b0e2cb8e470acc552b4ed3fde3d5b1322b426bf2
  
https://github.com/django/django/commit/b0e2cb8e470acc552b4ed3fde3d5b1322b426bf2
  Author: Tim Graham 
  Date:   2012-09-08 (Sat, 08 Sep 2012)

  Changed paths:
M docs/howto/custom-model-fields.txt
M docs/topics/db/queries.txt

  Log Message:
  ---
  [1.4.X] Fixed #15566 - Documented that update() doesn't honor 
DateField.auto_now

Thanks Shabda Raaj for the draft patch.

Backport of dc01e41d23 from master



-- 
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] #18365: remind in the "set languages redirection view" that the i18n template context processor should be set

[Django]

#18365: remind in the "set languages redirection view" that the i18n template
context processor should be set
-+-
 Reporter:  anonymous|Owner:
 Type:   |  nickmartini
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.4
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham ):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [b7d3b057f32ed6aa7ee0941e1f0dec9d3e9223a3]:
 {{{
 #!CommitTicketReference repository=""
 revision="b7d3b057f32ed6aa7ee0941e1f0dec9d3e9223a3"
 Fixed #18365 - Added a reminder of the context processor required for the
 set_language view.

 Thanks Nick Martini for the patch.
 }}}

-- 
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] b7d3b0: Fixed #18365 - Added a reminder of the context pro...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b7d3b057f32ed6aa7ee0941e1f0dec9d3e9223a3
  
https://github.com/django/django/commit/b7d3b057f32ed6aa7ee0941e1f0dec9d3e9223a3
  Author: Tim Graham 
  Date:   2012-09-08 (Sat, 08 Sep 2012)

  Changed paths:
M docs/topics/i18n/translation.txt

  Log Message:
  ---
  Fixed #18365 - Added a reminder of the context processor required for the 
set_language view.

Thanks Nick Martini for the patch.



-- 
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] #18909: QueryString with non-ascii characters under Windows (Python 2.7) may be decoded inproperly

[Django]

#18909: QueryString with non-ascii characters under Windows (Python 2.7) may be
decoded inproperly
-+--
 Reporter:  public@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (URLs)  |  Version:  1.4
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by lukeplant):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 I think this is invalid.

 If you want Django to interpret incoming data from the client as a
 specific encoding, you need to set DEFAULT_CHARSET to that encoding, or
 set request.encoding, and your project does neither. There is
 (unfortunately due to oversight in HTTP) no automatic way for Django to
 know what the encoding the client is using. Normally this works correctly
 most of the time by declaring the encoding on your web page, and the
 client (browser) then uses the same encoding when submitting GET/POST
 data.

 I think there is also confusion here about the difference between
 'Unicode' and 'UTF-16' (which is not unicode - it is the normal way that
 most Windows APIs pass unicode around, but not in Python). You seem to be
 expecting something to get automatically translated to UTF-16, which isn't
 going to happen. There is also some confusion about Python byte strings
 and Python unicode strings.

-- 
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] #18928: Redundant language in docs/README

[Django]

#18928: Redundant language in docs/README
-+-
 Reporter:  agiliq   |Owner:  agiliq
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [b036baa9902395cf913e26bcc6d5490f562e9a40]:
 {{{
 #!CommitTicketReference repository=""
 revision="b036baa9902395cf913e26bcc6d5490f562e9a40"
 Merge pull request #354 from shabda/ticket_18928

 Fixed #18928 - Tightened language in docs/README
 }}}

-- 
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] #18928: Redundant language in docs/README

[Django]

#18928: Redundant language in docs/README
-+-
 Reporter:  agiliq   |Owner:  agiliq
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Shabda Raaj ):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [8198a1923ebbf3181447b4efdc058a4d6a86d83d]:
 {{{
 #!CommitTicketReference repository=""
 revision="8198a1923ebbf3181447b4efdc058a4d6a86d83d"
 Fixed #18928. Tightened language in docs/README.
 }}}

-- 
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] 8198a1: Fixed #18928. Tightened language in docs/README.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 8198a1923ebbf3181447b4efdc058a4d6a86d83d
  
https://github.com/django/django/commit/8198a1923ebbf3181447b4efdc058a4d6a86d83d
  Author: Shabda Raaj 
  Date:   2012-09-07 (Fri, 07 Sep 2012)

  Changed paths:
M docs/README

  Log Message:
  ---
  Fixed #18928. Tightened language in docs/README.


  Commit: b036baa9902395cf913e26bcc6d5490f562e9a40
  
https://github.com/django/django/commit/b036baa9902395cf913e26bcc6d5490f562e9a40
  Author: Tim Graham 
  Date:   2012-09-08 (Sat, 08 Sep 2012)

  Changed paths:
M docs/README

  Log Message:
  ---
  Merge pull request #354 from shabda/ticket_18928

Fixed #18928 - Tightened language in docs/README


Compare: https://github.com/django/django/compare/dc01e41d2343...b036baa99023

-- 
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] #17324: Improve security docs with better CSRF explanation

[Django]

#17324: Improve security docs with better CSRF explanation
-+-
 Reporter:  PaulM|Owner:
 Type:   |  davidfischer
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.3
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Pull request was merged.

-- 
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.