date:20141113

Re: [Django] #16358: cached_db session with memcached forgets big values

2014-11-13 Thread Django

#16358: cached_db session with memcached forgets big values
-+-
 Reporter:  ccrisan  |Owner:  manfre
 Type:  Bug  |   Status:  closed
Component:  Core (Cache system)  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  session cache| Triage Stage:  Ready for
  memcached  |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Michael Manfre ):

 In [changeset:"a305695f28cb15165a19c3871aec878a230a5105"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a305695f28cb15165a19c3871aec878a230a5105"
 Merge pull request #3481 from manfre/ticket-16358

 Fixed #16358 - Made memcache backend delete old value on a failure to set.
 }}}

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

Re: [Django] #16358: cached_db session with memcached forgets big values

2014-11-13 Thread Django

#16358: cached_db session with memcached forgets big values
-+-
 Reporter:  ccrisan  |Owner:  manfre
 Type:  Bug  |   Status:  closed
Component:  Core (Cache system)  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  session cache| Triage Stage:  Ready for
  memcached  |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Michael Manfre ):

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


Comment:

 In [changeset:"bc8abe36ba5508fe788f6d49a26749268d368583"]:
 {{{
 #!CommitTicketReference repository=""
 revision="bc8abe36ba5508fe788f6d49a26749268d368583"
 Fixed #16358 - Made memcache backend delete old value on a failure to set.

 Default Memcached configuration allows for a maximum object of 1MB and
 will fail to set the key if it is too large. The key will be deleted from
 memcached if it fails to be set. This is needed to avoid an issue with
 cache_db session backend using the old value stored in memcached, instead
 of the newer value stored in the database.
 }}}

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

Re: [Django] #22503: Inconsistent behavior when a QuerySet is sliced

2014-11-13 Thread Django

#22503: Inconsistent behavior when a QuerySet is sliced
-+-
 Reporter:  ajaest   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  QuerySet, filter,|  Needs documentation:  0
  slice  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by tchaumeny):

 See also https://groups.google.com/forum/#!topic/django-
 developers/ELqU2xt_Qo0 (sliced querysets not usable in a
 `ModelChoiceField` because not filterable).

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

Re: [Django] #23817: QuerySet evaluation docs are out of date

2014-11-13 Thread Django

#23817: QuerySet evaluation docs are out of date
---+--
 Reporter:  konk   |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by konk):

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


Comment:

 I created a simple pull request
 (https://github.com/django/django/pull/3507) as well and while I was in
 there, I also added a note regarding #22503. If anyone wants to suggest a
 different wording, no problem.

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

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

[Django] #23817: QuerySet evaluation docs are out of date

2014-11-13 Thread Django

#23817: QuerySet evaluation docs are out of date
---+
 Reporter:  konk   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 The [[https://docs.djangoproject.com/en/dev/ref/models/querysets/#when-
 querysets-are-evaluated|docs for QuerySet]] contain a reference to partial
 evaluation of queryset and a warning that explicitly calling `list(qs)`
 requires more memory than just iterating over a queryset.

 As far as I can see, anytime a QuerySet is evaluated, all results are
 pulled from the database at once, stored in `_result_cache` and most list-
 like operations are simply proxied to this cache. This means that there is
 no partial evaluation going on anymore, and `list(qs)` simply creates a
 shallow copy of `qs._result_cache`.

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

Re: [Django] #23778: Running tests outside the test runner needs clarification

2014-11-13 Thread Django

Comment (by prestontimmons):

I think there's merit to keeping your example minimal.

I just started imagining a best-practice type section of the docs for
running tests in reusable apps. It would cover things like:

* Using the test runner in a script
* Managing python path
* Adding test-only models
* Configuring settings manually when including an example project is
overkill
* etc.

This assumes there's a relative consensus of what "best practice" means.

I don't think that's in scope of this ticket, though.

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

Re: [Django] #23588: list_display method attributes description links

2014-11-13 Thread Django

#23588: list_display method attributes description links
--+
 Reporter:  eliasvc   |Owner:  funkybob
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.7
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  1
  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:"3a550bb6d32172fc1ec5dd314d20ef1235db995a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3a550bb6d32172fc1ec5dd314d20ef1235db995a"
 Fixed #23588 -- Added a link in tutorial for list_display options.
 }}}

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

