Re: [Django] #18596: Documentation of JavaScriptCatalog isn't very clear (was: Documentation of javascript_catalog isn't very clear)

[Django]

#18596: Documentation of JavaScriptCatalog isn't very clear
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 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
--+
Description changed by timgraham:

Old description:

> This is the documentation part of #18394.
>
> The [https://docs.djangoproject.com/en/dev/topics/i18n/translation
> /#module-django.views.i18n documentation of javascript_catalog] should:
> a) explain what the view does
> b) explain what the packages arguments are and what restrictions apply
> c) explain how the view can be invoked
> d) exlpain the technical details (for advanced use)
>
> Currently all this information is mixed and it can be confusing.

New description:

 This is the documentation part of #18394.

 The [https://docs.djangoproject.com/en/dev/topics/i18n/translation
 /#module-django.views.i18n documentation of JavaScriptCatalog] should:
 a) explain what the view does
 b) explain what the packages arguments are and what restrictions apply
 c) explain how the view can be invoked
 d) explain the technical details (for advanced use)

 Currently all this information is mixed and it can be confusing.

--

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.c33b303f71813a9af86484e784fb6f2b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19222: Documentation for use_for_related_fields should clarify that it doesn't work for intermediate joins

[Django]

#19222: Documentation for use_for_related_fields should clarify that it doesn't
work for intermediate joins
-+-
 Reporter:  andrewbadr   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  use_for_related_fields |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * keywords:   => use_for_related_fields


--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.f1ba89b0db9c27c9e340876653f23bf1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26600: map says a queryset is not iterable

[Django]

#26600: map says a queryset is not iterable
-+-
 Reporter:  ihucos   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  queryset iterator| Triage Stage:
  map|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by shaib):

 FWIW, the original traceback (which your `verbose_map()` hides) may be
 much more informative. Guessing that you're on Python 2,  you may want to
 rewrite it as something like:

 {{{#!python
 def verbose_map(function, iterable):
 try:
 return map(function, iterable)
 except TypeError:
 e_cls, e_inst, traceback = sys.exc_info()
 raise TypeError, (
'map failed: "{}". iterable: {}, type: {}, attrs:
 {}'.
format(e_inst, iterable, type(iterable),
 dir(iterable))
   ), traceback
 }}}

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.b319bc60cfb9fb0f8bb913bbb9f256fd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21379: class AbstractUser: validators should compile re with Unicode

[Django]

#21379: class AbstractUser: validators should compile re with Unicode
-+
 Reporter:  anonymous|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.auth |  Version:  master
 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):

 * severity:  Normal => Release blocker


Comment:

 Marking as blocker, just as we don't forget to make a decision before
 releasing 1.10.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.3a41632eb810f8f78feabedc36cf7f4a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

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

[Django]

#14370: Adding support for Autocomplete in contrib.admin
-+-
 Reporter:  tyrion   |Owner:  codingjoe
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  autocomplete,| Triage Stage:  Accepted
  jquery, javascript, widgets,   |
  admin  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by haras):

 * cc: djangoproject.com@… (removed)


--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.d52dac7525f7bc0474890e36d3e8a9d7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26601: DEP5 implementation: Improved middleware

[Django]

#26601: DEP5 implementation: Improved middleware
---+-
 Reporter:  timgraham  |Owner:  timgraham
 Type:  New feature|   Status:  assigned
Component:  HTTP handling  |  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 timgraham):

 * status:  new => assigned
 * owner:  nobody => timgraham
 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/6501 PR]

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.534ccd613732231b6684889b520675e7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26601: DEP5 implementation: Improved middleware

[Django]

#26601: DEP5 implementation: Improved middleware
-+
   Reporter:  timgraham  |  Owner:  nobody
   Type:  New feature| Status:  new
  Component:  HTTP handling  |Version:  master
   Severity:  Normal |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 The existing Django "middleware" abstraction suffers from a lack of strict
 layering and balanced in/out calls to a given middleware. This DEP
 proposes an improved abstraction for wrapping the request cycle in layered
 pre-view and post-view actions.

 [https://github.com/django/deps/blob/master/draft/0005-improved-
 middleware.rst DEP]

 [https://groups.google.com/d/topic/django-
 developers/8LMJ44KAxWI/discussion django-developers discussion]

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.6ea066e86383370ba9b0eb56d027017f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26578: validate_ipv4_address (and probably other validators) accept non-ASCII digits

