Re: [Django] #29400: mark_safe() doesn't work as a decorator for template filters and tags

[Django]

#29400: mark_safe() doesn't work as a decorator for template filters and tags
-+
 Reporter:  Torsten Bronger  |Owner:  oliver
 Type:  Bug  |   Status:  assigned
Component:  Template system  |  Version:  2.0
 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 oliver):

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


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

Re: [Django] #29392: Command parsing does not handle options that conflict with `--settings`/`--pythonpath`

[Django]

#29392: Command parsing does not handle options that conflict with
`--settings`/`--pythonpath`
-+-
 Reporter:  Ryan P Kilby |Owner:  lefcourn
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"2dcc5d629a6439b5547cdd6e67815cabf608fcd4" 2dcc5d62]:
 {{{
 #!CommitTicketReference repository=""
 revision="2dcc5d629a6439b5547cdd6e67815cabf608fcd4"
 Fixed #29392 -- Disallowed use of abbreviated forms of --settings and
 --pythonpath management command options.
 }}}

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

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

Re: [Django] #16470: Make FileResponse set the Content-Disposition header (was: RFC5987/RFC6266 Support (Content-Disposition headers))

[Django]

#16470: Make FileResponse set the Content-Disposition header
-+-
 Reporter:  mnot@…   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  HTTP handling|  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:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

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

Re: [Django] #29407: django.forms field in edit dialog don't display default values

[Django]

#29407: django.forms field in edit dialog don't display default values
-+-
 Reporter:  Alex Volkov  |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Uncategorized|  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  forms,   | Triage Stage:
  django.forms, fields   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by oliver):

 * owner:  oliver => (none)
 * 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/065.cd2387085e64146316a9fcc85650f637%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29407: django.forms field in edit dialog don't display default values

[Django]

#29407: django.forms field in edit dialog don't display default values
-+-
 Reporter:  Alex Volkov  |Owner:  oliver
 Type:  Bug  |   Status:  assigned
Component:  Uncategorized|  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  forms,   | Triage Stage:
  django.forms, fields   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by oliver):

 * status:  new => assigned
 * owner:  (none) => oliver


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

Re: [Django] #29407: django.forms field in edit dialog don't display default values

[Django]

#29407: django.forms field in edit dialog don't display default values
-+-
 Reporter:  Alex Volkov  |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Uncategorized|  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  forms,   | Triage Stage:
  django.forms, fields   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by oliver):

 * owner:  oliver => (none)
 * 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/065.5472ce81a33e5513a6c66ec9e6b4e569%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29407: django.forms field in edit dialog don't display default values

[Django]

#29407: django.forms field in edit dialog don't display default values
-+-
 Reporter:  Alex Volkov  |Owner:  oliver
 Type:  Bug  |   Status:  assigned
Component:  Uncategorized|  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  forms,   | Triage Stage:
  django.forms, fields   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by oliver):

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


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

Re: [Django] #28834: Fields cache should attempt to follow ancestor links on lookup failures

[Django]

#28834: Fields cache should attempt to follow ancestor links on lookup failures
-+-
 Reporter:  Simon Charette   |Owner:  Simon
 Type:   |  Charette
  Cleanup/optimization   |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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
-+-

Comment (by Tim Graham ):

 In [changeset:"265506bbc347a6b3fcc6c66ab1a2417b3b7ea57a" 265506bb]:
 {{{
 #!CommitTicketReference repository=""
 revision="265506bbc347a6b3fcc6c66ab1a2417b3b7ea57a"
 Refs #28834 -- Moved ancestor field cached value fallback to related
 fields descriptor.
 }}}

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

Re: [Django] #28919: Add support for Common Table Expression (CTE) queries

[Django]

#28919: Add support for Common Table Expression (CTE) queries
-+-
 Reporter:  Daniel Miller|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  QuerySet.extra   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Matthew Schinckel):

 * cc: Matthew Schinckel (added)


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

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

Re: [Django] #29405: Missing dependecies on the contribuiting tutorial

[Django]

#29405: Missing dependecies on the contribuiting tutorial
---+--
 Reporter:  Benny Daon |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  2.0
 Severity:  Normal |   Resolution:  wontfix
 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 Tim Graham):

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


Comment:

 The tutorial says:

 > If you encounter an error during the installation, your system might be
 missing a dependency for one or more of the Python packages. Consult the
 failing package’s documentation or search the Web with the error message
 that you encounter.

 The issue has been raised before and the consensus is that it's not
 Django's job to document all the possibilities for various operating
 systems.

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

[Django] #29407: django.forms field in edit dialog don't display default values

[Django]