Re: [Django] #23588: list_display method attributes description links

2014-11-13 Thread Django

#23588: list_display method attributes description links
--+
 Reporter:  eliasvc   |Owner:  funkybob
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.7
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"b050dc46a9758e370c5b05ff25a133b741ffe465"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b050dc46a9758e370c5b05ff25a133b741ffe465"
 [1.7.x] Fixed #23588 -- Added a link in tutorial for list_display options.

 Backport of 3a550bb6d32172fc1ec5dd314d20ef1235db995a 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/065.4b2238477f952a8aea1e028d1a4c414c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23793: Password Reset is confusing

2014-11-13 Thread Django

#23793: Password Reset is confusing
--+
 Reporter:  collinanderson|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.auth  |  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:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Cleanup/optimization
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 This sounds fine. Ideally the documentation changes would be a separate
 commit or pull request so it can be more easily backported.

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

Re: [Django] #23765: Get rid of system check 1_6.W002

2014-11-13 Thread Django

#23765: Get rid of system check 1_6.W002
--+
 Reporter:  marfire   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (System checks)  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"c24a2e6cbd391c0d6359fce00e6390de9af9d2d0"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c24a2e6cbd391c0d6359fce00e6390de9af9d2d0"
 Fixed #23765 -- Removed BooleanField default check which often yielded
 false positives.
 }}}

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

Re: [Django] #23802: Typos in 1.7 release notes

2014-11-13 Thread Django

#23802: Typos in 1.7 release notes
---+--
 Reporter:  aruseni|Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"d5a109f6e6684b2ea8028af5c57f4257872d11aa"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d5a109f6e6684b2ea8028af5c57f4257872d11aa"
 Fixed #23802 -- Typos in 1.7 release notes.
 }}}

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

Re: [Django] #23802: Typos in 1.7 release notes

2014-11-13 Thread Django

#23802: Typos in 1.7 release notes
---+--
 Reporter:  aruseni|Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 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 Tim Graham ):

 In [changeset:"cf5e2c46f2122c19c60f74299275f6fbcdd9144b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="cf5e2c46f2122c19c60f74299275f6fbcdd9144b"
 [1.7.x] Fixed #23802 -- Typos in 1.7 release notes.

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

Re: [Django] #23741: [System Check for migrations] Check presence of all foreign keys

2014-11-13 Thread Django

Comment (by notsqrt):

An initial implementation at https://github.com/NotSqrt/django/compare/fk-
check

It's harder than I thought:

* how to ignore models that have to be migrated ? (in the actual apps, and
in django tests)
* how to use migrations in django test suite if we ignore unmigrated
models ?
* Is there a standard way for django test suite to test against various DB
backends ? SQLite does not support foreign key constraints in the first
place, so it's not interesting to test against a SQLite DB.. (I have not
looked into the details of djangoci)
* Do I really have to check each model in each database ? or is there
something intelligent to do via database routers ?

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

[Django] #23816: Ability to defer model field by default

2014-11-13 Thread Django

#23816: Ability to defer model field by default
--+
 Reporter:  rcoup |  Owner:  nobody
 Type:  New feature   | Status:  new
