date:20160315

[Django] #26361: Template Filter for loop with range

2016-03-15 Thread Django

#26361: Template Filter for loop with range
-+
 Reporter:  the-kid89|  Owner:  nobody
 Type:  Uncategorized| Status:  new
Component:  Template system  |Version:  1.9
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 I propose a filter be added to make a template for loop from a range. This
 could look something like this {% for _ in 5|range %}. It seems to me that
 something like this should already be in the template language for Django
 already. This would be added to "django/template/defaultfilters.py"

 The code for something like this could be as follows


 {{{
 @register.filter(is_safe=False)
 @stringfilter
 def range(value):
 """
 Returns a list the length of the value

 Will cast a string to an int
 """
 return list(range(int(value)))
 }}}

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

Re: [Django] #26359: explain dual ticket tracking system

2016-03-15 Thread Django

* needs_better_patch: => 0
* needs_docs: => 0
* component: Uncategorized => Documentation
* needs_tests: => 0
* stage: Unreviewed => Accepted

Comment:

There aren't any *tickets* on GitHub - we've disabled the Issues feature
on our Github account. However, we do accept Pull Requests on GitHub,
which have a number that is very similar to a ticket.

So, if you're reporting a problem, you need to use Trac; when you submit a
pull request, that PR will be given a number, and that number should
reference the Trac issue number.

I know this is a bit confusing, so improved documentation is definitely a
good idea. The source of the problem is that GitHub's ticket system isn't
practical for a large project like Django, and we had a legacy of 2
tickets in Trac (many of which had a significant history) that couldn't be
imported into GitHub when we moved our repository there.

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

--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.725823f55dea235c913ebb1d4555dce4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26360: add section on testing to django tutorial

2016-03-15 Thread Django

#26360: add section on testing to django tutorial
---+
 Reporter:  beckastar  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.9
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 No app is complete without testing, and most beginner materials leave this
 out.  This is a great place to introduce this concept as an optional
 additional unit.

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

[Django] #26359: explain dual ticket tracking system

2016-03-15 Thread Django

#26359: explain dual ticket tracking system
---+
 Reporter:  beckastar  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.9
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 The contribution documents at
 https://docs.djangoproject.com/en/1.9/internals/contributing/ link to the
 Trac system for creating tickets.

 I was confused when the first ticket I made was a duplicate of an issue on
 Github.

 It would be very helpful to explain that there are also tickets on GH and
 why (legacy? I'm new here) and how to check for dupes.  Is there a
 preference for what gets reported where? Please explain this to make it
 more n00b friendly. 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/052.99087b9f57421b79fce47debe52b599c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26290: Pagination module should warn about unordered query set

2016-03-15 Thread Django

#26290: Pagination module should warn about unordered query set
--+
 Reporter:  kartikanand   |Owner:  duane9
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  pagination| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by duane9):

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

Re: [Django] #26290: Pagination module should warn about unordered query set

2016-03-15 Thread Django

#26290: Pagination module should warn about unordered query set
--+
 Reporter:  kartikanand   |Owner:  duane9
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  pagination| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by duane9):

 Okay, I will do that. I will have it done in two weeks.

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

Re: [Django] #23155: Add request attr to user_login_failed signal

2016-03-15 Thread Django

#23155: Add request attr to user_login_failed signal
--+
 Reporter:  anonymous |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by timgraham):

 What I meant about a separate ticket for a deprecation to make `request` a
 required argument for authentication backends is something like this in
 `authenticate()`:
 {{{ #!python
 try:
 inspect.getcallargs(backend.authenticate, request, **credentials)
 except TypeError:
 try:
 inspect.getcallargs(backend.authenticate, **credentials)
 except TypeError:
 # This backend doesn't accept these credentials as arguments. Try
 the next one.
 continue
 else:
 warnings.warn(
 "Update authentication backend %s to accept a "
 "positional `request` argument." % backend
 RemovedInDjango20Warning
 )
 }}}

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

