date:20150526

Re: [Django] #24862: Patch for GeoDjango to improve error message if database connection is bad

2015-05-26 Thread Django

#24862: Patch for GeoDjango to improve error message if database connection is 
bad
-+-
 Reporter:  brycenesbitt |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  GIS  |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  PostGIS, GeoDjango,  | Triage Stage:
  GIS, Usability |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by brycenesbitt):

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


Old description:

> For a project with GeoDjango fi the database is completely down, you'll
> get exception:
>
> {{{
> django.core.exceptions.ImproperlyConfigured: Cannot determine PostGIS
> version for database "umap" . GeoDjango requires at least PostGIS version
> 1.3. Was the database created from a spatial database template?
> }}}
>
> This patch first does a trivial database connection to flesh out the real
> exception, before checking the PostGIS version number:
>

> {{{
> ***
> *** 246,256 
>   # comprising user-supplied values for the major, minor, and
>   # subminor revision of PostGIS.
> -
> - # First connect to the database trivially
> - # This prevents raising a GeoDjango exception below if the
> connection is bad
> - with self.connection.temporary_connection() as cursor:
> - cursor.execute('SELECT version()')
> -
> - # Now check PostGIS
>   if hasattr(settings, 'POSTGIS_VERSION'):
>   version = settings.POSTGIS_VERSION
> --- 246,249 
> ***
> *** 260,265 
>   except DatabaseError:
>   raise ImproperlyConfigured(
> ! 'Cannot determine PostGIS version for database "%s"
> '
> ! 'using command "SELECT postgis_lib_version()". '
>   'GeoDjango requires at least PostGIS version 1.3. '
>   'Was the database created from a spatial database '
> --- 253,257 
>   except DatabaseError:
>   raise ImproperlyConfigured(
> ! 'Cannot determine PostGIS version for database
> "%s". '
>   'GeoDjango requires at least PostGIS version 1.3. '
>   'Was the database created from a spatial database '
>
> }}}

New description:

 For a project with GeoDjango if the database is completely down, you'll
 get exception:

 {{{
 django.core.exceptions.ImproperlyConfigured: Cannot determine PostGIS
 version for database "umap" . GeoDjango requires at least PostGIS version
 1.3. Was the database created from a spatial database template?
 }}}

 This patch first does a trivial database connection to flesh out the real
 exception, before checking the PostGIS version number:


 {{{
 ***
 *** 246,256 
   # comprising user-supplied values for the major, minor, and
   # subminor revision of PostGIS.
 -
 - # First connect to the database trivially
 - # This prevents raising a GeoDjango exception below if the
 connection is bad
 - with self.connection.temporary_connection() as cursor:
 - cursor.execute('SELECT version()')
 -
 - # Now check PostGIS
   if hasattr(settings, 'POSTGIS_VERSION'):
   version = settings.POSTGIS_VERSION
 --- 246,249 
 ***
 *** 260,265 
   except DatabaseError:
   raise ImproperlyConfigured(
 ! 'Cannot determine PostGIS version for database "%s"
 '
 ! 'using command "SELECT postgis_lib_version()". '
   'GeoDjango requires at least PostGIS version 1.3. '
   'Was the database created from a spatial database '
 --- 253,257 
   except DatabaseError:
   raise ImproperlyConfigured(
 ! 'Cannot determine PostGIS version for database "%s".
 '
   'GeoDjango requires at least PostGIS version 1.3. '
   'Was the database created from a spatial database '

 }}}

--

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to

[Django] #24862: Patch for GeoDjango to improve error message if database connection is bad

2015-05-26 Thread Django

#24862: Patch for GeoDjango to improve error message if database connection is
bad
-+-
Reporter: brycenesbitt | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: GIS |Version: 1.8
Severity: Normal | Keywords: PostGIS, GeoDjango,
| GIS, Usability
Triage Stage: Unreviewed | Has patch: 1
Easy pickings: 1| UI/UX: 0
-+-
For a project with GeoDjango fi the database is completely down, you'll
get exception:

{{{
django.core.exceptions.ImproperlyConfigured: Cannot determine PostGIS
version for database "umap" . GeoDjango requires at least PostGIS version
1.3. Was the database created from a spatial database template?
}}}

This patch first does a trivial database connection to flesh out the real
exception, before checking the PostGIS version number:

{{{
***
*** 246,256
# comprising user-supplied values for the major, minor, and
# subminor revision of PostGIS.
-
- # First connect to the database trivially
- # This prevents raising a GeoDjango exception below if the
connection is bad
- with self.connection.temporary_connection() as cursor:
- cursor.execute('SELECT version()')
-
- # Now check PostGIS
if hasattr(settings, 'POSTGIS_VERSION'):
version = settings.POSTGIS_VERSION
--- 246,249
***
*** 260,265
except DatabaseError:
raise ImproperlyConfigured(
! 'Cannot determine PostGIS version for database "%s"
'
! 'using command "SELECT postgis_lib_version()". '
'GeoDjango requires at least PostGIS version 1.3. '
'Was the database created from a spatial database '
--- 253,257
except DatabaseError:
raise ImproperlyConfigured(
! 'Cannot determine PostGIS version for database "%s".
'
'GeoDjango requires at least PostGIS version 1.3. '
'Was the database created from a spatial database '

}}}

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

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

Re: [Django] #24856: raw_id_fields popup missing

2015-05-26 Thread Django

#24856: raw_id_fields popup missing
---+--
 Reporter:  liwee  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  1.8
 Severity:  Normal |   Resolution:  worksforme
 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 liwee):

 * Attachment "10_javascript.PNG" 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/063.203274da0510a0ce74241c95553dc618%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24856: raw_id_fields popup missing

2015-05-26 Thread Django

#24856: raw_id_fields popup missing
---+--
 Reporter:  liwee  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  1.8
 Severity:  Normal |   Resolution:  worksforme
 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 liwee):

 * Attachment "9_javascript.PNG" 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/063.e7dfead24c783b69b248a0e5575d15b8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24856: raw_id_fields popup missing

2015-05-26 Thread Django

#24856: raw_id_fields popup missing
---+--
 Reporter:  liwee  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  1.8
 Severity:  Normal |   Resolution:  worksforme
 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 liwee):

 chrome Version 43.0.2357.81 m
 attached javascript console output below

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

Re: [Django] #24836: force_text doesn't force SimpleLazyObject into a string

2015-05-26 Thread Django

#24836: force_text doesn't force SimpleLazyObject into a string
-+
 Reporter:  riklaunim|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Utilities|  Version:  1.8
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by timgraham):

 * needs_better_patch:  1 => 0


Comment:

 Test failures resolved.

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

Re: [Django] #24709: ArrayField doesn't support .update() and F() objects

2015-05-26 Thread Django

#24709: ArrayField doesn't support .update() and F() objects
-+-
 Reporter:  ris  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.postgres |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  postgresql contrib   | Triage Stage:  Accepted
  arrayfield update  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jarshwah):

 This seems like a very similar problem to how F() and Sum() evolved
 separately when they could have been the same with a little (lot..) more
 work. Marc, could you require that the inputs to Array/HStore be
 expressions (with an appropriate _parse_expression() to wrap basic values
 in Value())? If you provide support for expressions only, then getting
 basic values in comes fairly naturally too.

 I haven't looked into the implementation of these fields though, so I
 don't know how feasible it would be to support.

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

Re: [Django] #24861: Pass a queryset for each different field Admin Inlines

2015-05-26 Thread Django

#24861: Pass a queryset for each different field Admin Inlines
-+-
 Reporter:  unehub   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  admin, inlines,  | Triage Stage:
  forms, formsets|  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:   => invalid


Comment:

 Please don't post support requests to Trac. Your post on
 [https://groups.google.com/d/msg/django-users/K_WPqFlZ4KQ/8M8ofnaUwuoJ
 django-users] is the correct place to ask for help. Thanks!

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

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

Re: [Django] #24732: Reorder tutorial to cover basics before bells and whistles

2015-05-26 Thread Django

#24732: Reorder tutorial to cover basics before bells and whistles
-+-
 Reporter:  carljm   |Owner:
 Type:   |  dirtycoder
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 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):

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


