date:20150619

Re: [Django] #25009: create_user(..., is_staff=True) raises TypeError multiple values for keyword argument 'is_staff'

2015-06-19 Thread Django

#25009: create_user(..., is_staff=True) raises TypeError multiple values for
keyword argument 'is_staff'
--+
 Reporter:  allcaps   |Owner:  pahko
 Type:  Bug   |   Status:  assigned
Component:  contrib.auth  |  Version:  1.8
 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 pahko):

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

Re: [Django] #25009: create_user(..., is_staff=True) raises TypeError multiple values for keyword argument 'is_staff'

2015-06-19 Thread Django

#25009: create_user(..., is_staff=True) raises TypeError multiple values for
keyword argument 'is_staff'
--+
 Reporter:  allcaps   |Owner:  pahko
 Type:  Bug   |   Status:  assigned
Component:  contrib.auth  |  Version:  1.8
 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 pahko):

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

Re: [Django] #25009: create_user(..., is_staff=True) raises TypeError multiple values for keyword argument 'is_staff'

2015-06-19 Thread Django

#25009: create_user(..., is_staff=True) raises TypeError multiple values for
keyword argument 'is_staff'
--+
 Reporter:  allcaps   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by allcaps):

 Seems like we can have a cheeseburger without cheese :). Forgiveness is
 cool. But we can also raise an error for the superuser.

 {{{
 def create_user(self, username, email=None, password=None,
 **extra_fields):
 extra_fields.setdefault('is_staff', False)
 extra_fields.setdefault('is_superuser', False)
 return self._create_user(username, email, password, **extra_fields)

 def create_superuser(self, username, email, password, **extra_fields):
 if extra_fields.has_key('is_staff') and extra_fields.get('is_staff')
 is False:
 raise ValueError('Superuser needs to be staff. Do not set
 `is_staff`.')
 if extra_fields.has_key('is_superuser') and
 extra_fields.get('is_superuser') is False:
 raise ValueError('Superuser needs to be superuser. Do not set
 `is_superuser`.')
 extra_fields.setdefault('is_staff', True)
 extra_fields.setdefault('is_superuser', True)
 return self._create_user(username, email, password, **extra_fields)
 }}}

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

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

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

2015-06-19 Thread Django

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

 * has_patch:  0 => 1


Comment:

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

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

Re: [Django] #24985: Provide a way to sanitize invalid characters from Rss201rev2Feed

2015-06-19 Thread Django

Comment (by claudep):

Proposal for a documentation addition:

{{{
#!diff
diff --git a/docs/ref/contrib/syndication.txt
b/docs/ref/contrib/syndication.txt
index 6c86be0..940123c 100644
--- a/docs/ref/contrib/syndication.txt
+++ b/docs/ref/contrib/syndication.txt
@@ -919,7 +919,10 @@ They share this interface:
``self.feed`` for use with `custom feed generators`_.

All parameters should be Unicode objects, except ``categories``,
which
-should be a sequence of Unicode objects.
+should be a sequence of Unicode objects. Beware that some control
characters
+are `not allowed `_
+in XML documents. If your content has some of them, you might
encounter a
+:exp:`ValueError` when producing the feed.

:meth:`.SyndicationFeed.add_item`
Add an item to the feed with the given parameters.
}}}

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

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

2015-06-19 Thread Django

#25005: DateField, DateTimeField defaults needed even when auto_now=True
-+-
 Reporter:  monobotsoft  |Owner:  coldmind
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  DateField,   | Triage Stage:  Accepted
  DateTimeField  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by coldmind):

 So, seems there changes in `effective_default` are needed, so I'm going
 this way

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

Re: [Django] #25009: create_user(..., is_staff=True) raises TypeError multiple values for keyword argument 'is_staff'

2015-06-19 Thread Django

#25009: create_user(..., is_staff=True) raises TypeError multiple values for
keyword argument 'is_staff'
--+
 Reporter:  allcaps   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  1.8
 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 bmispelon):

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