Re: [Django] #26358: link in new contributor guide is unclear and needs some improvements

2016-03-15 Thread Django

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

Comment:

1. I don't see the quoted text -- closest is "Report bugs with Django or
Django documentation in our ticket tracker" in the sidebar. Is that what
you meant? There is a section "Write some documentation" on the new
contributors page with links to some guidelines. Please clarify what you
found confusing. It might be a case where removing some duplicated
information is better than adding more information.

2. This issue is tracked in
https://github.com/django/djangoproject.com/issues/533.

As an aside for future reference, please try to limit each ticket to one
item, otherwise it's difficult to see what has been done and what still
needs to be done.

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

Re: [Django] #26357: 'related-lookup' and 'add-another' popups don't work for admin fields added via ajax

2016-03-15 Thread Django

#26357: 'related-lookup' and 'add-another' popups don't work for admin fields 
added
via ajax
-+-
 Reporter:  julianandrews|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin javascript | Triage Stage:  Accepted
  ajax   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-

Comment (by timgraham):

 Sure, some documented guidelines wouldn't hurt.

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

Re: [Django] #26347: Saving ManyToMany field under race condition causes data loss

2016-03-15 Thread Django

#26347: Saving ManyToMany field under race condition causes data loss
-+-
 Reporter:  hchargois|Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  mysql transaction| Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by cristianocca):

 The UI fix would be too basic, the race condition (if really an issue)
 would be still there by using multiple users or even tabs...

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

[Django] #26358: link in new contributor guide is unclear and needs some improvements

2016-03-15 Thread Django

#26358: link in new contributor guide is unclear and needs some improvements
--+---
 Reporter:  beckastar |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Uncategorized |Version:  1.9
 Severity:  Normal|   Keywords:  documentation
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+---
 On this page: https://docs.djangoproject.com/en/1.9/internals/contributing
 /new-contributors/

 "Report bugs in our ticket tracker."

 "Report bugs" brings you to the page on bug reporting.  It would be useful
 to include a description of standards for improving and reorganizing
 documentation.

 "ticket tracker' links to this page:
 https://code.djangoproject.com/newticket. It's  behind a login, and could
 be confusing.  Instead, include instructions for creating an account via
 github or by creating an account.

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

Re: [Django] #23155: Add request attr to user_login_failed signal

2016-03-15 Thread Django

#23155: Add request attr to user_login_failed signal
--+
 Reporter:  anonymous |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by gavinwahl):

 I'm unsure how to continue. What is the desired change?

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

Re: [Django] #23155: Add request attr to user_login_failed signal

2016-03-15 Thread Django

#23155: Add request attr to user_login_failed signal
--+
 Reporter:  anonymous |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.auth  |  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 gavinwahl):

 * cc: gavinwahl+gh@… (added)


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

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

Re: [Django] #26290: Pagination module should warn about unordered query set

2016-03-15 Thread Django

#26290: Pagination module should warn about unordered query set
--+
 Reporter:  kartikanand   |Owner:  duane9
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  pagination| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by claudep):

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


Comment:

 Was the runtime warning excluded somewhere? I still think it might be a
 good idea.

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

Re: [Django] #26297: collectstatic --clear throws NotImplementedError, "This backend doesn't support absolute paths."

2016-03-15 Thread Django

#26297: collectstatic --clear throws NotImplementedError, "This backend doesn't
support absolute paths."
-+-
 Reporter:  topher86 |Owner:
 |  berkerpeksag
 Type:  Bug  |   Status:  assigned
Component:  contrib.staticfiles  |  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:  clear| Triage Stage:  Ready for
  notimplementederror path   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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

Re: [Django] #25364: Provide a more generic way to test different browsers in selenium tests

2016-03-15 Thread Django

#25364: Provide a more generic way to test different browsers in selenium tests
-+-
 Reporter:  timgraham|Owner:  akki
 Type:  New feature  |   Status:  closed