Comment:

 Final review to be done tomorrow.

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

Re: [Django] #24856: raw_id_fields popup missing

2015-05-26 Thread Django

#24856: raw_id_fields popup missing
---+--
 Reporter:  liwee  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  1.8
 Severity:  Normal |   Resolution:  worksforme
 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):

 What browser? Any JavaScript errors in the console?

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

Re: [Django] #24861: Pass a queryset for each different field Admin Inlines

2015-05-26 Thread Django

#24861: Pass a queryset for each different field Admin Inlines
-+-
 Reporter:  unehub   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin, inlines,  | Triage Stage:
  forms, formsets|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by unehub):

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


Old description:

> Pretend to have in the Django admin, 2 forms inlines, Each with a pair of
> fields choices, "Attributes" and "Value Option". We have the first pair,
> which initialize the field one with a value, for example color and other
> field you must have a queryset the choices.
>
> [[Image(http://i.stack.imgur.com/kk1xQ.png)]]
>
> As you can see We need to filter each pair with their default values, if
> Color should show only white, black and blue.
>

> {{{
> class ProductAttributeValueForm(forms.ModelForm):
> attribute = forms.ModelChoiceField(label=_('Attribute'),
> widget=forms.Select(attrs={'disabled': 'True'}),
> queryset=ProductAttribute.objects.all(), required=False)
>
> class ProductAttributeValueFormSet(BaseInlineFormSet):
>
> def __init__(self, *args, **kwargs):
> super(ProductAttributeValueFormSet, self).__init__(*args,
> **kwargs)
> # This return initial [{'attribute' initial}, {..}, {..}]
> self.initial = [{'attribute': a} for a in
> obj.category.attributes.all()]
> # Now we need to make a queryset to each field of each form
> inline
> self.queryset = [{'value_option' .. }, { .. }]
> }}}
>
> What I do is initialize each attribute with a value, for example, Color
> and passed a queryset to value_option with their respective values,
> white, blue and black. I have tried to do this two days ago and I have
> not accomplished anything, not if the solution is on the forms or in any
> function of admin.
>
> if I could just iterate a QuerySet each model choice of the form. The
> only thing achieved is that a queryset applies to all forms inline, but I
> need a different one for each inline.
>
> def formfield_for_foreignkey(self, db_field, request, **kwargs):
> if db_field.name == "value_option":
> kwargs["queryset"] = request._obj_.category.attributes.all()
> return super(AttributeInline,
> self).formfield_for_foreignkey(db_field, request, **kwargs)
>
> So, if you have Attribute: Color, Size, ROM, RAM,  the ideal would happen
> to a custom list value_options each.

New description:

 Pretend to have in the Django admin, 2 forms inlines, Each with a pair of
 fields choices, "Attributes" and "Value Option". We have the first pair,
 which initialize the field one with a value, for example color and other
 field you must have a queryset the choices.

 [[Image(http://i.stack.imgur.com/kk1xQ.png)]]

 As you can see We need to filter each pair with their default values, if
 Color should show only white, black and blue.


 {{{
 class ProductAttributeValueForm(forms.ModelForm):
 attribute = forms.ModelChoiceField(label=_('Attribute'),
 widget=forms.Select(attrs={'disabled': 'True'}),
 queryset=ProductAttribute.objects.all(), required=False)

 class ProductAttributeValueFormSet(BaseInlineFormSet):

 def __init__(self, *args, **kwargs):
 super(ProductAttributeValueFormSet, self).__init__(*args,
 **kwargs)
 # This return initial [{'attribute' initial}, {..}, {..}]
 self.initial = [{'attribute': a} for a in
 obj.category.attributes.all()]
 # Now we need to make a queryset to each field of each form inline
 self.queryset = [{'value_option' .. }, { .. }]
 }}}

 What I do is initialize each attribute with a value, for example, Color
 and passed a queryset to value_option with their respective values, white,
 blue and black. I have tried to do this two days ago and I have not
 accomplished anything, not if the solution is on the forms or in any
 function of admin.

 if I could just iterate a QuerySet each model choice of the form. The only
 thing achieved is that a queryset applies to all forms inline, but I need
 a different one for each inline.


 {{{
 def formfield_for_foreignkey(self, db_field, request, **kwargs):
 if db_field.name == "value_option":
 kwargs["queryset"] = request._obj_.category.attributes.all()
 return super(AttributeInline, self).formfield_for_foreignkey(db_field,
 request, **kwargs)
 }}}


 So, if you have Attribute: Color,

[Django] #24861: Pass a queryset for each different field Admin Inlines

2015-05-26 Thread Django

#24861: Pass a queryset for each different field Admin Inlines
-+-
 Reporter:  unehub   |  Owner:  nobody
 Type:  New feature  | Status:  new
Component:   |Version:  master
  contrib.admin  |
 Severity:  Normal   |   Keywords:  admin, inlines, forms, formsets
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 Pretend to have in the Django admin, 2 forms inlines, Each with a pair of
 fields choices, "Attributes" and "Value Option". We have the first pair,
 which initialize the field one with a value, for example color and other
 field you must have a queryset the choices.

 [[Image(http://i.stack.imgur.com/kk1xQ.png)]]

 As you can see We need to filter each pair with their default values, if
 Color should show only white, black and blue.


 {{{
 class ProductAttributeValueForm(forms.ModelForm):
 attribute = forms.ModelChoiceField(label=_('Attribute'),
 widget=forms.Select(attrs={'disabled': 'True'}),
 queryset=ProductAttribute.objects.all(), required=False)

 class ProductAttributeValueFormSet(BaseInlineFormSet):

 def __init__(self, *args, **kwargs):
 super(ProductAttributeValueFormSet, self).__init__(*args,
 **kwargs)
 # This return initial [{'attribute' initial}, {..}, {..}]
 self.initial = [{'attribute': a} for a in
 obj.category.attributes.all()]
 # Now we need to make a queryset to each field of each form inline
 self.queryset = [{'value_option' .. }, { .. }]
 }}}

 What I do is initialize each attribute with a value, for example, Color
 and passed a queryset to value_option with their respective values, white,
 blue and black. I have tried to do this two days ago and I have not
 accomplished anything, not if the solution is on the forms or in any
 function of admin.

 if I could just iterate a QuerySet each model choice of the form. The only
 thing achieved is that a queryset applies to all forms inline, but I need
 a different one for each inline.

 def formfield_for_foreignkey(self, db_field, request, **kwargs):
 if db_field.name == "value_option":
 kwargs["queryset"] = request._obj_.category.attributes.all()
 return super(AttributeInline, self).formfield_for_foreignkey(db_field,
 request, **kwargs)

 So, if you have Attribute: Color, Size, ROM, RAM,  the ideal would happen
 to a custom list value_options each.

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

Re: [Django] #24856: raw_id_fields popup missing

2015-05-26 Thread Django

#24856: raw_id_fields popup missing
---+--
 Reporter:  liwee  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  1.8
 Severity:  Normal |   Resolution:  worksforme
 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 liwee):

 * Attachment "10.PNG" 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/063.246c3f6630d3bb1eb450ae08b4bb8e3c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24856: raw_id_fields popup missing

2015-05-26 Thread Django

#24856: raw_id_fields popup missing
---+--
 Reporter:  liwee  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  1.8
 Severity:  Normal |   Resolution:  worksforme
 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 liwee):

 * Attachment "11.PNG" 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/063.003987a4a28e9d057d6c7ea209c04544%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24856: raw_id_fields popup missing

2015-05-26 Thread Django

#24856: raw_id_fields popup missing
---+--
 Reporter:  liwee  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  1.8
 Severity:  Normal |   Resolution:  worksforme
 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 liwee):

 * Attachment "9.PNG" 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/063.00b87cfce57b2d6d6270f380568418f7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24856: raw_id_fields popup missing

2015-05-26 Thread Django

#24856: raw_id_fields popup missing
---+--
 Reporter:  liwee  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  1.8
 Severity:  Normal |   Resolution:  worksforme
 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 liwee):

 I started a new project based on the tutorial. I have attached relevant
 screens as well

 models.py

 {{{
 class Customer(models.Model):
 name = models.CharField(max_length=200)

 class Task(models.Model):
 cust = models.ForeignKey(Customer)
 }}}

 admin.py

 {{{
 from .models import *

 class TaskAdmin(admin.ModelAdmin):
 raw_id_fields = ('cust',)

 admin.site.register(Task, TaskAdmin)
 admin.site.register(Customer)
 }}}

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

[Django] #24860: Migrations leak stale RelatedManager related_model definitions

2015-05-26 Thread Django

#24860: Migrations leak stale RelatedManager related_model definitions
--+---
 Reporter:  ecederstrand  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Migrations|Version:  1.8
 Severity:  Normal|   Keywords:  migration, RelatedManager
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+---
 I have a Django 1.8.2 app with models A and B, where data in class A has
 been migrated from one field to another. My actual code is a lot more
 involved and difficult to reduce to a sane test case, but the following is
 the essence of my debugging:

 {{{
 # Unchanged
 class B(models.Model):
pass


 # version 1
 class A(models.Model):
b = models.ForeignKey(B)
x = models.FooField()
 }}}

 Now field 'y' is added to class A and a migration is created

 {{{
 # version 2
 class A(models.Model):
rel = models.ForeignKey(B)
x = models.FooField()
y = models.BarField()
 }}}

 A data migration to move data from 'x' to 'y' is created

 {{{
A = apps.get_model("my_app", "A")
for i in A.objects.all():
   i.y = i.x
   i.save()
 }}}

 Field 'x' is no longer needed on class A. New migration is created

 {{{
 # version 3
 class A(models.Model):
rel = models.ForeignKey(B)
y = models.BarField()
 }}}

 Now when I run a test case which uses prefetch, invalid SQL is generated.

 {{{
 def test_case():
 list(B.objects.all().prefetch_related('a_set'))
 ->  psycopg2.ProgrammingError: column A.x does not exist
 }}}


 The reason for this is that 'def related_manager_cls()' in
 django/db/models/fields/related.py:832 is a @cached_property. When I run
 my test case, the migrations are run to create the test database. This
 caches version 2 of class A in self.related.related_model as a , which is then returned later on in the test case. Thus,
 prefetch SQL for version 2 is produced instead of for version 3. I suspect
 the problem occurs because of the data migration.

 No errors show when I use prefetch_related() in production, because the
 migrations aren't run.

 I'm uncertain how to fix this. Somehow the property caches should be
 invalidated after each migration is run.

 It seems related.py has more potentally dangerous uses of @cached_property

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

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

Re: [Django] #24709: ArrayField doesn't support .update() and F() objects

2015-05-26 Thread Django

#24709: ArrayField doesn't support .update() and F() objects
-+-
 Reporter:  ris  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.postgres |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  postgresql contrib   | Triage Stage:  Accepted
  arrayfield update  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by adamchainz):

 I have written a similar separate F API for the the comma-separated fields
 in Django-MySQL - see http://django-
 mysql.readthedocs.org/en/latest/model_fields.html#listf-expressions . I
 made a `ListF` class for doing single atomic add/remove operations on
 either end of the list, which is about all that can be done with MySQL's
 comma-separated-list parsing capabilities.

 It is obviously much less involved than Postgres' arrays, but maybe it
 will inspire. I think add/remove operations are quite useful to consider
 on top of the 'set element at position X to Y' and 'set array field to
 [Y]' operations.

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

Re: [Django] #24817: Renaming a model field that has null=False makes it nullable in MySQL

2015-05-26 Thread Django

#24817: Renaming a model field that has null=False makes it nullable in MySQL
-+
 Reporter:  murfi|Owner:  coldmind
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.8
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by coldmind):

 PR against master - https://github.com/django/django/pull/4715

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

Re: [Django] #23658: Provide the password to PostgreSQL from "dbshell" command

2015-05-26 Thread Django

#23658: Provide the password to PostgreSQL from "dbshell" command
-+-
 Reporter:  etanol   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  postgresql dbshell   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by MarkusH):

 * needs_better_patch:  0 => 1


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

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

Re: [Django] #24836: force_text doesn't force SimpleLazyObject into a string

2015-05-26 Thread Django

#24836: force_text doesn't force SimpleLazyObject into a string
-+
 Reporter:  riklaunim|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Utilities|  Version:  1.8
 Severity:  Release blocker  |   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
 * has_patch:  0 => 1
 * component:  CSRF => Utilities


Comment:

 [https://github.com/django/django/pull/4713 PR], but have some test
 failures on Python 2 that need to be investigated.

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

Re: [Django] #24817: Renaming a model field that has null=False makes it nullable in MySQL

2015-05-26 Thread Django

#24817: Renaming a model field that has null=False makes it nullable in MySQL
-+
 Reporter:  murfi|Owner:  coldmind
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.8
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by coldmind):

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


Comment:

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

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

Re: [Django] #24817: Renaming a model field that has null=False makes it nullable in MySQL

2015-05-26 Thread Django

#24817: Renaming a model field that has null=False makes it nullable in MySQL
-+
 Reporter:  murfi|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.8
 Severity:  Release blocker  |   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 coldmind):

 * cc: me@… (added)


Comment:

 I just attached a patch with tests which reproduces the issue.
 I'm also working on fixing 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/063.018ae85a5183c9a1d7d10b5aa5837a03%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24817: Renaming a model field that has null=False makes it nullable in MySQL

2015-05-26 Thread Django

#24817: Renaming a model field that has null=False makes it nullable in MySQL
-+
 Reporter:  murfi|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.8
 Severity:  Release blocker  |   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 coldmind):

 * Attachment "ticket_24817.patch" added.

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