Comment:

 I can indeed reproduce the issue.

 Interestingly, prior to cab333cb16656cbb7d2bcfb06b2f7aeab9bac7af (which
 landed in 1.6), doing `User.objects.create_user(..., is_staff=True)`
 actually worked, but `User.objects.create_superuser(..., is_staff=False)`
 would raise a similar error to what we have now.

 I think the fix should be to allow these parameters to be passed. It can
 lead to weird code like `User.objects.create_superuser(...,
 is_superuser=False)` but I don't think we should code against that.

 The fix is then quite straighforward:
 {{{#!python
 def create_user(self, username, email=None, password=None,
 **extra_fields):
 extra_fields.setdefault('is_staff', False)
 extra_fields.setdefault('is_superuser', False)
 return self._create_user(username, email, password,
 **extra_fields)

 def create_superuser(self, username, email, password, **extra_fields):
 extra_fields.setdefault('is_staff', True)
 extra_fields.setdefault('is_superuser', True)
 return self._create_user(username, email, password,
 **extra_fields)
 }}}

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

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

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

2015-06-19 Thread Django

#25005: DateField, DateTimeField defaults needed even when auto_now=True
-+-
 Reporter:  monobotsoft  |Owner:  coldmind
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  DateField,   | Triage Stage:  Accepted
  DateTimeField  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by coldmind):

 Changing autodetector is not a problem.
 But...
 When we have some model, then adding DateField or DateTimeField with
 auto_now/auto_now_add, and disable promting for default, it throws
 integrity errors for null. So seems it not works on existing objects. Is
 that normal behavior or it is 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.499f719d61e9106d177dc575bc140c37%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

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

2015-06-19 Thread Django

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

 * owner:  nobody => coldmind
 * status:  new => assigned
 * 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/069.597e6142a4dc59d663b10b38d60541db%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

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

2015-06-19 Thread Django

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

 * Attachment "ticket_25005.patch" added.

 Tests to reproduce the 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/069.22a39c925daf53a4df871ccede413fd2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #25009: create_user(..., is_staff=True) raises TypeError multiple values for keyword argument 'is_staff'

2015-06-19 Thread Django

#25009: create_user(..., is_staff=True) raises TypeError multiple values for
keyword argument 'is_staff'
--+
 Reporter:  allcaps   |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  contrib.auth  |Version:  1.8
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+
 When I do:

 {{{
 >>> from django.contrib.auth.models import User
 >>> user = User.objects.create_user('test', email='t...@example.com',
 password='password', is_staff=True)
 Traceback (most recent call last):
   File "", line 1, in 
   File "/Users/coen/git/prive/tvdordrecht.nl/env/lib/python2.7/site-
 packages/django/contrib/auth/models.py", line 183, in create_user
 **extra_fields)
 TypeError: _create_user() got multiple values for keyword argument
 'is_staff'
 }}}

 Expected:

 {{{
 >>> user.is_staff
 True
 }}}

 From StackOverflow:
 http://stackoverflow.com/questions/30711544/create-staff-user-in-
 django/30946633#30946633


 Related
 
https://github.com/bak1an/django/commit/dc2f67679712412e2f8bdfbecc340f796d6dbc24
 https://code.djangoproject.com/ticket/20541

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

Re: [Django] #25008: Replace F() Object with updated value after save method is called

2015-06-19 Thread Django

#25008: Replace F() Object with updated value after save method is called
-+-
 Reporter:  aykut|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  F Object | 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:   => duplicate


Comment:

 Duplicate of #23386

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

Re: [Django] #25008: Replace F() Object with updated value after save method is called (was: New value should be replaced with F() Object after save method is called)

2015-06-19 Thread Django

#25008: Replace F() Object with updated value after save method is called
-+-
 Reporter:  aykut|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  F Object | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aykut):

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

[Django] #25008: New value should be replaced with F() Object after save method is called

2015-06-19 Thread Django

#25008: New value should be replaced with F() Object after save method is called
--+--
 Reporter:  aykut |  Owner:  nobody
 Type:  New feature   | Status:  new