Component:  Testing framework|  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 Simon Charette ):

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


Comment:

 In [changeset:"44c0ecdd9226d039a8c666b36ae320af2046a1c1" 44c0ecdd]:
 {{{
 #!CommitTicketReference repository=""
 revision="44c0ecdd9226d039a8c666b36ae320af2046a1c1"
 Fixed #25364 -- Added generic way to test on all browsers supported by
 selenium.

 Browser names should be passed as a comma separated list to the --selenium
 flag.

 Thanks Tim Graham, Simon Charette and Moritz Sichert for review and
 discussion.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.6c25f0f5bee77350d375f0693baee8b1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26357: 'related-lookup' and 'add-another' popups don't work for admin fields added via ajax

2016-03-15 Thread Django

Comment (by julianandrews):

@timgraham: I've gone ahead and added comments.

I agree that maintaining future support for the use case would be nice,
but I'm not sure exactly what that would look like. Given how common ajax
and dynamic page content is now, it's probably a good practice to avoid
writing javascript that assumes a static page structure. Maybe a line to
that effect could be added to
https://docs.djangoproject.com/en/dev/internals/contributing/writing-
code/javascript/?

In any case, Fusionbox relies on ajax in the admin somewhat heavily so
we're likely to catch inadvertent breakage down the line and send PRs.

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

Re: [Django] #24932: Add Cast database function

2016-03-15 Thread Django

#24932: Add Cast database function
-+-
 Reporter:  Ian-Foote|Owner:
 Type:  New feature  |   Status:  new
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:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_better_patch:  0 => 1


Comment:

 (waiting for #25759 to merge before tweaking this a bit)

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

Re: [Django] #26357: 'related-lookup' and 'add-another' popups don't work for admin fields added via ajax

2016-03-15 Thread Django

* type: Uncategorized => Cleanup/optimization
* stage: Unreviewed => Accepted

Comment:

The main concern I have is how to ensure the admin continues to support
such use cases in the future. I guess we can say "no tests = no official
support" and you can continue sending PRs in the future if things
inadvertently break? At least you might want to add a comment about it so
someone doesn't "cleanup" the code to the old version.

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

Re: [Django] #26158: cookie parsing fails with python 3.x if request contains unnamed cookie

2016-03-15 Thread Django

#26158: cookie parsing fails with python 3.x if request contains unnamed cookie
-+-
 Reporter:  Treverix |Owner:  timgraham
 Type:  Bug  |   Status:  closed
Component:  HTTP handling|  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  cookie python3   | 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 Tim Graham ):

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


Comment:

 In [changeset:"93a135d111c2569d88d65a3f4ad9e6d9ad291452" 93a135d]:
 {{{
 #!CommitTicketReference repository=""
 revision="93a135d111c2569d88d65a3f4ad9e6d9ad291452"
 Fixed #26158 -- Rewrote http.parse_cookie() to better match browsers.
 }}}

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

Re: [Django] #26357: 'related-lookup' and 'add-another' popups don't work for admin fields added via ajax

2016-03-15 Thread Django

#26357: 'related-lookup' and 'add-another' popups don't work for admin fields 
added
via ajax
-+-
 Reporter:  julianandrews|Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin javascript | Triage Stage:
  ajax   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by julianandrews):

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


Comment:

 I've created a patch here:
 https://github.com/fusionbox/django/tree/ticket_26357

 It's a fairly simple fix, but since I can see arguments against this
 approach, I've held off on making a PR directly. If I get the go ahead,
 I'll make a PR on this 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/071.f2a3ec69559f79308b2ce8fb1e6af98f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26357: 'related-lookup' and 'add-another' popups don't work for admin fields added via ajax

2016-03-15 Thread Django

#26357: 'related-lookup' and 'add-another' popups don't work for admin fields
added
via ajax
---+---
Reporter: julianandrews | Owner: nobody
Type: Uncategorized | Status: new
Component: contrib.admin |Version: master
Severity: Normal | Keywords: admin javascript ajax
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 1
---+---
If a field with a `'related-lookup'` or `'add-another'` link is added
after page load (for instance via ajax), the javascript event handler
which causes these links to open a pop-up doesn't get attached to the new
links. Instead of opening a pop-up window to allow selection of the
related object, the links simply send the user to the list page for the
object.

As a result ajax generated admin fields don't work correctly. While this
doesn't break the Django admin itself, it does make extending the admin
with Ajax difficult.

An easy fix is to attach the `'related-lookup'` and `'add-another'`
`click` events to `document` instead of to the links themselves. This
would come at a small performance cost since the events will be triggered
on every click instead of just on link click, but with modern javascript
engines I think the cost would be unnoticeable, and given how unobtrusive
this change is I think the added flexibility justifies the cost.

I'll attach a PR for the proposed fix after I submit this report.

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

--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/056.1b0260dbb309ff3f2a272d9e1a4ce4d3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25251: Inconsistent availability of data migrations in TransactionTestCase when using --keepdb

2016-03-15 Thread Django

#25251: Inconsistent availability of data migrations in TransactionTestCase when
using --keepdb
---+
 Reporter:  davidszotten   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.8
 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 timgraham):

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

Re: [Django] #26351: Recommend enabling MySQL's STRICT_TRANS_TABLES to prevent silent truncation

2016-03-15 Thread Django

#26351: Recommend enabling MySQL's STRICT_TRANS_TABLES to prevent silent 
truncation
-+-
 Reporter:  zhebrak  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:  get_or_create,   | Triage Stage:  Accepted
  max_length |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by mdunhem):

 Should we also add a note in the 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/065.c9ffc49a6d182492a0f8e066cce9c137%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26356: Allow management commands to require tagged checks

