Re: [Django] #14400: Latvian localflavor

[Django]

#14400: Latvian localflavor
-+-
   Reporter:  krikulis   |Owner:  nobody
   Type: |   Status:  new
  Uncategorized  |Component:  contrib.localflavor
  Milestone: | Severity:  Normal
Version:  SVN| Keywords:
 Resolution: |Has patch:  1
   Triage Stage:  Accepted   |  Needs tests:  0
Needs documentation:  0  |
Patch needs improvement:  1  |
-+-
Changes (by julien):

 * needs_better_patch:  0 => 1
 * type:   => Uncategorized
 * severity:   => Normal


Comment:

 The patch does not apply any more. The structure of locaflavor tests has
 changed recently, so the patch now needs to be updated. Other than that
 everything looks good.

-- 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #14273: Development server does not shutdown cleanly

[Django]

#14273: Development server does not shutdown cleanly
-+-
   Reporter:  rmboggs|Owner:  nobody
   Type: |   Status:  reopened
  Cleanup/optimization   |Component:  Core (Other)
  Milestone: | Severity:  Normal
Version:  1.2| Keywords:  runserver
 Resolution: |Has patch:  1
   Triage Stage:  Accepted   |  Needs tests:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-

Comment (by julien):

 I think the attached patch is a bit better. Could you test it under
 OpenBSD?

-- 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15816: Typo in utils reference doc

[Django]

#15816: Typo in utils reference doc
-+-
   Reporter:  julien |Owner:  nobody
   Type: |   Status:  new
  Cleanup/optimization   |Component:  Documentation
  Milestone: | Severity:  Normal
Version:  1.2| Keywords:
 Resolution: |Has patch:  1
   Triage Stage: |  Needs tests:  0
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-

Comment (by julien):

 One objection to this change might be that there currently only is one
 data structure that is documented (SortedDict).

-- 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #15816: Typo in utils reference doc

[Django]

#15816: Typo in utils reference doc
-+-
   Reporter:  julien |Owner:  nobody
   Type:  Cleanup/optimization   |   Status:  new
  Milestone: |Component:
Version:  1.2|  Documentation
   Keywords: | Severity:  Normal
  Has patch:  1  | Triage Stage:
Needs tests:  0  |  Unreviewed
 |  Needs documentation:  0
 |  Patch needs improvement:  0
-+-
 See patch attached.

-- 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #14608: Adding a INPhoneNumberField to indian localflavor

[Django]

#14608: Adding a INPhoneNumberField to indian localflavor
---+---
   Reporter:  lawgon   |Owner:  lawgon
   Type:  New feature  |   Status:  reopened
  Milestone:   |Component:  contrib.localflavor
Version:  SVN  | Severity:  Normal
 Resolution:   | Keywords:  india phone
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  1|
---+---

Comment (by julien):

 Thanks for the update. By the way, feel free to add your name to the
 AUTHORS file, if only in memory of this epic 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15812: SortedDict.update() should accept tuples or generators

[Django]

#15812: SortedDict.update() should accept tuples or generators
---+
   Reporter:  slinkp   |Owner:  nobody
   Type:  New feature  |   Status:  new
  Milestone:   |Component:  Core (Other)
Version:  SVN  | Severity:  Normal
 Resolution:   | Keywords:
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  1|  Needs tests:  0
Patch needs improvement:  0|
---+
Changes (by julien):

 * needs_docs:   => 1
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 I think that makes sense. Perhaps the docs could be improved too, giving
 more examples about the various possibilities:
 
http://docs.djangoproject.com/en/dev/ref/utils/#django.utils.datastructures.SortedDict

-- 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15813: STATES_NORMALIZED dict for India does not include all states

[Django]

#15813: STATES_NORMALIZED dict for India does not include all states
-+-
   Reporter:  jsdalton   |Owner:  nobody
   Type: |   Status:  new
  Cleanup/optimization   |Component:  contrib.localflavor
  Milestone:  1.4| Severity:  Normal
Version:  SVN| Keywords:
 Resolution: |Has patch:  1
   Triage Stage:  Accepted   |  Needs tests:  1
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by julien):

 * needs_docs:   => 0
 * needs_better_patch:   => 0
 * has_patch:  0 => 1
 * needs_tests:   => 1
 * stage:  Unreviewed => Accepted