Re: [Django] #24496: Check CSRF Referer against CSRF_COOKIE_DOMAIN

2015-05-26 Thread Django

#24496: Check CSRF Referer against CSRF_COOKIE_DOMAIN
--+
 Reporter:  mattrobenolt  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  CSRF  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  csrf  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

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

Re: [Django] #24720: using middleware.common to append slashes causes extra overhead to all requests that do not end in a slash

2015-05-26 Thread Django

#24720: using middleware.common to append slashes causes extra overhead to all
requests that do not end in a slash
-+-
 Reporter:  electricjay  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  optimization | Triage Stage:  Accepted
  middleware common  |
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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

Re: [Django] #24847: Items set on a RequestContext after creation get lost

2015-05-26 Thread Django

#24847: Items set on a RequestContext after creation get lost
-+
 Reporter:  pmdhazy  |Owner:  pwmarcz
 Type:  Bug  |   Status:  assigned
Component:  Template system  |  Version:  1.8
 Severity:  Release blocker  |   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 pwmarcz):

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

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

[Django] #24859: UUIDField does not Properly Raise TyperError

2015-05-26 Thread Django

#24859: UUIDField does not Properly Raise TyperError
---+
 Reporter:  cancan101  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Uncategorized  |Version:  1.8
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I have two models one with an int pk and one with a UUIDField pk:


 {{{
 class Bar(models.Model):
 id = models.UUIDField(primary_key=True, default=uuid4)

 class Bar2(models.Model):
 pass
 }}}

 If I try to get these using a value of {} they fail differently. The model
 with the int pk:

 {{{
 >>> Bar2.objects.all().get(pk={})
 TypeError: int() argument must be a string or a number, not 'dict'
 }}}


 whereas:

 {{{
 >>> Bar.objects.all().get(pk={})
 Traceback (most recent call last):
   File "", line 1, in 
   File "/Users/alex/.virtualenvs/TestPG/lib/python2.7/site-
 packages/django/db/models/query.py", line 328, in get
 num = len(clone)
   File "/Users/alex/.virtualenvs/TestPG/lib/python2.7/site-
 packages/django/db/models/query.py", line 144, in __len__
 self._fetch_all()
   File "/Users/alex/.virtualenvs/TestPG/lib/python2.7/site-
 packages/django/db/models/query.py", line 965, in _fetch_all
 self._result_cache = list(self.iterator())
   File "/Users/alex/.virtualenvs/TestPG/lib/python2.7/site-
 packages/django/db/models/query.py", line 238, in iterator
 results = compiler.execute_sql()
   File "/Users/alex/.virtualenvs/TestPG/lib/python2.7/site-
 packages/django/db/models/sql/compiler.py", line 840, in execute_sql
 cursor.execute(sql, params)
   File "/Users/alex/.virtualenvs/TestPG/lib/python2.7/site-
 packages/django/db/backends/utils.py", line 79, in execute
 return super(CursorDebugWrapper, self).execute(sql, params)
   File "/Users/alex/.virtualenvs/TestPG/lib/python2.7/site-
 packages/django/db/backends/utils.py", line 64, in execute
 return self.cursor.execute(sql, params)
   File "/Users/alex/.virtualenvs/TestPG/lib/python2.7/site-
 packages/django/db/utils.py", line 97, in __exit__
 six.reraise(dj_exc_type, dj_exc_value, traceback)
   File "/Users/alex/.virtualenvs/TestPG/lib/python2.7/site-
 packages/django/db/backends/utils.py", line 64, in execute
 return self.cursor.execute(sql, params)
   File "/Users/alex/.virtualenvs/TestPG/lib/python2.7/site-
 packages/django/db/backends/sqlite3/base.py", line 318, in execute
 return Database.Cursor.execute(self, query, params)
 InterfaceError: Error binding parameter 0 - probably unsupported type.
 }}}

 This inconsistency leads to issues like: https://github.com/tomchristie
 /django-rest-framework/issues/2970

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