2016-03-15 Thread Django

#26356: Allow management commands to require tagged checks
-+-
 Reporter:  julen|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  system checks| Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by julen):

 Thanks for the pointer, and no problem — we'll see if our need extends to
 the point we have to bring it up in the mailing list. Thanks again for the
 quick interaction!

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

Re: [Django] #25579: Lack of type adaptation in ArrayField querying/lookups

2016-03-15 Thread Django

#25579: Lack of type adaptation in ArrayField querying/lookups
-+-
 Reporter:  freshquiz|Owner:  freshquiz
 Type:  Bug  |   Status:  closed
Component:  contrib.postgres |  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  ArrayField query | Triage Stage:  Accepted
  lookup |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"e7e5d9b338cabaafc61b7a0c55ff395b533d8c9e" e7e5d9b3]:
 {{{
 #!CommitTicketReference repository=""
 revision="e7e5d9b338cabaafc61b7a0c55ff395b533d8c9e"
 Fixed #25579 -- Fixed ArrayField.get_db_prep_value() to allow complex
 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/067.9c881149f227c87a9bb5fc9678e580e4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26158: cookie parsing fails with python 3.x if request contains unnamed cookie

2016-03-15 Thread Django

#26158: cookie parsing fails with python 3.x if request contains unnamed cookie
-+-
 Reporter:  Treverix |Owner:  timgraham
 Type:  Bug  |   Status:  assigned
Component:  HTTP handling|  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  cookie python3   | 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 timgraham):

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

Re: [Django] #26356: Allow management commands to require tagged checks

2016-03-15 Thread Django

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

Comment:

As [https://docs.djangoproject.com/en/dev/topics/checks/ the
documentations says], "The system check framework is a set of static
checks for validating Django projects."

Therefore, I feel your use case of checks that deal with objects in the
database is really outside the scope of the intended use of the checks
framework. If you'd like to raise a wider discussion about it and see if
anyone else supports expanding it, feel free to post to the
DevelopersMailingList.

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

Re: [Django] #26356: Allow management commands to require tagged checks

2016-03-15 Thread Django

Comment (by julen):

Thanks for the quick reply :)

Yeah, I'm aware of `requires_system_checks`.

Our use-case is that some of our system checks deal with existing DB data
and they assume such data is there, however some other commands might be
run before the DB is setup (`migrate`, and other related custom commands).
For now we are catching potential exceptions in our checks' code, and
hence it'd be sweet if we could just omit running such checks for certain
commands in the first place as we have them tagged.

We could override `BaseCommand.execute()` or `BaseCommand.check()`, but
this feels clumsy and error-prone. On the other hand, `BaseCommand` could
potentially read the tags to be checked from e.g.
`BaseCommand.requires_system_check_tags` and this would be AFAICT roughly
a single-line change in Django and our management 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/063.2a0690ae9c552983d7561074c83c3b7d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26352: models.E003 check incorrectly prevents duplicate ManyToMany through-self that differ by through_fields

2016-03-15 Thread Django

#26352: models.E003 check incorrectly prevents duplicate ManyToMany through-self
that differ by through_fields
-+-
 Reporter:  simonw   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 In absence of a reported use case, I don't mind closing the issue for now.

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

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

Re: [Django] #26355: Add support for PostgreSQL's array_append to ArrayField (was: Postgres ArrayField append)

2016-03-15 Thread Django

#26355: Add support for PostgreSQL's array_append to ArrayField
--+
 Reporter:  graup |Owner:
 Type:  New feature   |   Status:  new
Component:  contrib.postgres  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * stage:  Unreviewed => Accepted


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.91b32a2b41107cb538a27e39d0b23703%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26290: Pagination module should warn about unordered query set

2016-03-15 Thread Django

#26290: Pagination module should warn about unordered query set
--+
 Reporter:  kartikanand   |Owner:  duane9
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:  pagination| Triage Stage:  Accepted
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:"f8b23e52e86307428da2cf928bf4f1d9fdbd2694" f8b23e5]:
 {{{
 #!CommitTicketReference repository=""
 revision="f8b23e52e86307428da2cf928bf4f1d9fdbd2694"
 Fixed #26290 -- Documented that a QuerySet for pagination should be
 ordered.
 }}}

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

