date:20150308

Re: [Django] #24201: order_with_respect_to GenericForeignKey

2015-03-08 Thread Django

Comment (by AlexHill):

Hey Tim, thanks for reviewing this!

I've just rebased against current master and it now will merge cleanly.
However, the code uses `add_lazy_relation`, which will be deprecated as
soon as #24215 is merged, so I would prefer to wait until that happens and
then update this patch to use the new API.

#24215 has been thoroughly reviewed by Aymeric, Carl and others and is, I
think, ready to be merged pending approval of
https://github.com/django/django/pull/4122. I would be very grateful if
you could have a look over it.

Cheers,
Alex

--
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.c9034d18dd4014da092b47fab5e4138b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24215: Refactor of lazy model operations

2015-03-08 Thread Django

#24215: Refactor of lazy model operations
-+-
 Reporter:  AlexHill |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 AlexHill):

 Current status of this issue: [https://github.com/django/django/pull/4130
 the main pull request, #4130] has been reviewed extensively but is waiting
 on  [https://github.com/django/django/pull/4122 another pull request,
 #4122], which makes some changes to SQLite schema alterations slightly.

 My last change to the SQLite schema alteration branch explicitly disables
 FK constraints during schema alterations in order to guarantee the
 expected behaviour. This change hasn't been reviewed yet; if anybody has a
 few minutes, I would really appreciate a review:
 https://github.com/django/django/pull/4122

 Cheers,
 Alex

--
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.09a56f517b3f3b2c7b6b362d6f29ca90%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23422: Cannot add Permission to Group in data migration

2015-03-08 Thread Django

#23422: Cannot add Permission to Group in data migration
+--
 Reporter:  tjwalch |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.7
 Severity:  Normal  |   Resolution:  wontfix
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by jwhitlock):

 Here's an example of calling `create_permissions` directly from a data
 migration, as suggested  by carljm:

 {{{
 def make_permissions(apps, schema_editor, with_create_permissions=True):
 Group = apps.get_model("auth", "Group")
 Permission = apps.get_model("auth", "Permission")
 try:
 perm = Permission.objects.get(
 codename='add_mymodel', content_type__app_label='my_app')
 except Permission.DoesNotExist:
 if with_create_permissions:
 # Manually run create_permissions
 from django.contrib.auth.management import create_permissions
 assert not getattr(apps, 'models_module', None)
 apps.models_module = True
 create_permissions(apps)
 apps.models_module = None
 return make_permissions(
 apps, schema_editor, with_create_permissions=False)
 else:
 raise
 my_new_group = Group.objects.create(name="test_group")
 my_new_group.permissions.add(perm)
 }}}

 Feels a little hacky, but it solved this `wontfix` for me .  I'd prefer a
 migration configuration that says "stop migrating, emit `post_migrate`
 signals, and restart migrations."

--
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/065.94576d82e90dd87aa004f7e8f21b913b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24382: django.utils.numberformat should be UTF-8 safe

2015-03-08 Thread Django

#24382: django.utils.numberformat should be UTF-8 safe
-+-
 Reporter:  jrief|Owner:
 Type:   |  alainivars
  Cleanup/optimization   |   Status:  new
Component:  Utilities|  Version:  1.8alpha1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by aaugustin):

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


--
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/063.5ba384d8d72f4923a5b2efa6623eed1f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21661: Password reset part of django.auth isn't documented

2015-03-08 Thread Django