Re: [Django] #24847: Items set on a RequestContext after creation get lost

2015-05-26 Thread Django

#24847: Items set on a RequestContext after creation get lost
-+
 Reporter:  pmdhazy  |Owner:  pwmarcz
 Type:  Bug  |   Status:  assigned
Component:  Template system  |  Version:  1.8
 Severity:  Release blocker  |   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 pwmarcz):

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


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

Re: [Django] #22938: clearsessions doesn't remove file-based sessions (was: clearsessions not remore session files from tmp)

2015-05-26 Thread Django

#22938: clearsessions doesn't remove file-based sessions
--+
 Reporter:  atarkowska@…  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.sessions  |  Version:  1.6
 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/081.f369f64c31845f921dad5c3685ca4990%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #10941: Add querystring helper methods to Page class

2015-05-26 Thread Django

#10941: Add querystring helper methods to Page class
--+
 Reporter:  benspaulding  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  pagination| 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.46b89b5b71d31372e759926afbe2e67a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24857: Add main entry point as an alias for django-admin

2015-05-26 Thread Django

#24857: Add __main__ entry point as an alias for django-admin
-+-
 Reporter:  tricoder42   |Owner:
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by tricoder42):

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


Comment:

 I agree that simple test will be sufficient:

 {{{
 import subprocess


 def test_module_installed():
 call_args = ['python', '-m', 'django', '-v']
 assert subprocess.call(call_args) == 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/068.c071a7a55af0c9807a67934137291b3f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24853: FK value not inserted in database in data migration

2015-05-26 Thread Django

Comment (by timgraham):

I think the problem is roughly described in
[https://docs.djangoproject.com/en/1.8/topics/migrations/#dependencies the
dependencies section] of the migrations docs. Basically, migrations and
models without migrations don't interact very well.

I don't think we are going to invest any time in trying to remedy this as
migrations will be compulsory for all apps in 1.9. We could add a sentence
to the 1.8 docs in the dependencies section, "In addition, any models that
are used in RunPython operations must have migrations."

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

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

Re: [Django] #24853: FK value not inserted in database in data migration

2015-05-26 Thread Django

#24853: FK value not inserted in database in data migration
-+-
 Reporter:  rakanalh |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  1.7
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  database,| Triage Stage:
  migrations |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by rakanalh):

 That worked.

 I ran:

 {{{
 python manage.py makemigrations dynamic_scraper
 }}}

 Then

 {{{
 python manage.py migrate dynamic_scraper --fake
 }}}
 Because the tables already exist.

 And ran migrate again on my app and everything ran as expected.

 Could you please provide more context of why i needed to create a
 migration for this third party app?

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

Re: [Django] #24159: compilemessages does not behave the same as makemessages

2015-05-26 Thread Django

#24159: compilemessages does not behave the same as makemessages
--+
 Reporter:  dracos|Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Internationalization  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * needs_docs:  0 => 1
 * version:  1.7 => master


Comment:

 Code looks okay to me, but needs documentation as noted on the pull
 request.

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

Re: [Django] #24853: FK value not inserted in database in data migration

2015-05-26 Thread Django

#24853: FK value not inserted in database in data migration
-+-
 Reporter:  rakanalh |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  1.7
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  database,| Triage Stage:
  migrations |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 You could try adding an initial migration to the dynamic_scraper app (use
 [https://docs.djangoproject.com/en/1.8/ref/settings/#migration-modules
 settings.MIGRATION_MODULES]). Then update your data migration to have a
 dependency on that migration.

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

Re: [Django] #24853: FK value not inserted in database in data migration

2015-05-26 Thread Django

Comment (by rakanalh):

Thanks for the follow up on this ticket.

I started off the project using Django 1.6 which is how i managed to run
the south migrations in the first place.

I upgraded to django 1.7 and then upon your request to 1.8, removed the
".id" part and i was able to regenerate the issue on 1.8.2 as well.

As for Tim's comment, Shaib's assumptions are correct. My
"content_scraper" app has no models, it just provides a "default" data
migration for the models provided by "dynamic_scraper".

Let me know how i can be of any further help.

Thanks,
Rakan

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

Re: [Django] #24853: FK value not inserted in database in data migration

2015-05-26 Thread Django

Comment (by shaib):

Replying to [comment:2 timgraham]:
> Is the migration with `RunPython` the initial migration, i.e.
`0001_initial.py`? If so, this is incorrect -- you need an initial
migration which creates all the models in the app.

If I understand correctly, the migration belongs to `content_scraper` (an
app with no models of its own?) but it uses the models from
`dynamic_scraper`, which appears to be an unmigrated app (its public
repository has only South migrations). This should be valid, as far as I
understand, but only if my assumptions indeed hold.

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

Re: [Django] #24857: Add main entry point as an alias for django-admin

2015-05-26 Thread Django

#24857: Add __main__ entry point as an alias for django-admin
-+-
 Reporter:  tricoder42   |Owner:
 |  tricoder42
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 Did you investigate my suggestion of using the subprocess module
 (following the example in `tests/model_regress/test_pickle.py`). I don't
 think we need to test `python -m django`, but rather just execute the the
 `__main__.py` script directly and ensure it works like django-admin (one
 test should be enough -- I don't think we don't need to execute all the
 admin_script tests through 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.1f96aaff8d5380e2a38e948ee38d8a7e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24858: get_foo_display with the ArrayField

2015-05-26 Thread Django

#24858: get_foo_display with the ArrayField
--+--
 Reporter:  MounirMesselmeni  |Owner:
 Type:  Uncategorized |   Status:  new
Component:  contrib.postgres  |  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:

 Could you please add a code snippet of the expected behavior?

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

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

[Django] #24858: get_foo_display with the ArrayField

2015-05-26 Thread Django

#24858: get_foo_display with the ArrayField
--+-
 Reporter:  MounirMesselmeni  |  Owner:
 Type:  Uncategorized | Status:  new
Component:  contrib.postgres  |Version:  1.8
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+-
 I think using ArrayField as a many choices field would be awesome.
 Passing choices to ArrayField works fine with MultipleChoiceField on the
 form.
 But calling get_foo_display return a TypeError: unhashable type: 'list',
 maybe this method need to check if the field is an ArrayField it can
 return a string representation of the choices separated by comma.

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

Re: [Django] #24857: Add main entry point as an alias for django-admin

2015-05-26 Thread Django

#24857: Add __main__ entry point as an alias for django-admin
-+-
 Reporter:  tricoder42   |Owner:
 |  tricoder42
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by ryanhiebert):

 I've worked on this a bit more, added a couple updates to the PR
 referenced in the OP. I spent a little time figuring out how to test it,
 but don't have it all worked out yet. Best I can tell so far is that the
 tests probably need to live in {{{tests/admin_scripts/tests.py}}}, but I
 don't have it worked out what and how is the best way to test.

 My first thought is to subclass or copy the {{{DjangoAdmin*}}} tests to
 use the python entry point. I could subclass {{{AdminScriptTestCase}}},
 but that just seems like a lot of test coupling.

 One problem I'm not quite sure how to deal with is that the current tests
 don't seem to require that Django be installed properly. I might be able
 to just make sure the current working directory is the root of the
 repository...

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

Re: [Django] #24340: Nested deconstruction does not descend into lists, tuples or dicts

2015-05-26 Thread Django

#24340: Nested deconstruction does not descend into lists, tuples or dicts
+
 Reporter:  gasman  |Owner:  gasman
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by Markus Holtermann ):

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


Comment:

 In [changeset:"ff8a02ae0b33ee52050e22909d432a3aa060d683" ff8a02a]:
 {{{
 #!CommitTicketReference repository=""
 revision="ff8a02ae0b33ee52050e22909d432a3aa060d683"
 Fixed #24340 -- Added nested deconstruction for list, tuple and dict
 values

 Nested deconstruction should recursively deconstruct items within list,
 tuple and dict values.
 }}}

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

Re: [Django] #24675: Skip "SET SQL_AUTO_IS_NULL = 0" on versions of MySQL that don't need it

2015-05-26 Thread Django

#24675: Skip "SET SQL_AUTO_IS_NULL = 0" on versions of MySQL that don't need it
-+-
 Reporter:  ssjunior |Owner:  ssjunior
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  mysql| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 Claude, how did you imagine a test would look like for this?

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

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

Re: [Django] #18247: filter and Decimal equality doesn't work

2015-05-26 Thread Django

#18247: filter and Decimal equality doesn't work
-+-
 Reporter:  elmopl@… |Owner:  NEOatNHNG
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  decimal filter   | Triage Stage:  Accepted
  annotate having|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by NEOatNHNG):

 * cc: NEOatNHNG (added)
 * keywords:  decimal filter => decimal filter annotate having
 * status:  new => assigned
 * owner:  nobody => NEOatNHNG


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

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