#29407: django.forms field in edit dialog don't display default values
-+-
   Reporter:  avolkov|  Owner:  nobody
   Type:  Bug| Status:  new
  Component: |Version:  2.0
  Uncategorized  |   Keywords:  forms,
   Severity:  Normal |  django.forms, fields
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 I created a project with Django 2.0.4 running on Python 3.6.5 with
 cookiecutter django template.

 I created an app (survey) then created a form using a model with model
 form interface view and template. Everything works except when I added a
 form for editing existing model values, the form fields with default
 values don't get populated. Here's a snippet from my implementation:


 {{{
 #!div style="font-size: 80%"
 models.py
   {{{#!python
   from django.db import models

 class Survey(models.Model):

class Meta:
"""Set composite key for file_number/location fields"""
unique_together = (('file_number', 'court_location', ))

 file_number = models.CharField(max_length=127)
 location = models.ForeignKey(Location, on_delete=models.PROTECT)
   }}}
 }}}


 {{{
 #!div style="font-size: 80%"
 forms.py
   {{{#!python
 from django import forms

 class SurveyForm(forms.ModelForm):
 """Survey Form along with customizations"""

 def __init__(self, *args, **kwargs):
 self.user = kwargs.pop('user', None)
 super().__init__(*args, **kwargs)
 # Only show locations available to the user
 locations =
 Location.objects.filter(contract__user_id=self.user.id)
 self.fields['location'].queryset = locations

 class Meta:
 model = Survey
 fields = '__all__'
   }}}
 }}}

 {{{
 #!div style="font-size: 80%"
 views.py
   {{{#!python
 class SurveyEdit(View):
 """Edit form for SurveyForm class"""

 def get(self, request, survey_id):
 survey_obj = Survey.objects.get(id=survey_id)
 survey_form = SurveyForm(
 request.GET, user=request.user, instance=survey_obj)
 return render(
 request,
 'survey_edit_form.html',
 {'survey_form': survey_form, 'survey_id': survey_id}
 )

 def post(self, request, survey_id):
 sf = SurveyForm(
 request.POST,
 user=request.user,
 instance=Survey.objects.get(id=survey_id))
 if sf.is_valid():
 sf.save()
 messages.add_message(
 request,
 messages.SUCCESS,
 "Survey {} was
 updated".format(sf.cleaned_data['file_number'])
 )
 return HttpResponseRedirect('/survey/list')
 error_message(sf, request)
 return render(
 request,
 'survey_edit_form.html',
 {'survey_form': sf, 'survey_id': survey_id}
 )
   }}}
 }}}


 {{{
 #!div style="font-size: 80%"
 survey_edit_form.html
   {{{#!jinja
 {% extends "base.html" %}

 {% block title %}
   {% block head_title %}
   Edit Survey
   {% endblock head_title %}
 {% endblock title %}

 {% block content %}
 
   
 
   {% csrf_token %}
   {% for field in survey_form %}
 
   {{ field.label }}
   {{ field }}
 
   {% endfor %}
   
 
   
 
 {% endblock %}
   }}}
 }}}

 {{{
 #!div style="font-size: 80%"
 url.py
   {{{#!python
   path('edit/', login_required(SurveyEdit.as_view()),
 name='edit'),
   }}}
 }}}

 I also have the following test case, which verifiees that the data is
 loaded into the form

 {{{
 #!div style="font-size: 80%"
 tests.py
   {{{#!python
 def test_006_edit_data_is_loaded(self):
 """When editing a survey through SurveyForm, verify Survey data is
 loaded"""
 client = Client()
 client.force_login(self.user)
 # create survey object from generated data
 edit_survey_data = copy(gen_survey_data(self))
 edit_survey = Survey(**edit_survey_data)
 edit_survey.save()
 # go to edit page
 edit_url = '/survey/edit/{}'.format(edit_survey.id)
 resp = client.get(edit_url)
 # verify that field values were loaded
 content = str(resp.content)
 self.assertIn(edit_survey_data['file_number'], content)"
   }}}
 }}}


 The problem seems to be somewhere either in django.forms.boundfield

 