Component:  Database layer (models, ORM)  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Today's small #IWantAPony is to be able to mark model fields as deferred
 by default. No need to chase down every queryset and add `.defer()`, or
 use a custom manager setup & remember to set `use_for_related_fields`.

 {{{
 class MyModel(models.Model):
enormous_field = models.TextField(defer=True)
other_field = models.IntegerField()
 }}}

 Which is (simplistically) equivalent to the following:

 {{{
 class MyManager(models.Manager):
   use_for_related_fields = True

   def get_queryset(self, *args, **kwargs):
 return super(MyManager, self).get_queryset(*args,
 **kwargs).defer("enormous_field")

 class MyModel(models.Model):
enormous_field = models.TextField()
other_field = models.IntegerField()

objects = MyManager()
 }}}

 Obviously, you can still do `MyModel.objects.defer(None)` to do the full
 query.

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

[Django] #23815: CsrfViewMiddleware UnicodeDecodeError

2014-11-13 Thread Django

#23815: CsrfViewMiddleware UnicodeDecodeError
-+-
 Reporter:   |  Owner:  nobody
  codeitloadit   | Status:  new
 Type:   |Version:  1.6
  Uncategorized  |   Keywords:  middleware CsrfViewMiddleware
Component:  HTTP |  UnicodeDecodeError
  handling   |  Has patch:  0
 Severity:  Normal   |  UI/UX:  0
 Triage Stage:   |
  Unreviewed |
Easy pickings:  0|
-+-
 The csrf middleware is raising an exception when the HTTP_REFERER contains
 non-ascii characters.  Since this code is attempting to validate the
 referer, I would expect these request to just be rejected and return 403.

 Here is the code in `django/middleware/csrf.py`:

 {{{

 referer = request.META.get('HTTP_REFERER')
 if referer is None:
 return self._reject(request, REASON_NO_REFERER)

 # Note that request.get_host() includes the port.
 good_referer = 'https://%s/' % request.get_host()
 if not same_origin(referer, good_referer):
 reason = REASON_BAD_REFERER % (referer, good_referer)
 return self._reject(request, reason)
 }}}

 This issue is very similar to
 [https://code.djangoproject.com/ticket/20356] which was patched by
 
[https://github.com/django/django/commit/8fd44b2551b9cca765b216a31306f9c6935f1492]
 which just encodes the referer like so:
 {{{
 referer = force_text(request.META.get('HTTP_REFERER', ''),
 errors='replace')
 }}}

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

Re: [Django] #23748: inspectdb should introspect autofield (was: inspectdb converts auto increment primary keys into primary key models.IntegerField() rather than primary key models.AutoField())

2014-11-13 Thread Django

#23748: inspectdb should introspect autofield
-+-
 Reporter:  paulcdejean  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.7
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  inspectdb|  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by collinanderson):

 * status:  closed => new
 * resolution:  invalid =>
 * component:  Utilities => Database layer (models, ORM)
 * type:  Uncategorized => New feature
 * stage:  Unreviewed => Someday/Maybe


Comment:

 Opening this for if someone wants to implement the introspection. (Though,
 it's not a 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/069.e031b6e8d514e8c674f4e2030dc8bd88%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23812: Use django.utils.six.moves.range instead of xrange

2014-11-13 Thread Django

#23812: Use django.utils.six.moves.range instead of xrange
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by collinanderson):

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

Re: [Django] #23784: Error reporting docs needs to state clearly that changing logging conf error emails are not sent out unless configuring it again

2014-11-13 Thread Django

#23784: Error reporting docs needs to state clearly that changing logging conf
error emails are not sent out unless configuring it again
---+
 Reporter:  peterlauri |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  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:  1  |UI/UX:  0
---+
Changes (by collinanderson):

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


Comment:

 I could see slightly improved wording being helpful, though it would be
 nice to not increase the amount of text too much.

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

Re: [Django] #23765: Get rid of system check 1_6.W002

2014-11-13 Thread Django

#23765: Get rid of system check 1_6.W002
--+
 Reporter:  marfire   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (System checks)  |  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 collinanderson):

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


Comment:

 I originally proposed the idea for this check because I was bitten by it a
 few times while upgrading, but I agree that it is now more safe to remove
 this.

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

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

Re: [Django] #23814: Documented apps refactored out of Django

2014-11-13 Thread Django