#21661: Password reset part of django.auth isn't documented
-+-
 Reporter:  cortex@… |Owner:
 Type:   |  chriscauley
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.6
 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 Erik Romijn ):

 In [changeset:"8917684c736c445b7f4bfb7225b632cc3e5d400c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="8917684c736c445b7f4bfb7225b632cc3e5d400c"
 [1.7.x] Fixed #21661 -- Expanded authentication views documentation

 Backport of eb9b7abb833a6d317e355265552d47e0d8f24af8 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 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/083.5c0483363d4314ed99b22959911dba66%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21661: Password reset part of django.auth isn't documented

2015-03-08 Thread Django

#21661: Password reset part of django.auth isn't documented
-+-
 Reporter:  cortex@… |Owner:
 Type:   |  chriscauley
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.6
 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 Erik Romijn ):

 In [changeset:"930fc4db7b8c4f7eeca5ce55fb7b7f8529b5a52a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="930fc4db7b8c4f7eeca5ce55fb7b7f8529b5a52a"
 [1.8.x] Fixed #21661 -- Expanded authentication views documentation

 Backport of eb9b7abb833a6d317e355265552d47e0d8f24af8 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 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/083.84e222a8062bd9c6822ff9f646a5db2b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21661: Password reset part of django.auth isn't documented

2015-03-08 Thread Django

#21661: Password reset part of django.auth isn't documented
-+-
 Reporter:  cortex@… |Owner:
 Type:   |  chriscauley
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.6
 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 Erik Romijn ):

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


Comment:

 In [changeset:"eb9b7abb833a6d317e355265552d47e0d8f24af8"]:
 {{{
 #!CommitTicketReference repository=""
 revision="eb9b7abb833a6d317e355265552d47e0d8f24af8"
 Fixed #21661 -- Expanded authentication views documentation
 }}}

--
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/083.592f333f2125c2054a2a4d4508194c6e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #12943: Unnamed captures are not passed to views in included URLconfs

2015-03-08 Thread Django

#12943: Unnamed captures are not passed to views in included URLconfs
--+-
 Reporter:  petri.lehtinen@…  |Owner:  bpeschier
 Type:  Bug   |   Status:  assigned
Component:  Core (URLs)   |  Version:  1.1
 Severity:  Normal|   Resolution:
 Keywords:  ams2015   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-

Comment (by MarkusH):

 PR https://github.com/django/django/pull/4279

--
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/080.b0e0f42d1aed40eeb5757abf894dc025%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #9596: Comparing a DateTimeField to a date is too hard

2015-03-08 Thread Django

#9596: Comparing a DateTimeField to a date is too hard
-+-
 Reporter:  django@… |Owner:
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  lookup_type date | Triage Stage:  Accepted
  datetimefield compare comparison   |
  query_term field lookup|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by jdufresne):

 * needs_better_patch:  1 => 0


Comment:

 Created a PR that is ready for review.

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

--
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/074.22d9d4c2c05fb050682ad4912534f388%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24382: django.utils.numberformat should be UTF-8 safe

2015-03-08 Thread Django

#24382: django.utils.numberformat should be UTF-8 safe
-+-
 Reporter:  jrief|Owner:
 Type:   |  alainivars
  Cleanup/optimization   |   Status:  closed
Component:  Utilities|  Version:  1.8alpha1
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by jrief):

 My concrete problem is an implementation of a class derived from
 ``Decimal``: https://github.com/jrief/django-
 shop/blob/0.3.0.dev/shop/money/money_maker.py

 This class overrides the ``__format__`` method, so that Django's
 ``numberformat`` can render instances of that type in the current locale.
 But my class also uses unicode symbols, for instance the € symbol.
 Therefore strings in ``numberformat`` shall be mixable with unicode
 strings from other modules.

 You can also see it from another perspective.
 Most Python files in Django contain this line:
 ```
 from __future__ import unicode_literals
 ```
 without that line, unicode literals only work with Python-3. By not adding
 this, Django intentionally behaves differently  in Py-2 and Py-3.

--
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/063.6f8d47c8dabb1c144fd2e96194c44825%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #24463: Remove old functionality from `HttpRequest`

2015-03-08 Thread Django

#24463: Remove old functionality from `HttpRequest`
--+
Reporter: rednaw| Owner: nobody
Type: Cleanup/optimization | Status: new
Component: HTTP handling |Version: master
Severity: Normal| Keywords:
Triage Stage: Unreviewed| Has patch: 0
Easy pickings: 0 | UI/UX: 0
--+
The `scheme()` method on `HttpRequest` returns the scheme the request was
on, so http or https. If you look at the implementation of the method:

https://github.com/django/django/blob/master/django/http/request.py#L163

You see that it checks a Django setting and if that doesn't result in
https, it falls back to the `_get_scheme()` method.

Now if you look at the `_get_scheme()` method:

https://github.com/django/django/blob/master/django/http/request.py#L159

You see it checks if the environment variable "HTTPS" is set to "on". I
think is old functionality that doesn't belong in Django anymore. It was
probably from the time mod_python was used. These days this functionality
is implemented by WSGI:

https://www.python.org/dev/peps/pep-/#environ-variables

(search for HTTPS=on)

Also the WSGI handler in Django overwrites the `_get_scheme()`:

https://github.com/django/django/blob/master/django/core/handlers/wsgi.py#L115

And since every HTTP request in Django goes through WSGI, the
`_get_scheme()` method in `HttpRequest` would never be used.

So I think we should remove this functionality from `HttpRequest`, to
prevent confusion, because when I stumbled upon this piece of code it
confused me quite a bit and it took me some time to find out what it might
be.

--
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/049.c3f5aa60696a6317e66e44e7314ba09b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21661: Password reset part of django.auth isn't documented

2015-03-08 Thread Django

#21661: Password reset part of django.auth isn't documented
-+-
 Reporter:  cortex@… |Owner:
 Type:   |  chriscauley
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by rednaw):

 * 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 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/083.fe6e42e3e4a341a7914cae1d208174ac%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23407: makemigrations doesn't use --noinput

2015-03-08 Thread Django

#23407: makemigrations doesn't use --noinput
-+-
 Reporter:  bmispelon|Owner:  knbk
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Migrations   |  Version:  1.7
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  sprint ams2015   | Triage Stage:  Ready for
 |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Markus Holtermann ):

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


Comment:

 In [changeset:"e272904ff7cc4d138e316ba2e7811666053860a4"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e272904ff7cc4d138e316ba2e7811666053860a4"
 Fixed #23407 -- Extended coverage of makemigrations --noinput option.

 Changed --noinput option in makemigrations to suppress all user prompts,
 not just when combined with --merge.
 }}}

--
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.dbc8d78dcc3ee54a227992804b3beb9f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21661: Password reset part of django.auth isn't documented

2015-03-08 Thread Django

#21661: Password reset part of django.auth isn't documented
-+-
 Reporter:  cortex@… |Owner:
 Type:   |  chriscauley
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.6
 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
-+-

Comment (by rednaw):

 I created a PR for this:

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

--
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/083.5ba190b7641f68edc42d6049895c75b9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23407: makemigrations doesn't use --noinput

2015-03-08 Thread Django

#23407: makemigrations doesn't use --noinput
-+-
 Reporter:  bmispelon|Owner:  knbk
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Migrations   |  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  sprint ams2015   | Triage Stage:  Ready for
 |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by MarkusH):

 * stage:  Accepted => Ready for checkin


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.67e324f0ac200a0da7e499be1da05a58%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #12943: Unnamed captures are not passed to views in included URLconfs

2015-03-08 Thread Django

#12943: Unnamed captures are not passed to views in included URLconfs
--+-
 Reporter:  petri.lehtinen@…  |Owner:  bpeschier
 Type:  Bug   |   Status:  assigned
Component:  Core (URLs)   |  Version:  1.1
 Severity:  Normal|   Resolution:
 Keywords:  ams2015   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-
Changes (by bpeschier):

 * keywords:   => ams2015
 * owner:  nobody => bpeschier
 * status:  new => assigned


Comment:

 I added a PR for this. It will enforce args and kwargs will never be
 combined, but if you only use unnamed arguments, it will propagate the
 positional argument.

--
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/080.c244e2cb871abcb3cc5000496d7a9ed6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23903: Update docs/man/django-admin.1

2015-03-08 Thread Django

#23903: Update docs/man/django-admin.1
--+
 Reporter:  timgraham |Owner:
 Type:  Cleanup/optimization  |   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
--+
Changes (by erikr):

 * owner:  erikr =>
 * status:  assigned => new