Re: [Django] #26290: Pagination module should warn about unordered query set

2016-03-15 Thread Django

#26290: Pagination module should warn about unordered query set
--+
 Reporter:  kartikanand   |Owner:  duane9
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:  pagination| 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:"0dc3822f56a0db83f9fc0b1ed320bbeb477eca63" 0dc3822f]:
 {{{
 #!CommitTicketReference repository=""
 revision="0dc3822f56a0db83f9fc0b1ed320bbeb477eca63"
 [1.9.x] Fixed #26290 -- Documented that a QuerySet for pagination should
 be ordered.

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

Re: [Django] #26356: Allow management commands to require tagged checks

2016-03-15 Thread Django

#26356: Allow management commands to require tagged checks
-+-
 Reporter:  julen|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  system checks| 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):

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


Comment:

 There's the `BaseCommand.requires_system_checks` attribute. What's your
 use case for wanting some checks but not all?

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

[Django] #26356: Allow management commands to require tagged checks

2016-03-15 Thread Django

#26356: Allow management commands to require tagged checks
+---
 Reporter:  julen   |  Owner:  nobody
 Type:  New feature | Status:  new
Component:  Core (Management commands)  |Version:  master
 Severity:  Normal  |   Keywords:  system checks
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+---
 It would be handy if management commands could opt-in for specific groups
 of system checks, as these can already be labeled.

 As I read through the source code, making this change would be trivial
 (`BaseCommand.check()` already supports tags), so I wonder if such a
 feature would be accepted by core devs. TIA!

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

Re: [Django] #25774: Refactor of datetime expressions and better, official support for right-hand-side date part extraction

2016-03-15 Thread Django

#25774: Refactor of datetime expressions and better, official support for right-
hand-side date part extraction
-+-
 Reporter:  ryuusenshi   |Owner:  jarshwah
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  db,expressions,date,time,extract,transform|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * stage:  Ready for checkin => Accepted


Comment:

 The review queue is "Accepted + Has 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/068.59cff1fc30bf86369202607ea8a86c66%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26355: Postgres ArrayField append

2016-03-15 Thread Django

#26355: Postgres ArrayField append
--+--
 Reporter:  graup |Owner:
 Type:  New feature   |   Status:  new
Component:  contrib.postgres  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by graup):

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


Old description:

> I am using an ArrayField to store a list of dates. I would like to use
> `update()` to add a value to the list, only if the list doesn't contain
> it already.
>
> The `contains` part is already supported by Django, but not the
> `array_append`.
>
> http://www.postgresql.org/docs/9.1/static/arrays.html#ARRAYS-MODIFYING
>
> Eventually I'd like to be able to do something like this:
>
> `User.objects.exclude(active_in__contains=[current_month]).update(active_in=F('active_in')
> + [current_month])`
>
> which should result in this SQL:
>
> `UPDATE user_user SET active_in = array_append(active_in, [%s]) WHERE
> NOT(active_in @> ARRAY[%s]::varchar[])  ['2012-01']`
>
> PS: I want to use `update` instead of `get()` and `save()` for
> performance reasons.

New description:

 I am using an ArrayField to store a list of dates. I would like to use
 `update()` to add a value to the list, only if the list doesn't contain it
 already.

 The `contains` part is already supported by Django, but not the
 `array_append`.

 http://www.postgresql.org/docs/9.1/static/arrays.html#ARRAYS-MODIFYING

 Eventually I'd like to be able to do something like this:

 
`User.objects.exclude(active_in__contains=[current_month]).update(active_in=F('active_in')
 + [current_month])`

 which should result in this SQL:

 `UPDATE user_user SET active_in = array_append(active_in, [%s]) WHERE
 NOT(active_in @> ARRAY[%s]::varchar[])  ['2012-01']`

 PS: I want to use `update` instead of `get()` and `save()` for performance
 reasons.

 I want to add that in this particular use case I can get around using it
 (because I already have the user object anyway), but it would nevertheless
 be nice of have this feature, I think.

--

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

[Django] #26355: Postgres ArrayField append

2016-03-15 Thread Django

#26355: Postgres ArrayField append
--+-
 Reporter:  graup |  Owner:
 Type:  New feature   | Status:  new
Component:  contrib.postgres  |Version:  1.9
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+-
 I am using an ArrayField to store a list of dates. I would like to use
 `update()` to add a value to the list, only if the list doesn't contain it
 already.

 The `contains` part is already supported by Django, but not the
 `array_append`.

 http://www.postgresql.org/docs/9.1/static/arrays.html#ARRAYS-MODIFYING

 Eventually I'd like to be able to do something like this:

 
`User.objects.exclude(active_in__contains=[current_month]).update(active_in=F('active_in')
 + [current_month])`

 which should result in this SQL:

 `UPDATE user_user SET active_in = array_append(active_in, [%s]) WHERE
 NOT(active_in @> ARRAY[%s]::varchar[])  ['2012-01']`

 PS: I want to use `update` instead of `get()` and `save()` for performance
 reasons.

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

Re: [Django] #25774: Refactor of datetime expressions and better, official support for right-hand-side date part extraction

2016-03-15 Thread Django

#25774: Refactor of datetime expressions and better, official support for right-
hand-side date part extraction
-+-
 Reporter:  ryuusenshi   |Owner:  jarshwah
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
  db,expressions,date,time,extract,transform|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by jarshwah):

 * needs_docs:  1 => 0
 * needs_tests:  1 => 0
 * stage:  Accepted => Ready for checkin