#23814: Documented apps refactored out of Django
--+
 Reporter:  shabda|Owner:  shabda
 Type:  Cleanup/optimization  |   Status:  assigned
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 shabda):

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

Re: [Django] #13883: SelectBox.js with grouping (optgroup elements)

2014-11-13 Thread Django

#13883: SelectBox.js with grouping (optgroup elements)
-+-
 Reporter:  SardarNL |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.2
 Severity:  Normal   |   Resolution:
 Keywords:  admin, SelectBox,| Triage Stage:  Accepted
  optgroup, sprintdec2010|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  1
Easy pickings:  0|
-+-

Comment (by timgraham):

 No, the ticket is still open. It doesn't appear we have a tested 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/066.887d08ee14e1ee18bde7a9444f53b7f4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23814: Documented apps refactored out of Django

2014-11-13 Thread Django

#23814: Documented apps refactored out of Django
--+
 Reporter:  shabda|Owner:  shabda
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  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:  1 |UI/UX:  0
--+
Changes (by timgraham):

 * stage:  Unreviewed => Accepted


Comment:

 I was thinking to put this new doc in something like `misc/official-
 apps.txt` but other ideas welcome.

 If you didn't see it, there is already a
 [https://github.com/django/django/pull/3385 pull request] to change
 formtools.

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

Re: [Django] #13883: SelectBox.js with grouping (optgroup elements)

2014-11-13 Thread Django

#13883: SelectBox.js with grouping (optgroup elements)
-+-
 Reporter:  SardarNL |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.2
 Severity:  Normal   |   Resolution:
 Keywords:  admin, SelectBox,| Triage Stage:  Accepted
  optgroup, sprintdec2010|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  1
Easy pickings:  0|
-+-

Comment (by rynomster):

 Did this change ever make it to trunk?
 I can't seem to find 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/066.4fd2239b1064b29661ce984c4619c7d9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23809: Update Localflavor docs

2014-11-13 Thread Django

#23809: Update Localflavor docs
-+-
 Reporter:  shabda   |Owner:  shabda
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.7
Component:  Documentation|   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by shabda):

 Opened #23814

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

Re: [Django] #23814: Documented apps refactored out of Django

2014-11-13 Thread Django

#23814: Documented apps refactored out of Django
-+-
 Reporter:  shabda   |Owner:  shabda
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.7
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by shabda):

 * owner:  nobody => shabda
 * needs_better_patch:   => 0
 * status:  new => assigned
 * needs_tests:   => 0
 * needs_docs:   => 0


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

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

[Django] #23814: Documented apps refactored out of Django

2014-11-13 Thread Django

#23814: Documented apps refactored out of Django
--+
 Reporter:  shabda|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.7
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+
 Follow up to: #23809

 Documented apps refactored out of Django

 * comments
 * localflavor
 * formtools

 Remove documentation for removed apps - Localflavor
 Remove documentation for formtools and point to RTD

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

Re: [Django] #23813: Add checks for common URLpattern errors

2014-11-13 Thread Django

#23813: Add checks for common URLpattern errors
--+
 Reporter:  jwa   |Owner:  jwa
 Type:  New feature   |   Status:  new
Component:  Core (System checks)  |  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 timgraham):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * needs_tests:   => 0
 * 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/061.92a215db5f44155e34cc1638d38ec241%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #23813: Add checks for common URLpattern errors

2014-11-13 Thread Django

#23813: Add checks for common URLpattern errors
--+
 Reporter:  jwa   |  Owner:  jwa
 Type:  New feature   | Status:  new
Component:  Core (System checks)  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 The system checks framework can be expanded to help less experienced users
 help with common mistakes. One source of those is the urlpatterns we have
 to configure. It would be nice to have checks in place that verify the
 validity and sanity of urls.

 One particular example that comes to mind (from my own experience):

 {{{
 urlpatterns = [
 url(r'^my_app/$', include('my_app')),
 ]
 }}}

 This would trigger a warning that the trailing '$' in this regular
 expression is most likely not intended. :-)


 Please do suggest any additional checks that could be added as well.

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