[Django]

#26578: validate_ipv4_address (and probably other validators) accept non-ASCII
digits
--+
 Reporter:  mdickopp  |Owner:  yakky
 Type:  Bug   |   Status:  assigned
Component:  Core (Other)  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by timgraham):

 Well, actually we're trying to simplify the regular expressions we use at
 least in some other places (e.g. #26423). Complex regular expressions are
 difficult to maintain and have resulted in recursive backtracking security
 issues.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.6c3815b07a8a03313f002f88a20abeb6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26578: validate_ipv4_address (and probably other validators) accept non-ASCII digits

[Django]

#26578: validate_ipv4_address (and probably other validators) accept non-ASCII
digits
--+
 Reporter:  mdickopp  |Owner:  yakky
 Type:  Bug   |   Status:  assigned
Component:  Core (Other)  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by the-kid89):

 I would suggest something a little more extensive for validating IP
 addresses. This will get almost all invalid IP addresses. Though it does
 still have problems with an IP address like "192.168.00.10".

 
"^(?:(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.){3}(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)$"

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.60f1b8be3b9f80bc381c5a4681464001%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26600: map says a queryset is not iterable

[Django]

#26600: map says a queryset is not iterable
-+-
 Reporter:  ihucos   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  queryset iterator| Triage Stage:
  map|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 No, I can't figure out if or where a bug might in Django based on the
 report.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.23f1db9cff141884da3932ef5aae24d0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26600: map says a queryset is not iterable

[Django]

#26600: map says a queryset is not iterable
--+
 Reporter:  ihucos|  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.8
 Severity:  Normal|   Keywords:  queryset
  |  iterator map
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 So I got a funny bug with iterators map and Django that I can not localize
 or reproduce.
 In our production server we get this sometimes, mainly for only one
 customer and it only fails on a very small percentage of all requests.

 Sorry for only chunks of information, not sure if it is enough to process
 this bug request:

 Th error message:
 {{{
 TypeError: argument 2 to map() must support iteration
 }}}

 Chunk of the code where this happens:
 {{{#!python
 if filter(
 lambda obj:
 self.pk in verbose_map(attrgetter('pk'),
obj.resources.all()) and
 obj.begins < end and obj.ends > dt,
 resource_override_qs):
 return 0
 }}}

 Trying to reconstruct resource_override_qs I come up with:
 {{{#!python
 facility = Facility.objects.\
 prefetch_related('resources',
  'opening_hours',
  'openinghour_overrides',
  'slow_hours').\
 get(pk=facility.pk)
  resource_override_qs =
 facility.facilityresourceoverride_set.prefetch_related('resources')
 }}}

 What I did was to replace map with verbose_map in our production
 environment.
 {{{#!python
 def verbose_map(function, iterable):
 try:
 return map(function, iterable)
 except TypeError, exc:
 raise TypeError('map failed: "{}". iterable: {}, type: {}, attrs:
 {}'.format(  # NOQA
 exc, iterable, type(iterable), dir(iterable)))
 }}}

 After two weeks or so the error occurred again:
 {{{#!python
 map failed: "argument 2 to map() must support iteration". iterable:
 [, , ,
 ], type: ,
 attrs: ['__and__', '__bool__', '__class__', '__deepcopy__', '__delattr__',
 '__dict__', '__doc__', '__format__', '__getattribute__', '__getitem__',
 '__getstate__', '__hash__', '__init__', '__iter__', '__len__',
 '__module__', '__new__', '__nonzero__', '__or__', '__reduce__',
 '__reduce_ex__', '__repr__', '__setattr__', '__setstate__', '__sizeof__',
 '__str__', '__subclasshook__', '__weakref__', '_add_hints', '_as_sql',
 '_batched_insert', '_clone', '_create_object_from_params', '_db',
 '_earliest_or_latest', '_extract_model_params', '_fetch_all',
 '_filter_or_exclude', '_for_write', '_has_filters', '_hints', '_insert',
 '_known_related_objects', '_merge_known_related_objects',
 '_merge_sanity_check', '_next_is_sticky', '_populate_pk_values',
 '_prefetch_done', '_prefetch_related_lookups',
 '_prefetch_related_objects', '_prepare', '_raw_delete', '_result_cache',
 '_setup_aggregate_query', '_sticky_filter', '_update', 'aggregate', 'all',
 'annotate', 'as_manager', 'bulk_create', 'complex_filter', 'count',
 'create', 'dates', 'datetimes', 'db', 'defer', 'delete', 'distinct',
 'earliest', 'exclude', 'exists', 'extra', 'filter', 'first', 'get',
 'get_or_create', 'in_bulk', 'is_compatible_query_object_type', 'iterator',
 'last', 'latest', 'model', 'none', 'only', 'order_by', 'ordered',
 'prefetch_related', 'query', 'raw', 'reverse', 'select_for_update',
 'select_related', 'update', 'update_or_create', 'using',
 'value_annotation', 'values', 'values_list']
 }}}
 As we can see map really gets an QuerySet object, that queryset object
 does reveal its content in __str__ but python's built in map says its not
 iterable nevertheless
 Alone for the customer where this happens the most that part of the code
 should be called at least a couple of times per day.

 I am going with a workaround like calling list() on the queryset before
 mapping it or so.
 But my company should be ok, to try this again with another verbose_map
 that may provide more debugging information. My efforts to reproduce this
 in our code base failed.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 

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