Comment:

 Patch is ready for review.

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

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

Re: [Django] #26351: Recommend enabling MySQL's STRICT_TRANS_TABLES to prevent silent truncation

2016-03-15 Thread Django

#26351: Recommend enabling MySQL's STRICT_TRANS_TABLES to prevent silent 
truncation
-+-
 Reporter:  zhebrak  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:  get_or_create,   | Triage Stage:  Accepted
  max_length |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by adamchainz):

 * cc: me@… (added)


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

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

Re: [Django] #26354: DEBUG = False problem

2016-03-15 Thread Django

#26354: DEBUG = False problem
---+--
 Reporter:  RaminFP|Owner:
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.9
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by MoritzS):

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


Comment:

 This is the bug tracker for the development of django itself, for support
 question you can use the [https://docs.djangoproject.com/en/1.9/internals
 /mailing-lists/ django-users mailing list], or #django on freenode.
 Maybe [https://docs.djangoproject.com/en/1.9/howto/error-reporting/ this]
 is related to your 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/065.879936815f9e086c0885c1f0c19308b5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26354: DEBUG = False problem

2016-03-15 Thread Django

#26354: DEBUG = False problem
---+-
 Reporter:  RaminFP|  Owner:
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.9
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+-
 Hi,

 i have one question , why DEBUG in settings.py other time work and other
 time not work for custome errors ,

 i use DEBUG = False not work for me return bad request (400) can not show
 my page URLS on urls.py ,  but i use DEBUG= True work it, also i set
 ALLOW_HOSTS = ['*']

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

Re: [Django] #25579: Lack of type adaptation in ArrayField querying/lookups

2016-03-15 Thread Django

#25579: Lack of type adaptation in ArrayField querying/lookups
-+-
 Reporter:  freshquiz|Owner:  freshquiz
 Type:  Bug  |   Status:  assigned
Component:  contrib.postgres |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  ArrayField query | Triage Stage:  Accepted
  lookup |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by freshquiz):

 * needs_better_patch:  1 => 0