Re: [Django] #23805: query `first` method clears cached queryset for prefetch_related

2014-11-13 Thread Django

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

Comment:

In the first code example, `first()` is used on an unordered queryset. As
`first()` is intended to be deterministic, it isn't surprising that it
tries to add an order condition (which default to `order_by('pk')`.

Your second code example might work, but it isn't deterministic either as
there is no guarantee on the ordering of `pizza.toppings.all()`.

Do you need an arbitrary element or the first one ? If you need the first
one, there should be some notion of ordering involved, otherwise your
second solution is fine.

Also, you might wanna have a look at

https://docs.djangoproject.com/en/1.7/ref/models/queries/#django.db.models.Prefetch
(I've never used it myself but it should allow more complex
prefetch_related queryset, including ORDER clause as described here
https://docs.djangoproject.com/en/1.7/ref/models/querysets/#prefetch-
related).

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

Re: [Django] #23807: Postgres backend throws error when coercing psycopg2 version string to int when version contains non-numeric characters

2014-11-13 Thread Django

#23807: Postgres backend throws error when coercing psycopg2 version string to 
int
when version contains non-numeric characters
-+-
 Reporter:  ryanbagwell  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timgraham):

 * needs_docs:   => 0
 * needs_better_patch:   => 0
 * version:  1.7 => master
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 It seems like a reasonable request. You could look at the strategies use
 by other database backends in Django (regular expressions in MySQL, for
 example). It might also be fine simply to discard the value that can't be
 parsed.

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

Re: [Django] #23810: Passing 'start' from django url gives error “start() takes exactly 2 arguments (1 given) ”

2014-11-13 Thread Django

#23810: Passing 'start' from django url gives error “start() takes exactly 2
arguments (1 given) ”
-+--
 Reporter:  yogeshdmca   |Owner:  yogesh
 Type:  Bug  |   Status:  closed
Component:  Core (URLs)  |  Version:  1.6
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  django-url   | Triage Stage:  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
 * resolution:   => needsinfo


Comment:

 You haven't provided sufficient details to suggest that this is a bug in
 Django. If you can provide a failing test for Django's test suite, that
 would work. Or use the support channels as Claude suggested to get help.
 Thanks!

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

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

Re: [Django] #23761: Mysql validator crashes with None db_type return. - Backport of master fix to 1.7

2014-11-13 Thread Django

#23761: Mysql validator crashes with None db_type return. - Backport of master 
fix
to 1.7
-+-
 Reporter:  adepue   |Owner:  timgraham
 Type:  Bug  |   Status:  closed
Component:  Core (System |  Version:  1.7
  checks)|   Resolution:  fixed
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:  mysql db_type|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"e118e3af371ae58cee7420d2ea2020c8bdeb461e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e118e3af371ae58cee7420d2ea2020c8bdeb461e"
 Fixed #23761 -- Added test for MySQL validator and db_type is None.

 The issue was fixed on master in e9103402c0fa873aea58a6a11dba510cd308cb84
 so this just forwardports the test and release notes from stable/1.7.x.

 Forwardport of 2d12a59938 from stable/1.7.x
 }}}

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

Re: [Django] #23761: Mysql validator crashes with None db_type return. - Backport of master fix to 1.7

2014-11-13 Thread Django

#23761: Mysql validator crashes with None db_type return. - Backport of master 
fix
to 1.7
-+-
 Reporter:  adepue   |Owner:  timgraham
 Type:  Bug  |   Status:  closed
Component:  Core (System |  Version:  1.7
  checks)|   Resolution:  fixed
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:  mysql db_type|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"2d12a599383efff4ac1914e4cc5cf3b08cb2ff53"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2d12a599383efff4ac1914e4cc5cf3b08cb2ff53"
 [1.7.x] Fixed #23761 -- Fixed crash with MySQL validator and db_type is
 None.

 The issue was fixed on master in e9103402c0fa873aea58a6a11dba510cd308cb84.
 }}}

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