--
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.4b146b38d4df7a940274531cd83c6873%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24460: Update documentation to explain why `HttpRequest.build_absolute_uri` doesn't have a scheme option

2015-03-08 Thread Django

#24460: Update documentation to explain why `HttpRequest.build_absolute_uri`
doesn't have a scheme option
--+
 Reporter:  rednaw|Owner:  rednaw
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:  build_absolute_uri| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Erik Romijn ):

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


Comment:

 In [changeset:"794c3f74c32062d0f2ad021cb2af0e530b40730d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="794c3f74c32062d0f2ad021cb2af0e530b40730d"
 Fixed #24460 -- Extended HttpRequest.build_absolute_uri documentation

 Added explanation on why build_absolute_uri always enforces the
 request's scheme.
 }}}

--
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.8f29e58ca3b304c7c34f087667b17568%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #13409: "wrap" argument for django.conf.urls.defaults.url to decorate views more easily

2015-03-08 Thread Django

#13409: "wrap" argument for django.conf.urls.defaults.url to decorate views more
easily
-+-
 Reporter:  yourcelf |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (URLs)  |  Version:  master
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  url, | Triage Stage:  Accepted
  RegexURLResolver,  |
  RegexURLPattern, decorators|
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by bpeschier):

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


Comment:

 {{{patterns}}} and dotted string urls are now deprecated, which
 invalidates the main focus of the ticket as described.

 Though I can see the use case of wrapping groups of urls as aaugustin
 described, pushing view functionality (decorators) through {{{include}}}
 which just builds up the urlconf strikes me as inappropriate (what about
 includes inside the included urlconf for example?).

--
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.f83a58e66fab842472a0b85cff599645%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24460: Update documentation to explain why `HttpRequest.build_absolute_uri` doesn't have a scheme option

2015-03-08 Thread Django

#24460: Update documentation to explain why `HttpRequest.build_absolute_uri`
doesn't have a scheme option
--+
 Reporter:  rednaw|Owner:  rednaw
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  build_absolute_uri| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+
Changes (by erikr):

 * needs_better_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 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.022c252d6e2dbaf44f17d303f3b5794d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24460: Update documentation to explain why `HttpRequest.build_absolute_uri` doesn't have a scheme option

2015-03-08 Thread Django

#24460: Update documentation to explain why `HttpRequest.build_absolute_uri`
doesn't have a scheme option
--+
 Reporter:  rednaw|Owner:  rednaw
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  build_absolute_uri| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by rednaw):

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


--
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.ebcbb5c92903ed21858c95cbef0ac025%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24460: Update documentation to explain why `HttpRequest.build_absolute_uri` doesn't have a scheme option

2015-03-08 Thread Django

#24460: Update documentation to explain why `HttpRequest.build_absolute_uri`
doesn't have a scheme option
--+
 Reporter:  rednaw|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  build_absolute_uri| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by bmispelon):

 * 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 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.d4a82df238c4fc489968037107f1ea02%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24460: Update documentation to explain why `HttpRequest.build_absolute_uri` doesn't have a scheme option

2015-03-08 Thread Django

#24460: Update documentation to explain why `HttpRequest.build_absolute_uri`
doesn't have a scheme option
--+
 Reporter:  rednaw|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  build_absolute_uri| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by rednaw):

 Created a pull request for this:

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

--
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.02e828438d6aaae5336816fdbe59a740%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22955: Admin: reloading clears filter_horizontal entries

2015-03-08 Thread Django

#22955: Admin: reloading clears filter_horizontal entries
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:  admin| Triage Stage:  Accepted
  filter_horizontal reload   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by benkonrath):

 This pull request adds a failing test case to demonstrate the problem.

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

 I'm not exactly sure what the way forward is for this issue. There seems
 to be a couple tickets that have full rewrite of the select filter js
 code. My primary interest is ensuring that any re-write of the select
 filter js code incorporates this test so that this problem gets fixed.