Re: [Django] #24857: Add main entry point as an alias for django-admin

2015-05-26 Thread Django

#24857: Add __main__ entry point as an alias for django-admin
-+-
 Reporter:  tricoder42   |Owner:
 |  tricoder42
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by ryanhiebert):

 I don't think it's worth it. I expect others will too, given that's how
 the duplication is avoided in {{{manage.py}}}.

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

Re: [Django] #24496: Check CSRF Referer against CSRF_COOKIE_DOMAIN

2015-05-26 Thread Django

#24496: Check CSRF Referer against CSRF_COOKIE_DOMAIN
--+
 Reporter:  mattrobenolt  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  CSRF  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  csrf  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

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

Re: [Django] #24375: Add ability to mark migration as "part of initial" in Migration

2015-05-26 Thread Django

#24375: Add ability to mark migration as "part of initial" in Migration
-+
 Reporter:  haeric   |Owner:  akulakov
 Type:  New feature  |   Status:  assigned
Component:  Migrations   |  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  fake migrations  | 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/064.671ea966c839dac1222ac22257d09c4b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24856: raw_id_fields popup missing

2015-05-26 Thread Django

#24856: raw_id_fields popup missing
---+--
 Reporter:  liwee  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  1.8
 Severity:  Normal |   Resolution:  worksforme
 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):

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