Re: [Django] #23810: Passing 'start' from django url gives error “start() takes exactly 2 arguments (1 given) ”

2014-11-13 Thread Django

#23810: Passing 'start' from django url gives error “start() takes exactly 2
arguments (1 given) ”
-+--
 Reporter:  yogeshdmca   |Owner:  yogesh
 Type:  Bug  |   Status:  new
Component:  Core (URLs)  |  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:  django-url   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by yogeshdmca):

 * cc: yogeshdmca (added)
 * status:  closed => new
 * resolution:  worksforme =>


Comment:

 Hi, issue i am getting that produce by django itself, that is not a
 mistake of any third party app or not my project code. so please take
 needful action.

 for example: you just create a demo project and give url like me. you will
 get same issue.

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

[Django] #23812: Use django.utils.six.moves.range instead of xrange

2014-11-13 Thread Django

#23812: Use django.utils.six.moves.range instead of xrange
+
   Reporter:  timgraham |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Core (Other)  |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  1
  UI/UX:  0 |
+
 These imports are equivalent but by using range the code looks more like
 Python 3 and has the advantage that we simply remove the import when the
 time comes to drop Python 2.

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

Re: [Django] #23811: Document how to use git bisect with runtests.py

2014-11-13 Thread Django

#23811: Document how to use git bisect with runtests.py
-+-
 Reporter:  timgraham|Owner:  bmispelon
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by bmispelon):

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


Comment:

 I've recently started to change my triaging workflow to be a little bit
 less ad-hoc.
 Ill try to document my new process.

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

[Django] #23811: Document how to use git bisect with runtests.py

2014-11-13 Thread Django

#23811: Document how to use git bisect with runtests.py
+
   Reporter:  timgraham |  Owner:
   Type:  Cleanup/optimization  | Status:  new
  Component:  Documentation |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 |
+
 While not specific to Django, it would be great to document how to
 automate bisecting a regression in Django. The text could live in
 internals/contributing/writing-code/unit-tests.txt.

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

Re: [Django] #23806: settings.DISALLOWED_USER_AGENTS has no tests

2014-11-13 Thread Django

#23806: settings.DISALLOWED_USER_AGENTS has no tests
--+
 Reporter:  timgraham |Owner:  sww
 Type:  Bug   |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"311feae8ba2a7b47e998764a1b0a26b5132e56f0"]:
 {{{
 #!CommitTicketReference repository=""
 revision="311feae8ba2a7b47e998764a1b0a26b5132e56f0"
 Fixed #23806 -- Added a test case for settings.DISALLOWED_USER_AGENTS.
 }}}

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

Re: [Django] #23810: Passing 'start' from django url gives error “start() takes exactly 2 arguments (1 given) ”

2014-11-13 Thread Django

#23810: Passing 'start' from django url gives error “start() takes exactly 2
arguments (1 given) ”
-+--
 Reporter:  yogeshdmca   |Owner:  yogesh
 Type:  Bug  |   Status:  closed
Component:  Core (URLs)  |  Version:  1.6
 Severity:  Normal   |   Resolution:  worksforme
 Keywords:  django-url   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by claudep):

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


Comment:

 Please, try first wiki:TicketClosingReasons/UseSupportChannels and open a
 ticket only if your problem is due to a bug in Django itself.

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

Re: [Django] #23809: Update Localflavor docs

2014-11-13 Thread Django

#23809: Update Localflavor docs
-+-
 Reporter:  shabda   |Owner:  shabda
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.7
Component:  Documentation|   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 I think it would be better to remove this page as we've done with other
 contrib apps that have been removed (like `comments`) and create a new
 page that includes a list of all the apps that live under the "django"
 GitHub umbrella. Care to create a ticket for that?

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

40 matches

Mail list logo