Comment:

 I see no reason why we shouldn't allow this. Every country is different,
 which is why we have the localflavors in place. Your patch looks good,
 although you need to add tests before it can be checked in. I see there
 already is some documentation for this feature so no needs to add more.

-- 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15810: Easy rename of apps in admin

[Django]

#15810: Easy rename of apps in admin
-+-
   Reporter: |Owner:  nobody
  aatanasov+django@… |   Status:  closed
   Type:  New|Component:  contrib.admin
  feature| Severity:  Normal
  Milestone: | Keywords:  app_label, admin
Version:  SVN|Has patch:  1
 Resolution:  duplicate  |  Needs tests:  0
   Triage Stage: |
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-

Comment (by russellm):

 I should also add -- #3591 was the subject of a Google Summer of Code
 project last year, and there's lots of interest in getting that work
 integrated into trunk in the 1.4 timeframe.

-- 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15810: Easy rename of apps in admin

[Django]

#15810: Easy rename of apps in admin
-+-
   Reporter: |Owner:  nobody
  aatanasov+django@… |   Status:  closed
   Type:  New|Component:  contrib.admin
  feature| Severity:  Normal
  Milestone: | Keywords:  app_label, admin
Version:  SVN|Has patch:  1
 Resolution:  duplicate  |  Needs tests:  0
   Triage Stage: |
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by russellm):

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


Comment:

 Closing as a duplicate of #3591. The bigger issue here is app
 configuration; renaming the app in the admin is just one part of a bigger
 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15815: Support memcached binary protocol in PyLibMCCache

[Django]

#15815: Support memcached binary protocol in PyLibMCCache
---+---
   Reporter:  mtigas   |Owner:  nobody
   Type:  New feature  |   Status:  new
  Milestone:   |Component:  Core (Cache system)
Version:  1.3  | Severity:  Normal
 Resolution:   | Keywords:
   Triage Stage:  Unreviewed   |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  0|
---+---
Changes (by mtigas):

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