--
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.5996df6e9b86259e205efd52dfe01fbc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23173: SCRIPT_URL on WSGI is misinterpreted when PATH_INFO is empty

2015-03-08 Thread Django

#23173: SCRIPT_URL on WSGI is misinterpreted when PATH_INFO is empty
-+-
 Reporter:  j-sz@…   |Owner:  bpeschier
 Type:  Bug  |   Status:  closed
Component:  Core (URLs)  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  wsgi, script name,   | Triage Stage:  Ready for
  negative index slicing,ams2015 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Markus Holtermann ):

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


Comment:

 In [changeset:"336512fae77ec214ad6db24166b9a8676007cc09"]:
 {{{
 #!CommitTicketReference repository=""
 revision="336512fae77ec214ad6db24166b9a8676007cc09"
 Fixed #23173 -- Fixed incorrect stripping of SCRIPT_URL
 }}}

--
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.8b2eb6e72c02588f9dfc66e31437a45f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #16860: Provide hooks for password policy

2015-03-08 Thread Django

#16860: Provide hooks for password policy
--+
 Reporter:  PaulM |Owner:  erikr
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  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
--+
Changes (by erikr):

 * owner:  nobody => erikr
 * status:  new => assigned
 * version:  1.3 => master


Comment:

 I've submitted a PR with a demo of a fresh approach on
 https://github.com/django/django/pull/4276
 The PR is not meant to be mergable.

 New mailing list discussion on: https://groups.google.com/forum/#!topic
 /django-developers/9GBhgGXmEKs

--
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/063.55d736e6cb118f5750a2bbbf1958d864%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23173: SCRIPT_URL on WSGI is misinterpreted when PATH_INFO is empty

2015-03-08 Thread Django

#23173: SCRIPT_URL on WSGI is misinterpreted when PATH_INFO is empty
-+-
 Reporter:  j-sz@…   |Owner:  bpeschier
 Type:  Bug  |   Status:  assigned
Component:  Core (URLs)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  wsgi, script name,   | Triage Stage:  Ready for
  negative index slicing,ams2015 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by MarkusH):

 * has_patch:  0 => 1
 * stage:  Accepted => Ready for checkin


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.2bf88b00745142f553a3986f8c9116f9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23838: LazyObject is missing iter

2015-03-08 Thread Django

#23838: LazyObject is missing __iter__
-+-
 Reporter:  rednaw   |Owner:  rednaw
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Baptiste Mispelon ):

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


Comment:

 In [changeset:"a5b225084f69e27b78fab0f2954fa9520656976e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a5b225084f69e27b78fab0f2954fa9520656976e"
 Fixed #23838 -- added missing `__iter__` to LazyObject
 }}}

--
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.f3e8eb7793f1cffc7f509eaa86980912%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23173: SCRIPT_URL on WSGI is misinterpreted when PATH_INFO is empty

2015-03-08 Thread Django

#23173: SCRIPT_URL on WSGI is misinterpreted when PATH_INFO is empty
-+-
 Reporter:  j-sz@…   |Owner:  bpeschier
 Type:  Bug  |   Status:  assigned
Component:  Core (URLs)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  wsgi, script name,   | Triage Stage:  Accepted
  negative index slicing,ams2015 |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by bpeschier):

 * keywords:  wsgi, script name, negative index slicing => wsgi, script
 name, negative index slicing,ams2015
 * owner:  nobody => bpeschier
 * 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 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.92a16c4e8ccf1e67628fe0ef54deba8c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24397: Speed up model rendering with apps.ready = False

2015-03-08 Thread Django

#24397: Speed up model rendering with apps.ready = False
--+
 Reporter:  knbk  |Owner:  knbk
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Migrations|  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 Markus Holtermann ):

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


Comment:

 In [changeset:"888c9b6429a44824078a49fb1ebacf2e950cd887"]:
 {{{
 #!CommitTicketReference repository=""
 revision="888c9b6429a44824078a49fb1ebacf2e950cd887"
 Fixed #24397 -- Sped up rendering multiple model states.

 Set apps.ready to False when rendering multiple models. This prevents
 that the cache on Model._meta is expired on all models after each time a
 single model is rendered. Prevented that Apps.clear_cache() refills the
 cache on Apps.get_models(), so that the wrong value cannot be cached
 when cloning a StateApps.
 }}}