https://github.com/django/django/blob/c591bc3ccece1514d6b419826c7fa36ada9d9213/django/forms/boundfield.py#L126

 {{{
 #!div style="font-size: 80%"
   {{{#!python
 def value(self):
 data = self.initial
 if self.form.is_bound:
 

[Django] #29406: Add Referrer-Policy header support

[Django]

#29406: Add Referrer-Policy header support
-+---
   Reporter:  James Bennett  |  Owner:  James Bennett
   Type:  New feature| Status:  assigned
  Component:  Utilities  |Version:  master
   Severity:  Normal |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+---
 Background information on django-dev list:

 https://groups.google.com/forum/#!topic/django-developers/DDpkrvFdnvk

 Other parts of that proposal still need work, but Referrer-Policy seemed
 to have consensus to go ahead and do.

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

[Django] #29405: Missing dependecies on the contribuiting tutorial

[Django]

#29405: Missing dependecies on the contribuiting tutorial
-+
   Reporter:  Benny Daon |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Documentation  |Version:  2.0
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 I followed the instruction in the "Writing your first patch for Django"
 page and in order to install the tests requirements I had to install
 python-dev, zlib and libmemcached. The page mentions neither of them.

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

Re: [Django] #29404: Add --show-sql option to the shell command

[Django]

#29404: Add --show-sql option to the shell command
-+-
 Reporter:  Ivan Khomutov|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  2.0
  commands)  |
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  shell, sql   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz):

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


Comment:

 There is a popular package you can use to do that: https://django-
 extensions.readthedocs.io/en/latest/shell_plus.html
 You may discuss on the django-developers mailing list if you think it
 should be in Django core, but you should provide convincing arguments.

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

Re: [Django] #29291: Conditional expressions and ~Q queries

[Django]

#29291: Conditional expressions and ~Q queries
-+-
 Reporter:  Bo Marchman  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by rjsparks):

 I think this is just a consequence of the way annotate works on a reverse
 ForeignKey rather than being a bug in the conditional expression.

 {{{
 In [53]: Application.objects.annotate(
 ...: needs_review=Case(
 ...: When(~Q(score__reviewed=True), then=V(True)),
 ...: default=V(False),
 ...: output_field=BooleanField()
 ...: )
 ...: )
 Out[53]: , , ]>

 In [54]: Application.objects.annotate(
 ...: needs_review=Case(
 ...: When(~Q(score__reviewed=True), then=V(True)),
 ...: default=V(False),
 ...: output_field=BooleanField()
 ...: )
 ...: ).values_list('needs_review',flat=True)
 Out[54]: 
 }}}

 Or more simply:

 {{{
 In [55]:
 Application.objects.annotate(score_has_been_reviewed=F('score__reviewed
 ...: '))
 Out[55]: , , ]>

 In [56]:
 Application.objects.annotate(score_has_been_reviewed=F('score__reviewed
 ...: ')).values_list('score_has_been_reviewed',flat=True)
 Out[56]: 
 }}}

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

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

Re: [Django] #29392: Command parsing does not handle options that conflict with `--settings`/`--pythonpath`

[Django]

#29392: Command parsing does not handle options that conflict with
`--settings`/`--pythonpath`
-+-
 Reporter:  Ryan P Kilby |Owner:  lefcourn
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 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 Ryan P Kilby):

 Thanks for the review Carlton. Added a note to the misc backwards
 incompatibility section.

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

Re: [Django] #29297: Exception ignored in: . at 0x111aafe08>

[Django]

#29297: Exception ignored in: . at 0x111aafe08>
-+-
 Reporter:  kingctan |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 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 Shaheed Haque):

 I see, thanks.

 I've Google'd around, and see other references to the contract of th C API
 being broken. Sadly, I don't see any obvious way to narrow down the
 cuplrit short of strace.

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

Re: [Django] #29392: Command parsing does not handle options that conflict with `--settings`/`--pythonpath`

[Django]

#29392: Command parsing does not handle options that conflict with
`--settings`/`--pythonpath`
-+-
 Reporter:  Ryan P Kilby |Owner:  lefcourn
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 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 lefcourn):

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

[Django] #29404: Add --show-sql option to the shell command

[Django]

#29404: Add --show-sql option to the shell command
-+-
   Reporter:  Ivan   |  Owner:  nobody
  Khomutov   |
   Type:  New| Status:  new
  feature|
  Component:  Core   |Version:  2.0
  (Management commands)  |
   Severity:  Normal |   Keywords:  shell, sql
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Basically, it refers to this SO answer
 [https://stackoverflow.com/a/5835465]
 It is very helpful feature, why not to try to include this into shell
 command itself?

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

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

Re: [Django] #29398: Clarify that cascade deletion doesn't invoke .delete() on the cascaded objects

[Django]

#29398: Clarify that cascade deletion doesn't invoke .delete() on the cascaded
objects
--+
 Reporter:  Daniel Quinn  |Owner:  tomlinsj
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.11
 Severity:  Normal|   Resolution:
 Keywords:  delete cascade| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by tomlinsj):

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


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

Re: [Django] #29299: Add type hints (PEP 484) and variable annotations (PEP 526)

[Django]

#29299: Add type hints (PEP 484) and variable annotations (PEP 526)
-+-
 Reporter:  Andreas Galazis  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Other) |  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Vlastimil Zíma):

 * cc: Vlastimil Zíma (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/066.bbd044f10341e742b01e638d50cedb4f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.