Comment:

 I had no trouble adding this to the tutorial:
 {{{
 class ChoiceAdmin(admin.ModelAdmin):
 raw_id_fields = ('question',)
 }}}
 We'll need more details such as steps to reproduce or a sample project we
 can download to see the error.

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

Re: [Django] #24506: Migrations are crashing after changing foreign key from auth.Group model to a proxy model of auth.Group (was: Proxying User model creates an invalid migration)

2015-05-26 Thread Django

#24506: Migrations are crashing after changing foreign key from auth.Group 
model to
a proxy model of auth.Group
+--
 Reporter:  tinloaf |Owner:  marcofucci
 Type:  Bug |   Status:  new
Component:  Migrations  |  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:  0   |UI/UX:  0
+--
Changes (by Ernest0x):

 * component:  Database layer (models, ORM) => Migrations


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.574b1fb93b18e52feb2c84e8ba6bbfad%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-05-26 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:  1
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by alasdairnicol):

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


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

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

Re: [Django] #24857: Add main entry point as an alias for django-admin

2015-05-26 Thread Django

#24857: Add __main__ entry point as an alias for django-admin
-+-
 Reporter:  tricoder42   |Owner:
 |  tricoder42
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by tricoder42):

 I've started working on it. I want to make `django/bin/django-admin.py` an
 alias for `django/__main__.py` so we don't have to duplicate code (just
 two lines though) but the best what I've got so far is:


 {{{
 # django/bin/django-admin.py
 #!/usr/bin/env python
 from runpy import run_module

 if __name__ == "__main__":
 run_module('django')
 }}}

 Not sure if it's worth it. I'll rather write some 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/068.17d8cca4c72e9518aba7b0a8a26af1d4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24857: Add main entry point as an alias for django-admin