--
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/062.f8ee302179462c67c4fc600ce87fb2fb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23926: Misleading error message provided when custom permission names are too long

2015-03-08 Thread Django

#23926: Misleading error message provided when custom permission names are too 
long
-+-
 Reporter:  Greatlemer   |Owner:  joeri
 Type:  Bug  |   Status:  assigned
Component:  contrib.auth |  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by erikr):

 * has_patch:  0 => 1
 * stage:  Accepted => Ready for checkin


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.c1baf11fe1b0a43372d29c4c7c51999a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22955: Admin: reloading clears filter_horizontal entries

2015-03-08 Thread Django

#22955: Admin: reloading clears filter_horizontal entries
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:  admin| Triage Stage:  Accepted
  filter_horizontal reload   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by benkonrath):

 * status:  closed => new
 * resolution:  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 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.1a10509480759de45417cfe27767ad4c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23926: Misleading error message provided when custom permission names are too long

2015-03-08 Thread Django

#23926: Misleading error message provided when custom permission names are too 
long
--+
 Reporter:  Greatlemer|Owner:  joeri
 Type:  Bug   |   Status:  assigned
Component:  contrib.auth  |  Version:  1.7
 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 joeri):

 Added PR https://github.com/django/django/pull/4274

--
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.ee1ef8fe7a6a5c664278dfe85f887ab8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22990: Sensitive POST data leaks from complex variables

2015-03-08 Thread Django

#22990: Sensitive POST data leaks from complex variables
--+
 Reporter:  vzima |Owner:  auvipy
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Core (Other)  |  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
--+
Changes (by auvipy):

 * owner:  vzima => auvipy


--
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/063.80e74e1f98dc4dc82e84354daaad84eb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23829: Allow customizing the `ping_google` URL

2015-03-08 Thread Django

#23829: Allow customizing the `ping_google` URL
-+-
 Reporter:  jwa  |Owner:  auvipy
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  contrib.sitemaps |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  sitemaps,| Triage Stage:  Accepted
  ping_google|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by auvipy):

 * owner:   => auvipy
 * 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 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/061.a511030e87c1545139d0892797319c70%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22955: Admin: reloading clears filter_horizontal entries

2015-03-08 Thread Django

#22955: Admin: reloading clears filter_horizontal entries
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.6
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  admin| Triage Stage:  Accepted
  filter_horizontal reload   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by benkonrath):

 I think #13614 is actually a separate issue (although it seems there has
 been some discussion about this issue on #13614). The test html in comment
 16 (https://code.djangoproject.com/ticket/13614#comment:16) seems to be
 working on Firfox 36.

 I can confirm that this is still problem on Firefox 36 with Django 1.6.10,
 1.7.5, 1.8b1. How can I reopen this bug?

--
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.de588b87c72210737ed879f295b9dfcd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23926: Misleading error message provided when custom permission names are too long

2015-03-08 Thread Django

#23926: Misleading error message provided when custom permission names are too 
long
--+
 Reporter:  Greatlemer|Owner:  joeri
 Type:  Bug   |   Status:  assigned
Component:  contrib.auth  |  Version:  1.7
 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 joeri):

 The error is technically correct but in some cases doesn't point people to
 the most obvious cause. The cryptic database error mentioned in #18866
 was replaced with the current message. It was an improvement but with
 custom permissions, the error is still cryptic.

--
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.b432fd544111c07b9888391f45b34b1f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #18586: Rewrite unit tests migrated from doctests

2015-03-08 Thread Django

#18586: Rewrite unit tests migrated from doctests
-+-
 Reporter:  konk |Owner:
 Type:   |  alainivars
  Cleanup/optimization   |   Status:  assigned
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  unit tests   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by alainivars):

 * owner:  ChillarAnand => alainivars
 * 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 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.8624203170df35a0f1c81dda200f186a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #16025: distinct does not apply to aggregated querysets