[Django]

#14370: Adding support for Autocomplete in contrib.admin
-+-
 Reporter:  tyrion   |Owner:  codingjoe
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  autocomplete,| Triage Stage:  Accepted
  jquery, javascript, widgets,   |
  admin  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-

Comment (by collinanderson):

 yeago: I think codingjoe is saying that his autocomplete is implemented
 differently from raw_id_fields. In his implementation, you need change
 permission on the model the you are currently editing not the related
 object. (Try it out and see if you agree.)

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.fc4301554f38304c91977be5692383ac%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24046: Consider deprecating the "escape" half of django.utils.safestring

[Django]

#24046: Consider deprecating the "escape" half of django.utils.safestring
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Utilities |  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 Tim Graham ):

 In [changeset:"bf3057d10bc1e78a8e45142a8288a733b3e908a2" bf3057d]:
 {{{
 #!CommitTicketReference repository=""
 revision="bf3057d10bc1e78a8e45142a8288a733b3e908a2"
 Refs #24046 -- Removed redundant condition in render_value_in_context()

 Calling conditional_escape() on SafeData won't change 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.8d02a0ea6738900d06ef8fdf273e7224%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26596: Document {{ csrf_input }} in Jinja2 templates

[Django]

#26596: Document {{ csrf_input }} in Jinja2 templates
---+
 Reporter:  aaugustin  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 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 timgraham):

 * stage:  Unreviewed => Accepted


--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.165e9b0b621312840304837ec05a128d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25005: DateField, DateTimeField defaults needed even when auto_now=True

[Django]

#25005: DateField, DateTimeField defaults needed even when auto_now=True
-+-
 Reporter:  monobotsoft  |Owner:  yakky
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  DateField,   | Triage Stage:  Accepted
  DateTimeField, TimeField   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"49c57f8565d4b655de5161d299a053eddfc00bf2" 49c57f85]:
 {{{
 #!CommitTicketReference repository=""
 revision="49c57f8565d4b655de5161d299a053eddfc00bf2"
 Fixed #25005 -- Made date and time fields with auto_now/auto_now_add use
 effective default.

 Thanks to Andriy Sokolovskiy for 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.d7057fc0abc327fb5b647edec96a0116%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26596: Document {{ csrf_input }} in Jinja2 templates

[Django]

#26596: Document {{ csrf_input }} in Jinja2 templates
---+--
 Reporter:  aaugustin  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--

Comment (by aaugustin):

 I saw that mention but I don't think it's sufficiently explicit about how
 to use that variable.

 We should say that:

 - {% csrf_token %} in Django templates translates to {{ csrf_input }} in
 Jinja2 templates
 - {{ csrf_token }} works identically in Django templates and in Jinja2
 templates

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.48383b4424c7798e00f88bedef65844d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26596: Document {{ csrf_input }} in Jinja2 templates

[Django]

#26596: Document {{ csrf_input }} in Jinja2 templates
---+--
 Reporter:  aaugustin  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--

Comment (by timgraham):

 There's a mention in the
 
[https://docs.djangoproject.com/en/dev/topics/templates/#django.template.backends.jinja2.Jinja2
 Jinja2 backend] docs. Did you miss it or have another place in mind?

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.6a23588c7d273ac619976ae833f6522b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #18394: Add warning for invalid JavaScriptCatalog 'packages' (was: Better docs, and possibly better handling, for 'packages' argument to javascript_catalog)

[Django]

#18394: Add warning for invalid JavaScriptCatalog 'packages'
--+
 Reporter:  ubernostrum   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Internationalization  |  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 timgraham):

 * cc: claudep (removed)
 * type:  Bug => Cleanup/optimization


--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.991c33bffde132a420f8020ac4d400b9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26599: Django Passsword Change Form giving wrong POST value for Old Password of Admin

[Django]

#26599: Django Passsword Change Form giving wrong POST value for Old Password of
Admin
-+-
 Reporter:  shikha-desai |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.8
 Severity:  Normal   |   Resolution:
 |  worksforme
 Keywords:  Admin:Password   | Triage Stage:
  Change Form|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 Please provide a test case for Django's test suite that demonstrates the
 problem (see the existing tests in `tests/auth_tests/test_views.py`) or
 very specific steps with the exact URLs and inputs for each step. Also be
 sure to disable any third-party apps to rule out a bug there.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.8d1806e4d13d45a0c54aef427e0c29ff%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26142: Provide a way for model formsets to disallow new object creation

[Django]

#26142: Provide a way for model formsets to disallow new object creation
-+
 Reporter:  timgraham|Owner:  Mortal
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by timgraham):

 Yes, I think it's that sending data that references pks that don't appear
 in the queryset creates new objects for that data.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.eb4d1ed770d3bfb3f7232e2280a00b66%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26599: Django Passsword Change Form giving wrong POST value for Old Password of Admin

[Django]

#26599: Django Passsword Change Form giving wrong POST value for Old Password of
Admin
-+
 Reporter:  shikha-desai |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Template system  |Version:  1.8
 Severity:  Normal   |   Keywords:  Admin:Password Change Form
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 I have created a link to the Password Change Form using :

 {% trans 'Change password'
 %}

 The problem is : It works for all web users, but if I login as admin and
 then change the password, say if the original password is:'admin'...Now I
 change it to '1234', it works and I can login again.

 But when I again go to change_password and try to change from '1234' to
 something else, it gives 'Incorrect Old Password'.

 On debugging, I found that the POST request received has the old_password
 field value as 'admin' while I have typed '1234'.

 When I tried to add another field on the html page and updated the
 old_password section as below:
 {{{
 
 
 {{ form.old_password.label_tag }}
 
 
 {% dab_field_rendering form.old_password %}
 {{ form.old_password }}
 {% if form.old_password.errors %}{{
 form.old_password.errors|striptags }}{% endif %}
 
 
 }}}

 It works perfectly fine and receives the correct request, but I can't ask
 user to enter the old password two times. There seems to be a problem with
 the code of change password.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/055.6be11cd1b5244ef6ed57f4ee72d9e4b4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #18394: Better docs, and possibly better handling, for 'packages' argument to javascript_catalog

[Django]

#18394: Better docs, and possibly better handling, for 'packages' argument to
javascript_catalog
--+
 Reporter:  ubernostrum   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Internationalization  |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by claudep):

 Yes, this is still relevant (now in `JavaScriptCatalog.get_paths` method).

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.6d52c726ad494c2029d9ea3122e7ca58%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26597: Optparse incorrect relationship between `noinput` and `interactive` in management command

[Django]

#26597: Optparse incorrect relationship between `noinput` and `interactive` in
management command
-+-
 Reporter:  JBKahn   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  migrate argparse | Triage Stage:
  command|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by claudep):

 Could you please give us an example of a `call_command` you wrote and
 where the `interactive` variable was reversed?

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.1ba2c3457fe521479b7f91e13a178354%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26598: {{ }} is not getting parsed by pyjade as expected with django

[Django]

#26598: {{ }} is not getting parsed by pyjade as expected with django
-+--
 Reporter:  himanshu0511 |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.9
 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 aaugustin):

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


Comment:

 I believe you're using pyjade, a third-party project, incorrectly.

 There's no evidence of a bug in Django here.

 Please see TicketClosingReasons/UseSupportChannels.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.475bad33afb7c4d4bf9c73716b4f7641%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.