Component:  Database layer (models, ORM)  |Version:  master
 Severity:  Normal|   Keywords:  F Object
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+--
 It is dirty and annoying to reload the new object, every time `F()` is
 used.

 So replacing fields expressed by `F()` with the updated values just like
 having `id` when you create objects, would be very useful.

 I think it will be possible on Oracle and PostgreSQL, since only they
 support `RETURNING`. However it is still a cool feature to have.

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

Re: [Django] #20197: XML serializer can output invalid characters

2015-06-19 Thread Django

#20197: XML serializer can output invalid characters
-+-
 Reporter:  ris  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Core |  Version:  1.3
  (Serialization)|
 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 Claude Paroz ):

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


Comment:

 In [changeset:"9368f51e1273c56ca40e396ef5a1aa0aa7c91871" 9368f51e]:
 {{{
 #!CommitTicketReference repository=""
 revision="9368f51e1273c56ca40e396ef5a1aa0aa7c91871"
 Fixed #20197 -- Made XML serializer fail loudly when outputting
 unserializable chars

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

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

2015-06-19 Thread Django

#25005: DateField, DateTimeField defaults needed even when auto_now=True
-+-
 Reporter:  monobotsoft  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  DateField,   | Triage Stage:  Accepted
  DateTimeField  |
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/069.98ee7665ff81c6cd462a1b4c1bec0a00%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #20197: XML serializer can output invalid characters

2015-06-19 Thread Django

#20197: XML serializer can output invalid characters
-+-
 Reporter:  ris  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core |  Version:  1.3
  (Serialization)|
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * component:  Documentation => Core (Serialization)
 * 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/061.c5e8ea988f2d178d22ab65f851caabe5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25006: Allow for custom Time shortcut in DateTimeShortCuts.js

2015-06-19 Thread Django

#25006: Allow for custom Time shortcut in DateTimeShortCuts.js
---+--
 Reporter:  RamezIssac |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  1.8
 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
---+--

Comment (by timgraham):

 I'm not too familiar with that code. If it's not much work could you
 implement your suggestion and send a pull request so I can better
 understand 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/068.e5f639f7f8e36dfcd8f84ca0351218cc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23804: Add a RasterField to GeoDjango

2015-06-19 Thread Django

#23804: Add a RasterField to GeoDjango
-+-
 Reporter:  yellowcap|Owner:  yellowcap
 Type:  New feature  |   Status:  closed
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  raster gdal  | 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:"b769bbd4f6a3cd1bcd9ebf3559ec6ea0f9b50565" b769bbd4]:
 {{{
 #!CommitTicketReference repository=""
 revision="b769bbd4f6a3cd1bcd9ebf3559ec6ea0f9b50565"
 Fixed #23804 -- Added RasterField for PostGIS.

 Thanks to Tim Graham and Claude Paroz for the reviews and patches.
 }}}

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

Re: [Django] #23804: Add a RasterField to GeoDjango

2015-06-19 Thread Django

#23804: Add a RasterField to GeoDjango
-+-
 Reporter:  yellowcap|Owner:  yellowcap
 Type:  New feature  |   Status:  assigned
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  raster gdal  | 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):

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


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

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

Re: [Django] #25007: UUIDFIeld(default=uuid.uuid4) created with migrations are the same

2015-06-19 Thread Django

#25007: UUIDFIeld(default=uuid.uuid4) created with migrations are the same
-+-
 Reporter:  afg984   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.8
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  migrations, uuid,| Triage Stage:
  UUIDField  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by afg984):

 sorry for that, should have read 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/064.aef114837b719ea3ba612ae7cb298a3f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25007: UUIDFIeld(default=uuid.uuid4) created with migrations are the same

2015-06-19 Thread Django

#25007: UUIDFIeld(default=uuid.uuid4) created with migrations are the same
-+-
 Reporter:  afg984   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.8
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  migrations, uuid,| Triage Stage:
  UUIDField  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 Please see [https://docs.djangoproject.com/en/1.8/howto/writing-migrations
 /#migrations-that-add-unique-fields how to write migrations that add
 unique fields].

 #23408 suggests to add a warning to `makemigrations` for this case.

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