2015-03-08 Thread Django

#16025: distinct does not apply to aggregated querysets
-+-
 Reporter:  micolous |Owner:
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |
 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 mikalai):

 * owner:  mikalai =>
 * status:  assigned => new


--
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.c04ea739d4b5c5493ec8487a7c5c4166%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24461: Admin readonly_fields pointing to properties (@property) do not get escaped.

2015-03-08 Thread Django

#24461: Admin readonly_fields pointing to properties (@property) do not get
escaped.
---+-
 Reporter:  eranrund   |Owner:  bmispelon
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  1.7
 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 bmispelon):

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


Comment:

 Hi,

 I can indeed reproduce the issue, thanks for bringing it up.

--
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.785de9e1dd640537b4430a0f5e02174b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23926: Misleading error message provided when custom permission names are too long

2015-03-08 Thread Django

#23926: Misleading error message provided when custom permission names are too 
long
--+
 Reporter:  Greatlemer|Owner:  joeri
 Type:  Bug   |   Status:  assigned
Component:  contrib.auth  |  Version:  1.7
 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 joeri):

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


--
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.7b0d823376e79c5b60aeb44787392c06%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24382: django.utils.numberformat should be UTF-8 safe

2015-03-08 Thread Django

#24382: django.utils.numberformat should be UTF-8 safe
-+-
 Reporter:  jrief|Owner:
 Type:   |  alainivars
  Cleanup/optimization   |   Status:  closed
Component:  Utilities|  Version:  1.8alpha1
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by alainivars):

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


Comment:

 I try to work on this ticket but I missing information about the actual
 problem. I try to impose unicode string as `number`, `decimal_sep` and
 `thousand_sep` but none of them failed. Can you give additional
 information what you are trying to accomplish.

--
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/063.e4d52e71a239bc1898c96fa879a694a4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24382: django.utils.numberformat should be UTF-8 safe

2015-03-08 Thread Django

#24382: django.utils.numberformat should be UTF-8 safe
-+-
 Reporter:  jrief|Owner:
 Type:   |  alainivars
  Cleanup/optimization   |   Status:  assigned
Component:  Utilities|  Version:  1.8alpha1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by alainivars):

 * owner:   => alainivars
 * 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 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/063.78de7d62f3f115012c4d7520bdff00d0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #9596: Comparing a DateTimeField to a date is too hard

2015-03-08 Thread Django

#9596: Comparing a DateTimeField to a date is too hard
-+-
 Reporter:  django@… |Owner:
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  lookup_type date | Triage Stage:  Accepted
  datetimefield compare comparison   |
  query_term field lookup|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 The code looks correct when USE_TZ = False. You also need to handle the
 more complicated case when USE_TZ = True.

 See the current implementation `datetime_trunc_sql` for an idea of what's
 needed.

--
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/074.64d21a40adad0c421568bf0395036d7c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #9596: Comparing a DateTimeField to a date is too hard

2015-03-08 Thread Django

#9596: Comparing a DateTimeField to a date is too hard
-+-
 Reporter:  django@… |Owner:
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  lookup_type date | Triage Stage:  Accepted
  datetimefield compare comparison   |
  query_term field lookup|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

 * owner:  aaugustin =>
 * status:  assigned => new


--
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/074.d9409cbb069ef99423c9c628806887ce%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23666: The command to run the unit tests doesn't work on windows

2015-03-08 Thread Django

Comment (by joeri):

The Windows (near) equivalent is to use with cmd.exe:

{{{
$ git clone https://github.com/django/django.git django-repo
$ cd django-repo\tests
$ set PYTHONPATH=..;%PYTHONPATH%
$ python runtests.py
}}}

The third line extends your PYTHONPATH with the parent directory for the
duration of the terminal session.
I added the python command in line 4, to use the one that is set in the
PATH rather than the one registered with Windows.

In my opinion the documentation doesn't need to have a Windows equivalent
of common bash commands.