Comment:

 Not sure if patch is in the proper format; have also opened a github pull
 request, tracking this bug. [https://github.com/django/django/pull/21]

 Looked into updating the docs, however the documentation appears to leave
 out implementation-specific details of the different memcached backends.
 Please let me know if I’m mistaken.

-- 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #15815: Support memcached binary protocol in PyLibMCCache

[Django]

#15815: Support memcached binary protocol in PyLibMCCache
-+
 Reporter:  mtigas   | Owner:  nobody
 Type:  New feature  |Status:  new
Milestone:   | Component:  Core (Cache system)
  Version:  1.3  |  Severity:  Normal
 Keywords:   |  Triage Stage:  Unreviewed
Has patch:  1|
-+
 As per [http://sendapatch.se/projects/pylibmc/#example-usage] , enabling
 the binary protocol requires the `binary=True` argument to be passed into
 pylibmc.Client when it is initialized.

 The binary protocol is available in Memcached 1.3+ and provides a
 performance boost in high-load circumstances:
 [http://www.slideshare.net/tmaesaka/memcached-binary-protocol-in-a
 -nutshell-presentation]

 pylibmc ignores any unknown options passed into Client.behaviors (see
 below), so putting this in `OPTIONS` seems like the way to go.

 {{{
 >>> import pylibmc
 >>> a=pylibmc.Client(['127.0.0.1:55838',])
 >>> print a.behaviors
 {'cas': 0, 'no_block': 0, 'receive_timeout': 0, 'send_timeout': 0,
 'ketama_hash': 0, '_poll_timeout': 5000, '_io_bytes_watermark': 66560,
 'cache_lookups': 0, '_sort_hosts': 0, '_io_key_prefetch': 0,
 '_auto_eject_hosts': 0, 'ketama': 0, 'ketama_weighted': 0,
 '_io_msg_watermark': 500, '_hash_with_prefix_key': 0, 'tcp_nodelay': 0,
 'failure_limit': 0, 'buffer_requests': 0, '_socket_send_size': 0,
 '_retry_timeout': 0, '_noreply': 0, '_socket_recv_size': 0,
 '_number_of_replicas': 0, 'distribution': 'modula', 'connect_timeout':
 4000, 'hash': 'default', 'verify_keys': 0}

 >>> a.behaviors = {"binary":True} # should be ignored by pylibmc
 >>> print a.behaviors
 {'cas': 0, 'no_block': 0, 'receive_timeout': 0, 'send_timeout': 0,
 'ketama_hash': 0, '_poll_timeout': 5000, '_io_bytes_watermark': 66560,
 'cache_lookups': 0, '_sort_hosts': 0, '_io_key_prefetch': 0,
 '_auto_eject_hosts': 0, 'ketama': 0, 'ketama_weighted': 0,
 '_io_msg_watermark': 500, '_hash_with_prefix_key': 0, 'tcp_nodelay': 0,
 'failure_limit': 0, 'buffer_requests': 0, '_socket_send_size': 0,
 '_retry_timeout': 0, '_noreply': 0, '_socket_recv_size': 0,
 '_number_of_replicas': 0, 'distribution': 'modula', 'connect_timeout':
 4000, 'hash': 'default', 'verify_keys': 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15814: Add a test util to abstract the process of using a test template loader

[Django]

#15814: Add a test util to abstract the process of using a test template loader
-+-
   Reporter: |Owner:  SmileyChris
  SmileyChris|   Status:  assigned
   Type: |Component:  Testing framework
  Cleanup/optimization   | Severity:  Normal
  Milestone: | Keywords:
Version: |Has patch:  1
 Resolution: |  Needs tests:  0
   Triage Stage:  Accepted   |
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-

Comment (by SmileyChris):

 This ticket came out of
 [http://code.djangoproject.com/ticket/15721#comment:8 the discussion] in
 #15721.

-- 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15721: {% include %} and RequestContext fails since r15795

[Django]

#15721: {% include %} and RequestContext fails since r15795
+---
   Reporter:  mk|Owner:  SmileyChris
   Type:  Bug   |   Status:  assigned
  Milestone:|Component:  Template system
Version:  1.3   | Severity:  Release blocker
 Resolution:| Keywords:
   Triage Stage:  Accepted  |Has patch:  1
Needs documentation:  0 |  Needs tests:  0
Patch needs improvement:  1 |
+---

Comment (by SmileyChris):

 See #15814 for the separation of the util. A review of that would be
 appreciated.

-- 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15814: Add a test util to abstract the process of using a test template loader

[Django]

#15814: Add a test util to abstract the process of using a test template loader
-+-
   Reporter: |Owner:  SmileyChris
  SmileyChris|   Status:  assigned
   Type: |Component:  Testing framework
  Cleanup/optimization   | Severity:  Normal
  Milestone: | Keywords:
Version: |Has patch:  1
 Resolution: |  Needs tests:  0
   Triage Stage:  Accepted   |
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by SmileyChris):

 * status:  new => assigned
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * owner:  nobody => SmileyChris
 * needs_docs:   => 0
 * has_patch:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 https://github.com/SmileyChris/django/compare/master...test-util-template-
 loader

-- 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #15814: Add a test util to abstract the process of using a test template loader

[Django]

#15814: Add a test util to abstract the process of using a test template loader
--+--
 Reporter:  SmileyChris   | Owner:  nobody
 Type:  Cleanup/optimization  |Status:  new
Milestone:| Component:  Testing framework
  Version:|  Severity:  Normal
 Keywords:|  Triage Stage:  Unreviewed
Has patch:  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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #7267: clean_html() bug

[Django]

#7267: clean_html() bug
-+-
   Reporter:  Nikolay|Owner:  nobody
    |   Status:  new
   Type:  Bug|Component:  Core (Other)
  Milestone: | Severity:  Normal
Version:  SVN| Keywords:  html
 Resolution: |Has patch:  1
   Triage Stage:  Accepted   |  Needs tests:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by aaugustin):

 * cc: aymeric.augustin@… (added)
 * needs_tests:  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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12890: extra() tables included twice do not generate aliases

[Django]

#12890: extra() tables included twice do not generate aliases
-+-
   Reporter:  semenov|Owner:  nobody
   Type:  Bug|   Status:  new
  Milestone: |Component:  Database layer
Version:  1.1|  (models, ORM)
 Resolution: | Severity:  Normal
   Triage Stage:  Accepted   | Keywords:
Needs documentation:  0  |Has patch:  0
Patch needs improvement:  0  |  Needs tests:  0
-+-

Comment (by daveycrockett):

 I see some fairly slow activity (15 months!) on this ticket and have
 a...vested interest in seeing it resolved, all of a sudden.  The current
 chain of conversation is exactly what I'm trying to implement...the
 behavior of extra() currently *contradicts* the documented behavior for
 the tables parameter.  I'm working to test the above patch further, but
 just wanted to post my results immediately; it meets my use-cases and
 doesn't break existing functionality.

 This seems especially useful when doing fun things with django-mptt, self-
 joins of mptt models are useful for aggregating over a particular level of
 a tree (just as a completely hypothetical example, ahem).

-- 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #15813: STATES_NORMALIZED dict for India does not include all states

[Django]

#15813: STATES_NORMALIZED dict for India does not include all states
--+
 Reporter:  jsdalton  | Owner:  nobody
 Type:  Cleanup/optimization  |Status:  new
Milestone:  1.4   | Component:  contrib.localflavor
  Version:  SVN   |  Severity:  Normal
 Keywords:|  Triage Stage:  Unreviewed
Has patch:  0 |
--+
 I got bit today by an inconsitency in the implementation of the
 STATES_NORMALIZED dictionary for India as compared with the U.S. and
 Canada. (These are the only three countries which offer this dictionary.

 My assumption is that the purpose of this dictionary is to help normalize
 user input to the correct two letter state abbreviation. For both the U.S.
 and Canada, this dictionary maps every two-letter abbreviation to the
 normalized version (e.g.. "bc" -> "BC"), every complete spelling to the
 normalized version (e.g. "british columbia" -> "BC") and common
 misspellings or abbreviations to the normalized version (e.g. "calif" ->
 "CA"). Makes sense.

 The STATES_NORMALIZED dict in India does not do this though. It *only*
 maps a handful of abbreviations and misspellings, but does not
 comprehensively map each two letter abbreviation and each state.

 I implemented some logic that assumed it worked like the U.S. and Canada
 and got a complaint from a user registering from Gujarat who could not do
 so, because no mapping is included for it. Yikes!

 I humbly propose we extend STATES_NORMALIZED for India with all two letter
 abbreviations and spelled out state names. If there is a reason not to do
 this, I'd like to hear it. Otherwise, my patch is attached.

-- 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #11595: Fixture validation errors should report their data

[Django]

#11595: Fixture validation errors should report their data
-+-
   Reporter:  freyley|Owner:  raulcd
   Type: |   Status:  assigned
  Cleanup/optimization   |Component:  Core (Serialization)
  Milestone: | Severity:  Normal
Version:  1.0| Keywords:  easy-pickings
 Resolution: |Has patch:  1
   Triage Stage:  Accepted   |  Needs tests:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by raulcd):

 * needs_tests:  1 => 0


Comment:

 I finally added tests to a new file. It would be better, as someone in the
 IRC told me, to move them if you think they fit better in another
 location. (tests/modeltests/validation/test_error_messages.py is the new
 test file).

 As you told me I will not set the ready for chekin, just wait comments. I
 removed the need tests checkbox (I don't know if I had to do it or someone
 who review the patch has to do 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #15812: SortedDict.update() should accept tuples or generators

[Django]

#15812: SortedDict.update() should accept tuples or generators
-+-
 Reporter:  slinkp   | Owner:  nobody
 Type:  New feature  |Status:  new
Milestone:   | Component:  Core (Other)
  Version:  SVN  |  Severity:  Normal
 Keywords:   |  Triage Stage:  Unreviewed
Has patch:  1|
-+-
 dict.update() accepts dictionaries, tuples of pairs, lists of pairs, or
 any generator of pairs.
 But SortedDict.update() only accepts dicts.

 This patch fixes that. With 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12238: ModelAdmin ignores dynamic fields of ModelForm

[Django]

#12238: ModelAdmin ignores dynamic fields of ModelForm
-+-
   Reporter:  anonymous  |Owner:  nobody
   Type:  Bug|   Status:  new
  Milestone: |Component:  contrib.admin
Version:  1.1| Severity:  Normal
 Resolution: | Keywords:  modelform modeladmin
   Triage Stage:  Accepted   |  dynamic field
Needs documentation:  0  |Has patch:  1
Patch needs improvement:  0  |  Needs tests:  1
-+-

Comment (by anonymous):

 @anonymous 6.Update ModelForm's Meta.fields to include "xyz" - howto? my
 Meta has no attr 'fields' while runtime in __init__
 I have the same problem - trying to add dynamic field to ModelForm

-- 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12909: Exceptions raised in response middleware don't invoke site 500/404 handlers.

[Django]

#12909: Exceptions raised in response middleware don't invoke site 500/404
handlers.
+
   Reporter:  jhovanny  |Owner:  nobody
   Type:  Bug   |   Status:  new
  Milestone:|Component:  Core (Other)
Version:  1.2-beta  | Severity:  Normal
 Resolution:| Keywords:
   Triage Stage:  Accepted  |Has patch:  1
Needs documentation:  0 |  Needs tests:  0
Patch needs improvement:  0 |
+
Changes (by gwilson):

 * cc: gary.wilson@… (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 this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #15811: Lazy doesn't take into account methods defined in parents

[Django]

#15811: Lazy doesn't take into account methods defined in parents
---+--
 Reporter:  abki   | Owner:  nobody
 Type:  Uncategorized  |Status:  new
Milestone: | Component:  Uncategorized
  Version:  1.2|  Severity:  Normal
 Keywords: |  Triage Stage:  Unreviewed
Has patch:  0  |
---+--
 Example:

 {{{
 from django.utils.datastructures import SortedDict
 from django.utils.functional import lazy

 def a(): return SortedDict([(2,2),(1,1)])

 f = lazy(a, SortedDict)()
 f[1]

 }}}

 This results in a TypeError

 I got a patch ready but not sure if it does what it should do well since I
 don't grasp all the ``lazy`` functionality.

-- 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #15810: Easy rename of apps in admin

[Django]

#15810: Easy rename of apps in admin
+--
 Reporter:  aatanasov+django@…  | Owner:  nobody
 Type:  New feature |Status:  new
Milestone:  | Component:  contrib.admin
  Version:  SVN |  Severity:  Normal
 Keywords:  app_label, admin|  Triage Stage:  Unreviewed
Has patch:  1   |
+--
 usage:
 {{{
 from django.contrib.admin.util import AppLabel
 class Meta:
 app_label = AppLabel('app_label','Title in admin')


 }}}

-- 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15809: Add optional obj parameter to ModelAdmin.has_add_permission

[Django]

#15809: Add optional obj parameter to ModelAdmin.has_add_permission
---+-
   Reporter:  EnTeQuAk |Owner:  nobody
   Type:  New feature  |   Status:  closed
  Milestone:   |Component:  contrib.admin
Version:  1.3  | Severity:  Normal
 Resolution:  invalid  | Keywords:
   Triage Stage:  Unreviewed   |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  0|
---+-
Changes (by EnTeQuAk):

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


Comment:

 damnit, just ignore it... I was wrong about the usage of that function.

-- 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #15809: Add optional obj parameter to ModelAdmin.has_add_permission

[Django]

#15809: Add optional obj parameter to ModelAdmin.has_add_permission
-+--
 Reporter:  EnTeQuAk | Owner:  nobody
 Type:  New feature  |Status:  new
Milestone:   | Component:  contrib.admin
  Version:  1.3  |  Severity:  Normal
 Keywords:   |  Triage Stage:  Unreviewed
Has patch:  1|
-+--
 If one is to overwrite has_add_permission it may sometimes help to rely on
 an optional object parameter that is applied.  For example it's required
 to properly check if one can add some new inline-objects on an parent
 object that can has a state "editable" or "not editable".

 The patch is very simple and does not change any behavior.

-- 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #15808: CSRF token cookie does not utilize the "Secure" or "HttpOnly" flag

[Django]

#15808: CSRF token cookie does not utilize the "Secure" or "HttpOnly" flag
--+-
 Reporter:  Samuel.Lavitt@…   | Owner:  nobody
 Type:  Bug   |Status:  new
Milestone:| Component:  contrib.csrf
  Version:  1.3   |  Severity:  Normal
 Keywords:  CSRF Secure HttpOnly  |  Triage Stage:  Unreviewed
Has patch:  0 |
--+-
 I have observed that the CSRF token will not utilize the Secure or
 HttpOnly flags, even when the django is configured to protect session
 cookies using them.  I would personally consider the lack of these flags a
 bug, as it could result in disclosure of the token value to an attacker,
 which would then allow them to preform CSRF attacks which would otherwise
 be prevented.

 Because of the nature of the CSRF protection, I feel that having, at a
 minimum, the ability to configure the Secure flag should be included, and
 possibly a default setting, I understand that jquery and javascript may
 have need to access the token for submission of data, so HttpOnly as a
 default may not work in many environments.

-- 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #3591: add support for custom app_label and verbose_name

[Django]

#3591: add support for custom app_label and verbose_name
-+
   Reporter:  jkocherhans|Owner:  adrian
   Type:  New feature|   Status:  reopened
  Milestone:  1.4|Component:  Core (Other)
Version:  SVN| Severity:  Normal
 Resolution: | Keywords:
   Triage Stage:  Fixed on a branch  |Has patch:  1
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+
Changes (by mgventura):

 * cc: mgventura (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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15807: order by 'pk' alias doesn't work with inherited models when parent has an ordering set (was: 'pk' alias doesn't work with inherited models when parent has an ordering set)

[Django]

#15807: order by 'pk' alias doesn't work with inherited models when parent has 
an
ordering set
-+-
   Reporter:  mat|Owner:  nobody
   Type:  Bug|   Status:  new
  Milestone: |Component:  Database layer
Version:  SVN|  (models, ORM)
 Resolution: | Severity:  Normal
   Triage Stage: | Keywords:
  Unreviewed |Has patch:  0
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+-
Changes (by mat):

 * needs_better_patch:   => 0
 * 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #15807: 'pk' alias doesn't work with inherited models when parent has an ordering set

[Django]

#15807: 'pk' alias doesn't work with inherited models when parent has an 
ordering
set
-+-
 Reporter:  mat  | Owner:  nobody
 Type:  Bug  |Status:  new
Milestone:   | Component:  Database layer (models, ORM)
  Version:  SVN  |  Severity:  Normal
 Keywords:   |  Triage Stage:  Unreviewed
Has patch:  0|
-+-
 Consider the following models:

 {{{
 #!python
 from django.db import models

 class Foo(models.Model):
 bar = models.PositiveSmallIntegerField(default=1)
 class Meta:
 ordering = ['bar']

 class Child(Foo):
 barchild = models.PositiveSmallIntegerField(default=1)
 }}}

 Trying to get the Child objects, ordering by 'id', works:
 {{{
 >>> str(Child.objects.order_by('id').query)
 'SELECT "test_pk_foo"."id", "test_pk_foo"."bar",
 "test_pk_child"."foo_ptr_id", "test_pk_child"."barchild" FROM
 "test_pk_child" INNER JOIN #"test_pk_foo" ON ("test_pk_child"."foo_ptr_id"
 = "test_pk_foo"."id") ORDER BY "test_pk_child"."foo_ptr_id" ASC'
 }}}

 However, trying to order by 'pk' doesn't (see the `ORDER BY` clause):
 {{{
 >>> str(Child.objects.order_by('pk').query)
 'SELECT "test_pk_foo"."id", "test_pk_foo"."bar",
 "test_pk_child"."foo_ptr_id", "test_pk_child"."barchild" FROM
 "test_pk_child" INNER JOIN #"test_pk_foo" ON ("test_pk_child"."foo_ptr_id"
 = "test_pk_foo"."id") ORDER BY "test_pk_foo"."bar" ASC'
 }}}

 The default ordering from the parent is used instead! Removing the
 `ordering` property or using `id` instead of `pk` works, but I expected
 `pk` to work.

 I reproduced this with django 1.2, 1.3 and trunk, with sqlite and
 postgresql_psycopg2 backends.

-- 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15805: assertFieldOutput should not use assertRaisesRegexp

[Django]

#15805: assertFieldOutput should not use assertRaisesRegexp
--+-
   Reporter:  julien  |Owner:  nobody
   Type:  Bug |   Status:  new
  Milestone:  |Component:  Testing framework
Version:  1.2 | Severity:  Release blocker
 Resolution:  | Keywords:
   Triage Stage:  Unreviewed  |Has patch:  1
Needs documentation:  0   |  Needs tests:  0
Patch needs improvement:  0   |
--+-
Changes (by lawgon):

 * cc: lawgon@… (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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #14370: Adding support for Autocomplete in contrib.admin

[Django]

#14370: Adding support for Autocomplete in contrib.admin
-+-
   Reporter:  tyrion |Owner:  nobody
   Type:  Uncategorized  |   Status:  new
  Milestone: |Component:  contrib.admin
Version:  1.2| Severity:  Normal
 Resolution: | Keywords:  autocomplete
   Triage Stage:  Accepted   |Has patch:  1
Needs documentation:  1  |  Needs tests:  0
Patch needs improvement:  0  |
-+-
Changes (by PF_tschwaerzl):

 * cc: thomas.schwaerzl@… (added)
 * type:   => Uncategorized
 * severity:   => Normal


-- 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15805: assertFieldOutput should not use assertRaisesRegexp

[Django]

#15805: assertFieldOutput should not use assertRaisesRegexp
--+-
   Reporter:  julien  |Owner:  nobody
   Type:  Bug |   Status:  new
  Milestone:  |Component:  Testing framework
Version:  1.2 | Severity:  Release blocker
 Resolution:  | Keywords:
   Triage Stage:  Unreviewed  |Has patch:  1
Needs documentation:  0   |  Needs tests:  0
Patch needs improvement:  0   |
--+-
Changes (by julien):

 * needs_tests:  1 => 0


Comment:

 I've added the regression tests. I think the `assertFieldOutput` is
 actually quite useful. Also it's quite generic and not really local flavor
 specific. So I'd suggest we eventually move it to the
 `django.utils.unittest.TestCase` class and document it so that the world
 knows about it. I'll create a new ticket for that if/when this patch gets
 checked in.

-- 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15805: assertFieldOutput should not use assertRaisesRegexp

[Django]

#15805: assertFieldOutput should not use assertRaisesRegexp
--+-
   Reporter:  julien  |Owner:  nobody
   Type:  Bug |   Status:  new
  Milestone:  |Component:  Testing framework
Version:  1.2 | Severity:  Release blocker
 Resolution:  | Keywords:
   Triage Stage:  Unreviewed  |Has patch:  1
Needs documentation:  0   |  Needs tests:  1
Patch needs improvement:  0   |
--+-
Changes (by julien):

 * needs_tests:  0 => 1


Comment:

 This actually needs some regression tests for `assertFieldOutput` itself.
 I'm working on 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #15806: Error in filebased cache culling

[Django]

#15806: Error in filebased cache culling
-+
 Reporter:  witek@…  | Owner:  nobody
 Type:  Bug  |Status:  new
Milestone:   | Component:  Core (Cache system)
  Version:  1.3  |  Severity:  Normal
 Keywords:   |  Triage Stage:  Unreviewed
Has patch:  0|
-+
 In line 115 of filebased.py we have:

 {{{
 try:
 filelist = sorted(os.listdir(self._dir))
 except (IOError, OSError):
 return

 if self._cull_frequency == 0:
 doomed = filelist
 else:
 doomed = [os.path.join(self._dir, k) for (i, k) in enumerate(filelist)
 if i % self._cull_frequency == 0]

 }}}

 In case of _cull_frequency == 0 instead of "doomed = filelist" we should
 have sth like:

 {{{
 doomed = [os.path.join(self._dir, d) for d in filelist]
 }}}

 Otherwise doomed tuple will not contains absolute paths but relative.

-- 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #14608: Adding a INPhoneNumberField to indian localflavor

[Django]

#14608: Adding a INPhoneNumberField to indian localflavor
---+---
   Reporter:  lawgon   |Owner:  lawgon
   Type:  New feature  |   Status:  reopened
  Milestone:   |Component:  contrib.localflavor
Version:  SVN  | Severity:  Normal
 Resolution:   | Keywords:  india phone
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  1|
---+---

Comment (by lawgon):

 found a typo in my patch. Attached a fresh 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 this group at 
http://groups.google.com/group/django-updates?hl=en.