[Django] #25007: UUIDFIeld(default=uuid.uuid4) created with migrations are the same

2015-06-19 Thread Django

#25007: UUIDFIeld(default=uuid.uuid4) created with migrations are the same
+-
 Reporter:  afg984  |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  1.8
 Severity:  Normal  |   Keywords:  migrations, uuid, UUIDField
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+-
 Steps to reproduce:

 1. Create model
 {{{#!python
 class Bar(models.Model):
 pass
 }}}

 2. makemigrations & migrate

 3. Create some Bar()s in the database
 {{{#!python
 >>> Bar.objects.create()
 
 >>> Bar.objects.create()
 
 >>> Bar.objects.create()
 
 >>> Bar.objects.create()
 
 }}}

 4. Add a UUIDField
 {{{#!python
 class Bar(models.Model):
 uu = models.UUIDField(default=uuid.uuid4)
 }}}

 5. makemigrations & migrate

 if I use `unique=True` in the previous step, `./manage.py migrate` gives
 me:
 {{{django.db.utils.IntegrityError: UNIQUE constraint failed:
 foo_bar__new.uu}}}

 6. The UUIDs are the same
 {{{#!python
 >>> [bar.uu for bar in Bar.objects.all()]
 [UUID('fae77227-7555-457d-a049-1e62e030ce1c'),
 UUID('fae77227-7555-457d-a049-1e62e030ce1c'),
 UUID('fae77227-7555-457d-a049-1e62e030ce1c'),
 UUID('fae77227-7555-457d-a049-1e62e030ce1c')]
 }}}


 Environment:
 {{{#!python
 >>> platform.python_version()
 '3.4.3'
 >>> platform.platform()
 'Linux-4.0.5-1-ARCH-x86_64-with-arch'
 >>> django.__version__
 '1.8.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/049.9a8317b39b98e9e9cbeda2fa0a030c19%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25006: Allow for custom Time shortcut in DateTimeShortCuts.js

2015-06-19 Thread Django

#25006: Allow for custom Time shortcut in DateTimeShortCuts.js
---+--
 Reporter:  RamezIssac |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  1.8
 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
---+--

Comment (by RamezIssac):

 I'm with you that it's not a big a deal, and hacks do exsits
 However, enhancing this might not be that hard, and most probably it's
 gonna stay with us when the html5 comes too.

 What do you think about this way...

 We add a new default in the DateTimeShortCut var, it use would look like
 this
 {{{

 DateTimeShortcuts['defaultTimes'] = {
 'all':[{ name : '8PM', hours:20} ,{ name : '10 PM', hours:22}],
 //special id, can make it _all_ to be get fancy
 //the default for all time fields , If not present we fall back to the
 django default
 'id_pub_date':[{ name : '11AM', hours:11} ,{ name : '11PM',
 hours:23}],
 'id_release_date':function(inp){
 //Go Nuts ! :-)
 }
 };
 }}}
 ?

 Kind Regards;

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

Re: [Django] #24940: unhashable type: 'RelatedManager' when deleting a model using django admin that has GenericRelation and related_query_name

2015-06-19 Thread Django

#24940: unhashable type: 'RelatedManager' when deleting a model using django 
admin
that has GenericRelation and related_query_name
-+-
 Reporter:  jmfederico   |Owner:  MarkusH
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.8
 Severity:  Release blocker  |   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
-+-

Comment (by Markus Holtermann ):

 In [changeset:"f64a3de2d4b623087c70405523a08a4e6043d102" f64a3de2]:
 {{{
 #!CommitTicketReference repository=""
 revision="f64a3de2d4b623087c70405523a08a4e6043d102"
 [1.8.x] Fixed #24940 -- Made model managers hashable

 Thanks Federico Jaramillo Martínez for the report and Tim Graham for the
 test and review.

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

Re: [Django] #24940: unhashable type: 'RelatedManager' when deleting a model using django admin that has GenericRelation and related_query_name

2015-06-19 Thread Django

#24940: unhashable type: 'RelatedManager' when deleting a model using django 
admin
that has GenericRelation and related_query_name
-+-
 Reporter:  jmfederico   |Owner:  MarkusH
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.8
 Severity:  Release blocker  |   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 Markus Holtermann ):

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


Comment:

 In [changeset:"d3d66d47222dd8765a20a15fdc754c0ed7635404" d3d66d4]:
 {{{
 #!CommitTicketReference repository=""
 revision="d3d66d47222dd8765a20a15fdc754c0ed7635404"
 Fixed #24940 -- Made model managers hashable

 Thanks Federico Jaramillo Martínez for the report and Tim Graham for the
 test and 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.5242577c1d92e7263e78f4df8cd659f8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

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

2015-06-19 Thread Django

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

Comment (by antialiasis):

 Chiming in with another +1 on the not-wontfixing - this is stopping me
 from running tests.

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

Re: [Django] #24313: Deprecate the class_prepared signal

2015-06-19 Thread Django

#24313: Deprecate the class_prepared signal
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by timgraham):

 There's also a
 
[https://github.com/django/django/blob/27c839e0fce99254ad61322bb827a821f832e840/django/db/models/signals.py#L15-L18
 usage in ModelSignal]. It's not immediately obvious to me how/if this can
 be refactored to use the app registry instead.

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

Re: [Django] #25002: Postgresql migration fails when changing a CharField to a TimeField

2015-06-19 Thread Django

#25002: Postgresql migration fails when changing a CharField to a TimeField
-+-
 Reporter:  dirkcuys |Owner:  charettes
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  migrations   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by charettes):

 Markus, I'm not sure how I should proceed, do you want me to add an
 additional test that makes sure an integer field can be converted to a
 char one? It looks like it's already working from the tests and doesn't
 require an explicit `USING`.

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

Re: [Django] #25002: Postgresql migration fails when changing a CharField to a TimeField

2015-06-19 Thread Django

#25002: Postgresql migration fails when changing a CharField to a TimeField
-+-
 Reporter:  dirkcuys |Owner:  charettes
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  migrations   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 #24264 looks like a suspect.

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

Re: [Django] #25004: Add an OpenLayers 3 compatible map widget

2015-06-19 Thread Django

#25004: Add an OpenLayers 3 compatible map widget
-+
 Reporter:  claudep  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  GIS  |  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 timgraham):

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

Re: [Django] #25002: Postgresql migration fails when changing a CharField to a TimeField

2015-06-19 Thread Django

#25002: Postgresql migration fails when changing a CharField to a TimeField
-+-
 Reporter:  dirkcuys |Owner:  charettes
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  migrations   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by charettes):

 Replying to [comment:5 MarkusH]:
 > That said, there is/was a ticket for `VARCHAR`/`INTEGER` conversation on
 a PK, I think. Do you mind investing that one too. Maybe they can both be
 closed by this patch?

 I'd like to but I can't find it by searching for tickets with the
 Migration component.

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

Re: [Django] #24970: Add option to sendtestmail command to email MANAGERS or ADMINS

2015-06-19 Thread Django

#24970: Add option to sendtestmail command to email MANAGERS or ADMINS
-+-
 Reporter:  timgraham|Owner:  rolo
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | 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 timgraham):

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


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

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

Re: [Django] #25006: Allow for custom Time shortcut in DateTimeShortCuts.js

2015-06-19 Thread Django

#25006: Allow for custom Time shortcut in DateTimeShortCuts.js
---+--
 Reporter:  RamezIssac |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  1.8
 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 timgraham):

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


Comment:

 [http://stackoverflow.com/questions/5770973/django-how-to-change-the-
 choices-of-admintimewidget Stackoverflow] has some ideas. Admittedly, none
 of these look particularly robust such that we could recommend them in our
 docs.

 I don't know that spending a lot of time trying to make it more
 customizable is worthwhile (can't think of an easy way), but I think an
 easy win for now would be to add 6pm to the list of choices so at least
 we're consistent with having options for every 6 hours.

 I think the best long-term solution would be to switch to HTML5
 `input="time"` and use the widgets provided by browsers. As of now, we are
 missing IE and Firefox support according to
 [http://www.w3schools.com/html/html_form_input_types.asp w3schools].

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

Re: [Django] #24887: Remove one-arg limitation from django.db.models.aggregate

2015-06-19 Thread Django

#24887: Remove one-arg limitation from django.db.models.aggregate
-+-
 Reporter:  akaariai |Owner:  gchp
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  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/066.0eccabbb274a93fce4821c9863f53d7c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24966: Unconfigured Allowed_Hosts Setting Should Raise ImproperlyConfigured Error

2015-06-19 Thread Django

#24966: Unconfigured Allowed_Hosts Setting Should Raise ImproperlyConfigured 
Error
-+-
 Reporter:  raiderrobert |Owner:
 Type:   |  raiderrobert
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  setting  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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

Re: [Django] #20916: Provide a "simple_login" feature for the test client

2015-06-19 Thread Django

#20916: Provide a "simple_login" feature for the test client
---+
 Reporter:  mjtamlyn   |Owner:
 Type:  New feature|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  auth   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by jdufresne):

 * cc: jon.dufresne@… (added)
 * needs_better_patch:  1 => 0
 * needs_docs:  1 => 0


Comment:

 Received a positive review from mjtamlyn, so removing some flags.

 More reviews and feedback is welcome. 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/066.940978c1fb1a3c256198d2a187857f9a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24970: Add option to sendtestmail command to email MANAGERS or ADMINS

2015-06-19 Thread Django

#24970: Add option to sendtestmail command to email MANAGERS or ADMINS
-+-
 Reporter:  timgraham|Owner:  rolo
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|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/067.ca6afa5a158be43244a01fd114723c22%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #25006: Allow for custom Time shortcut in DateTimeShortCuts.js

2015-06-19 Thread Django

#25006: Allow for custom Time shortcut in DateTimeShortCuts.js
---+
 Reporter:  RamezIssac |  Owner:  nobody
 Type:  New feature| Status:  new
Component:  contrib.admin  |Version:  1.8
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 The Time shortcut is an amazing add-on , yet it's kinda frustrating if the
 pre-defined shortcuts doesn't fit the field/the model or end user most
 used times.
 Shortcut times are: Now, 00:00 , 6 a.m. and noon, ..not very handy for
 night fun activities i might say :-D

 I managed to add this functionality through a javascript var that gets a
 check for existence when creating the shortcut html elements ;
 if found: loop through it & get shortcut 'Name' and 'hour' difference,
 Else: is the default behavior & times.

 I want to hear your opinion on the most 'django' way to go about it in
 order to make a pull request.

 Also, I apologize in advance if duplicated. (I honestly searched and
 couldn't find it)

 Regards;

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

Re: [Django] #25001: collectstatic does not correctly handle uninstallation of apps which write the same file as remaining apps.

2015-06-19 Thread Django

#25001: collectstatic does not correctly handle uninstallation of apps which
write
the same file as remaining apps.
-+-
Reporter: JulianAndrews|Owner: nobody
Type: Bug | Status: new
Component: contrib.staticfiles | Version: 1.8
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 timgraham):

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

Comment:

The issue is that `collectstatic` doesn't have any knowledge of which app
a static file was collected from. It only looks at a file's modification
time when determining whether to recopy a file. Unless there's an
alternate proposal, I'd suggest to add a documentation warning about this
and recommend the
[https://docs.djangoproject.com/en/stable/ref/contrib/staticfiles/#django-
admin-option---clear collectstatic --clear] option in this case.

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

Re: [Django] #12952: Models history doesn't use verbose names

2015-06-19 Thread Django

#12952: Models history doesn't use verbose names
--+
 Reporter:  acangiano |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.admin |  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:  1
--+

Comment (by RamezIssac):

 IMHO,  that depend on the intended audience of the changed message in the
 history.
 If it's the developer then verbose_name are the way to go.
 If it's the site 'content' administrator, this is what i think is the
 case, then labels are more of expected behavior; and in that case the
 "maybe different" verbose name can be confused as a bug.

 "I edited the field "More info", why does it show me that i edited
 'description' which is not even present on the form ?"

 :)

 Kind regards;

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

Re: [Django] #24881: order_with_respect_to needs better docs

2015-06-19 Thread Django

#24881: order_with_respect_to needs better docs
-+-
 Reporter:  karyon   |Owner:  karyon
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.8
 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:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"aa00f482801c78d0688ec347160177fd05e5d4c6" aa00f482]:
 {{{
 #!CommitTicketReference repository=""
 revision="aa00f482801c78d0688ec347160177fd05e5d4c6"
 [1.8.x] Fixed #24881 -- Clarified Meta.order_with_respect_to documentation

 Backport of 27c839e0fce99254ad61322bb827a821f832e840 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/064.cdc82e00c678b86d13a7fcd0ce15706c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24881: order_with_respect_to needs better docs

2015-06-19 Thread Django

#24881: order_with_respect_to needs better docs
-+-
 Reporter:  karyon   |Owner:  karyon
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.8
 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:  1|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"27c839e0fce99254ad61322bb827a821f832e840" 27c839e0]:
 {{{
 #!CommitTicketReference repository=""
 revision="27c839e0fce99254ad61322bb827a821f832e840"
 Fixed #24881 -- Clarified Meta.order_with_respect_to 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/064.231ef4f272791d742f5f5cefb77fdd16%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

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

2015-06-19 Thread Django

#25005: DateField, DateTimeField defaults needed even when auto_now=True
-+--
 Reporter:  monobotsoft  |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Migrations   |Version:  1.8
 Severity:  Normal   |   Keywords:  DateField, DateTimeField
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+--
 When you create a new DateField on a model even when it has auto_now=True.

 ./manage.py makemigrations asks for a default value

 This is a low priority bug since its so easylly solved using
 default=timezone.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/054.b7faed1acbe8acbd6f95c514c06addbe%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25004: Add an OpenLayers 3 compatible map widget

2015-06-19 Thread Django

#25004: Add an OpenLayers 3 compatible map widget
-+--
 Reporter:  claudep  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  GIS  |  Version:  master
 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
-+--
Changes (by claudep):

 * has_patch:  0 => 1


Comment:

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

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

[Django] #25004: Add an OpenLayers 3 compatible map widget

2015-06-19 Thread Django

#25004: Add an OpenLayers 3 compatible map widget
---+
   Reporter:  claudep  |  Owner:  nobody
   Type:  New feature  | Status:  new
  Component:  GIS  |Version:  master
   Severity:  Normal   |   Keywords:
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+
 OpenLayers 3 is out now from some time, and I think Django should support
 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/050.27daf7e27bb0160a907eaef46f394004%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24985: Provide a way to sanitize invalid characters from Rss201rev2Feed

2015-06-19 Thread Django

Comment (by claudep):

#20197 is similar but targets XML serialization with `dumpdata`. I just
added a patch in that ticket to loudly fail instead of silently producing
invalid XML. Automatic sanitation is tricky, because depending on the use
case, you might want to remove the offending chars, replace them with some
alternative coding, or simply fix the source.

The patch for #20197 also affects RSS production, as the same
`django.utils.xmlutils.SimplerXMLGenerator` is used. If it gets committed,
we might want to add a similar admonition in syndication docs.

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

Re: [Django] #20197: XML serializer can output invalid characters

2015-06-19 Thread Django

#20197: XML serializer can output invalid characters
--+
 Reporter:  ris   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.3
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by claudep):

 * has_patch:  0 => 1


Comment:

 This [https://github.com/django/django/pull/4888 PR] fails loudly when a
 control character is contained inside to-be-serialized content. I think
 that's better than silently producing invalid XML.

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

48 matches

Mail list logo