--
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.79375b55c7269a500226251c1cbbf191%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24456: Table of form and model field relationships should include links

2015-03-08 Thread Django

#24456: Table of form and model field relationships should include links
--+
 Reporter:  EvilDMP   |Owner:  PsiloLR
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.7
 Severity:  Normal|   Resolution:  fixed
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by PsiloLR ):

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


Comment:

 In [changeset:"866e71140f9612e45087b8acafefa2e51ffc4a29"]:
 {{{
 #!CommitTicketReference repository=""
 revision="866e71140f9612e45087b8acafefa2e51ffc4a29"
 Fixed #24456 -- Update modelforms.txt table of Form/Model refs

 Added links to the Form/Model table to the field reference docs to
 point to their individual field references
 }}}

--
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/065.af6ce615935893e50c17850f931f10fe%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24456: Table of form and model field relationships should include links

2015-03-08 Thread Django

#24456: Table of form and model field relationships should include links
--+
 Reporter:  EvilDMP   |Owner:  PsiloLR
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.7
 Severity:  Normal|   Resolution:  fixed
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Daniele Procida ):

 In [changeset:"180f75c2a0d15e54a7088bd5cb7a57342da5661d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="180f75c2a0d15e54a7088bd5cb7a57342da5661d"
 Merge pull request #4271 from PsiloLR/ticket_24456

 Fixed #24456 -- Update modelforms.txt table of Form/Model refs
 }}}

--
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/065.deec7c3d7d043a17117a698e0763606f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24456: Table of form and model field relationships should include links

2015-03-08 Thread Django

#24456: Table of form and model field relationships should include links
--+
 Reporter:  EvilDMP   |Owner:  PsiloLR
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by PsiloLR):

 * has_patch:  0 => 1


Old description:

> We should add links to the field reference docs:
>
> * https://docs.djangoproject.com/en/1.7/topics/forms/modelforms/#field-
> types

New description:

 We should add links to the field reference docs:

 * https://docs.djangoproject.com/en/1.7/topics/forms/modelforms/#field-
 types

--

--
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/065.67f0f5fd52ee0f2530154e595b37434b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24456: Table of form and model field relationships should include links

2015-03-08 Thread Django

#24456: Table of form and model field relationships should include links
--+
 Reporter:  EvilDMP   |Owner:  PsiloLR
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by PsiloLR):

 Please see my pull request: https://github.com/django/django/pull/4271

--
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/065.aefeb60aba335cc00190b18a8dd237a3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24013: reverse() escapes unreserved characters supplied by prefix

2015-03-08 Thread Django

#24013: reverse() escapes unreserved characters supplied by prefix
-+-
 Reporter:  tgerdes  |Owner:  bpeschier
 Type:  Bug  |   Status:  assigned
Component:  Core (URLs)  |  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:  ams2015  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by bpeschier):

 So the problem is very similar, as mentioned, to #3 and the solution
 is also very similar: treat the prefix as another path segment and use the
 same safe-argument when calling {{{urlquote}}} 1]. This makes the test for
 #20022 fail, but that test is incorrect and can be easily fixed (it should
 test escaping of {{{%}}}, not {{{~}}}, which is an unreserved char)

 There is another problem however: all url patterns should be valid regex,
 but the script prefix does not have to be (or does it?). When
 {{{reverse}}} tries to use the prefix, it assumes it needs to normalize it
 and thus that it is a valid regex. This breaks {{{normalize}}} when you
 add a singular {{{)}}} which is a valid path part, but not valid regex.

 The prefix-argument is undocumented and defaults to the script prefix. So
 we can either assume all prefixes can be treated as plain strings, or we
 can regex-escape {{{get_script_prefix}}} when {{{reverse}}} populates the
 prefix 2].


 1]:
 https://github.com/django/django/blob/master/django/core/urlresolvers.py#L448
 2]:
 https://github.com/django/django/blob/master/django/core/urlresolvers.py#L532

--
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/065.60fbe83f5f255da92d250e82318608e0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

51 matches

Mail list logo