Comment:

 Deleted `TagField.get_db_prep_value()`, but didn't add any new tests,
 because one of the tests from
 
[https://github.com/django/django/commit/2495023a4cae28f494d0a6172abfac3a47a0b816]
 failed after deleting that method (as I said it would).

 I also took a different approach to solving it, re-using existing code as
 much as possible.

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

Re: [Django] #25321: Make it clear that django.db.backends.schema messages (which can propogate to django.db.backends) don't include 'duration'

2016-03-15 Thread Django

#25321: Make it clear that django.db.backends.schema messages (which can 
propogate
to django.db.backends) don't include 'duration'
-+-
 Reporter:  netpositive36|Owner:  MarkusH
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  logging, db  | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  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:"1cb65b8a77bd1b15f094b5857468c107784aad90" 1cb65b8a]:
 {{{
 #!CommitTicketReference repository=""
 revision="1cb65b8a77bd1b15f094b5857468c107784aad90"
 Fixed #26157 #25321 -- Added sql/params to extra context of schema logger

 Thanks Akshesh Doshi for the initial patch and Tim Graham for the review
 }}}

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

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

Re: [Django] #26157: Unify database loggers to use same log record API

2016-03-15 Thread Django

#26157: Unify database loggers to use same log record API
-+-
 Reporter:  MarkusH  |Owner:  MarkusH
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  logging  | 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 Markus Holtermann ):

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


Comment:

 In [changeset:"1cb65b8a77bd1b15f094b5857468c107784aad90" 1cb65b8a]:
 {{{
 #!CommitTicketReference repository=""
 revision="1cb65b8a77bd1b15f094b5857468c107784aad90"
 Fixed #26157 #25321 -- Added sql/params to extra context of schema logger

 Thanks Akshesh Doshi for the initial patch and Tim Graham for the review
 }}}

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

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

45 matches

Mail list logo