2015-05-26 Thread Django

#24857: Add __main__ entry point as an alias for django-admin
-+-
 Reporter:  tricoder42   |Owner:
 |  tricoder42
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by bmispelon):

 * stage:  Unreviewed => Accepted


Comment:

 I think this is a good idea and there was support for it on the mailing
 list thread [1].

 The PR looks good but some basic tests would be nice.

 [1] https://groups.google.com/forum/#!searchin/django-developers/guessable
 /django-developers/_Mrf1nFVchk/tfpGyKatiHIJ

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

Re: [Django] #24846: MySQL Migration SchemaEditor default code is ignorant of other blob/text data types

2015-05-26 Thread Django

#24846: MySQL Migration SchemaEditor default code is ignorant of other blob/text
data types
-+-
 Reporter:  adamchainz   |Owner:
 |  adamchainz
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  mysql migrations | 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 claudep):

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

Re: [Django] #24857: Add main entry point as an alias for django-admin

2015-05-26 Thread Django

#24857: Add __main__ entry point as an alias for django-admin
-+-
 Reporter:  tricoder42   |Owner:
 |  tricoder42
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by tricoder42):

 * owner:  nobody => tricoder42
 * needs_docs:   => 1
 * status:  new => assigned
 * needs_tests:   => 1
 * needs_better_patch:   => 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/068.a69d3761cbe3366939edbe4beabd3604%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #24857: Add main entry point as an alias for django-admin

2015-05-26 Thread Django

#24857: Add __main__ entry point as an alias for django-admin
+
 Reporter:  tricoder42  |  Owner:  nobody
 Type:  New feature | Status:  new
Component:  Core (Management commands)  |Version:  master
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 There's a original pull request at
 https://github.com/django/django/pull/4588

 Add `__main__` entry point, so we can call management command via `python
 -m django`. It will behave as an alias for `django-admin` (`django-
 admin.py`).

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

[Django] #24856: raw_id_fields popup missing

2015-05-26 Thread Django

#24856: raw_id_fields popup missing
---+
 Reporter:  liwee  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  contrib.admin  |Version:  1.8
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Hi,

 My usual development server is running 1.7.x.
 Downloaded 1.8.2 today and copied my existing project over to 1.8.2.

 The popup for raw_id_fields seems to be missing. It was working on 1.7.x


 {{{
 raw_id_fields = ('cust', )
 }}}

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

57 matches

Mail list logo