Re: [Django] #24412: Red migration notice should be printed when running tests without --verbosity=2

[Django]

#24412: Red migration notice should be printed when running tests without
--verbosity=2
-+
 Reporter:  pzrq |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by pzrq):

 Thanks Markus, it is consistent with the 1.8 roadmap and the workaround is
 to watch closely `--verbosity=2 --keepdb`
 https://code.djangoproject.com/wiki/Version1.8Roadmap

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

Re: [Django] #24416: EmailMessage and send_email do not handle ugettext_lazy translated addresses correctly

[Django]

#24416: EmailMessage and send_email do not handle ugettext_lazy translated
addresses correctly
-+
 Reporter:  medmunds |Owner:  medmunds
 Type:  Bug  |   Status:  new
Component:  Core (Mail)  |  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by MarkusH):

 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #24413: Translations for language "en" missing

[Django]

#24413: Translations for language "en" missing
-+-
 Reporter:  ktosiek  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Uncategorized|  Version:  1.8alpha1
 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 bmispelon):

 For reference, here's what I did to reproduce the issue:

 1) Start a new project with `djangoadmin startproject myproject`
 2) Change `LANGUAGE_CODE = 'pl'` in `myproject/settings.py`
 3) Edit `myproject/urls.py` to contain the following:
 {{{#!python
 from django.conf.urls import url
 from django.http import HttpResponse
 from django.utils import translation

 def index(request):
 translation.activate('en')
 return HttpResponse(translation.ugettext('username'))

 urlpatterns = [
 url(r'^$', index),
 ]
 }}}
 4) Start `runserver` and navigate to the root URL

 When doing that, you'll see that the string `'username'` remains
 translated to Polish (I believe that's the issue being reported here)

 You'll note that using `translation.activate('en-us')` in the view makes
 the correct translation appear again.

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

Re: [Django] #24416: EmailMessage and send_email do not handle ugettext_lazy translated addresses correctly

[Django]

#24416: EmailMessage and send_email do not handle ugettext_lazy translated
addresses correctly
-+--
 Reporter:  medmunds |Owner:  medmunds
 Type:  Bug  |   Status:  new
Component:  Core (Mail)  |  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by medmunds):

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


Comment:

 Test case and fix: https://github.com/medmunds/django/tree/ticket_24416
 Pull request: https://github.com/django/django/pull/4211

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

Re: [Django] #24413: Translations for language "en" missing

[Django]

#24413: Translations for language "en" missing
-+-
 Reporter:  ktosiek  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Uncategorized|  Version:  1.8alpha1
 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 bmispelon):

 * needs_docs:   => 0
 * needs_better_patch:   => 0
 * severity:  Normal => Release blocker
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 Hi,

 I think I can reproduce this locally but I haven't managed to build a
 failing test case yet.

 Doing some manual bisecting, it seems that
 a5f6cbce07b5f3ab48d931e3fd1883c757fb9b45 introduced the regression.

 I'm bumping to "Release blocker" since it's a regression from 1.7.

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

Re: [Django] #24415: select_related() uses always QuerySet and Query classes from originating Model on spatialite

[Django]

#24415: select_related() uses always QuerySet and Query classes from originating
Model on spatialite
-+-
 Reporter:  jaimemarijke |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  query orm| Triage Stage:
  spatialite |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

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


Comment:

 Can you reproduce against master?

 The report for #12344 talks about a traceback, could you provide a small
 testcase to reproduce the issue with the raised exception traceback and
 re-open this ticket.

 Marking as ''needsinfo'' since the tests added in [a488589461] are passing
 on the [http://djangoci.com/job/django-master-
 
trusty/database=spatialite,label=trusty,python=python2.7/lastCompletedBuild/testReport/gis_tests.relatedapp.tests/RelatedGeoModelTest/
 Spatialite CI].

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

[Django] #24416: EmailMessage and send_email do not handle ugettext_lazy translated addresses correctly

[Django]

#24416: EmailMessage and send_email do not handle ugettext_lazy translated
addresses correctly
-+--
 Reporter:  medmunds |  Owner:  medmunds
 Type:  Bug  | Status:  new
Component:  Core (Mail)  |Version:  1.7
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+--
 Most (all?) of the core email backends seem to have issues with lazy
 strings used as addresses: to, cc, etc.:

 {{{
 >>> from django.utils.translation import ugettext_lazy as _
 >>> from django.core.mail import send_mail
 >>> send_mail('Subject', 'Content', _('f...@example.com'),
 [_('t...@example.com')])
 ... TypeError: sequence item 0: expected str instance, __proxy__ found
 }}}

 (#7574 fixed this for subject and content, but not the address fields.)

 Patch coming shortly.

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

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

[Django] #24415: select_related() uses always QuerySet and Query classes from originating Model on spatialite

[Django]

#24415: select_related() uses always QuerySet and Query classes from originating
Model on spatialite
--+
 Reporter:  jaimemarijke  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.6
 Severity:  Normal|   Keywords:  query orm
  |  spatialite
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 The issue described in https://code.djangoproject.com/ticket/12344 is
 marked as fixed for the Oracle spatial backend but repros for me when
 using spatialite.

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

Re: [Django] #24414: Add example of Prefetch object usage to docs

[Django]

#24414: Add example of Prefetch object usage to docs
---+
 Reporter:  coolRR |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Documentation  |  Version:  1.7
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by collinanderson):

 Here's a snippet from my code:
 {{{
 posts = Post.objects.filter(post_type='post',
 post_status='publish').exclude(id=self.id).order_by('-post_date')
 self.categories.prefetch_related(Prefetch('post_set', queryset=posts,
 to_attr='posts'))
 }}}

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

[Django] #24414: Add example of Prefetch object usage to docs

[Django]

#24414: Add example of Prefetch object usage to docs
---+
 Reporter:  coolRR |  Owner:  nobody
 Type:  New feature| Status:  new
Component:  Documentation  |Version:  1.7
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Example needed here to clarify:
 
https://docs.djangoproject.com/en/1.7/ref/models/queries/#django.db.models.Prefetch

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

Re: [Django] #24414: Add example of Prefetch object usage to docs

[Django]

#24414: Add example of Prefetch object usage to docs
---+
 Reporter:  coolRR |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Documentation  |  Version:  1.7
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by collinanderson):

 * cc: cmawebsite@… (added)
 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 agreed

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

Re: [Django] #24379: Document that user management tools don't work with remote authentication

[Django]

#24379: Document that user management tools don't work with remote 
authentication
--+
 Reporter:  mkesper   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by RossBrunton):

 I decided to give this a go, and created a pull request thing at:
 https://github.com/django/django/pull/4210

 Sorry if I'm doing something wrong with this process, this is my first
 time contributing.

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

Re: [Django] #20846: Increase contrib.auth's User.username length

[Django]

#20846: Increase contrib.auth's User.username length
--+
 Reporter:  ivoras@…  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * has_patch:  1 => 0
 * version:  1.5 => master
 * easy:  1 => 0
 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #24370: Recommend that all new projects use a custom user model

[Django]

#24370: Recommend that all new projects use a custom user model
--+
 Reporter:  carljm|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by carljm):

 I think adding a second startproject command or template, or adding
 something built-in which uses email address is username, is definitely
 going too far for this ticket.

--
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.e58f0fa86c34331cb23ebfc7de93b02c%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

[Django]

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

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.922c36ea3335060c520a9acd9b37c8e3%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

[Django]

#24340: Nested deconstruction does not descend into lists, tuples or dicts
+
 Reporter:  gasman  |Owner:  gasman
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  1.7
 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 gasman):

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

Re: [Django] #24370: Recommend that all new projects use a custom user model

[Django]

#24370: Recommend that all new projects use a custom user model
--+
 Reporter:  carljm|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by collinanderson):

 * cc: cmawebsite@… (added)


Comment:

 Maybe we could make a `manage.py startuserapp` which creates an app with a
 custom user that uses an email address as the username by default.

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

Re: [Django] #24403: makemessages when run for a django app and no settings will fail on settings.STATIC_ROOT and settings.MEDIA_ROOT not being set

[Django]

#24403: makemessages when run for a django app and no settings will fail on
settings.STATIC_ROOT and settings.MEDIA_ROOT not being set
-+-
 Reporter:  silkentrance |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  1.8alpha1
  commands)  |
 Severity:  Normal   |   Resolution:  duplicate
 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 claudep):

 You will get a new release with `pip install --pre ...`

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

Re: [Django] #24369: flush requires migrations

[Django]

#24369: flush requires migrations
-+-
 Reporter:  tanner   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Management |  Version:  1.7
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  flush| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

 * has_patch:  0 => 1


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

[Django] #24413: Translations for language "en" missing

[Django]

#24413: Translations for language "en" missing
---+---
 Reporter:  ktosiek|  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Uncategorized  |Version:  1.8alpha1
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+---
 It seems translations for "en" are missing, which gives wrong results for
 LANGUAGE_CODE != 'en'.

 I have LANGUAGE_CODE = 'pl', use the i18n/setlang/ view to set my current
 language to 'en', and visit a login page based on
 django.contrib.auth.forms.AuthenticationForm. Field labels are still in
 polish, but the strings the I've explicitly translated are in english. I
 expected the labels to use english versions, but looking here
 
https://github.com/django/django/blob/master/django/contrib/auth/locale/en/LC_MESSAGES/django.po
 it looks like none of those are actually provided (so Django falls back to
 LANGUAGE_CODE).

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/050.3453a0e2ca523da88c57fea3211477f7%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

[Django]

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

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


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

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

Re: [Django] #24407: Initial migration fails if app name has upper-case letters on Oracle

[Django]

#24407: Initial migration fails if app name has upper-case letters on Oracle
+
 Reporter:  CarstenF|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.7
 Severity:  Normal  |   Resolution:
 Keywords:  oracle  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by MarkusH):

 FWIW this is also a bit related to #24337.

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

Re: [Django] #24412: Red migration notice should be printed when running tests without --verbosity=2

[Django]

#24412: Red migration notice should be printed when running tests without
--verbosity=2
-+
 Reporter:  pzrq |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by MarkusH):

 * version:  1.8alpha1 => master
 * type:  Uncategorized => New feature
 * stage:  Unreviewed => Accepted


Comment:

 We don't accept any feature requests for 1.8 anymore, but I accepted it
 for the next version.

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

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

Re: [Django] #15574: IndexError: list index out of range caused by inline formsets

[Django]

#15574: IndexError: list index out of range caused by inline formsets
+
 Reporter:  poswald |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Forms   |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  inline formset  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by collinanderson):

 * cc: cmawebsite@… (added)


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

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

Re: [Django] #22689: inlines with sliced and ordered querysets save incorrectly when underlying data has changed since page load

[Django]

#22689: inlines with sliced and ordered querysets save incorrectly when 
underlying
data has changed since page load
---+
 Reporter:  cspinelive |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.7
 Severity:  Normal |   Resolution:
 Keywords:  admin inline   | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timgraham):

 * stage:  Unreviewed => Accepted


Comment:

 I meant that I think solving #15574 would fix the issue. But sure, we can
 leave this ticket open.

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

Re: [Django] #22689: inlines with sliced and ordered querysets save incorrectly when underlying data has changed since page load

[Django]

#22689: inlines with sliced and ordered querysets save incorrectly when 
underlying
data has changed since page load
---+--
 Reporter:  cspinelive |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.7
 Severity:  Normal |   Resolution:
 Keywords:  admin inline   | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Ernest0x):

 * status:  closed => new
 * version:  1.7-beta-2 => 1.7
 * resolution:  duplicate =>


Comment:

 Replying to [comment:1 timo]:
 > I think it's a probably a duplicate of #15574.

 Why do you think this is a duplicate of #15574?

 I am experiencing exactly the same behavior as the OP reports with 1.7.4
 (inlines with slicing on the formset's queryset). In addition, in my case,
 although the admin logs say that the objects were changed, in fact, they
 were (re-)added as new (same values, different ids)! It seems that
 something really bad is happening...

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

Re: [Django] #24394: Running tests fails when DATABASES['default'] = {}

[Django]

#24394: Running tests fails when DATABASES['default'] = {}
---+
 Reporter:  trecouvr   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.7
 Severity:  Normal |   Resolution:
 Keywords:  test   | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by knbk):

 * stage:  Unreviewed => Accepted


Comment:

 It is indeed a bug, as the documentation on
 [https://docs.djangoproject.com/en/1.7/topics/db/multi-db/#defining-your-
 databases multi-db setups] explicitly allows 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.17387310f53dad1642e64808e170d990%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #20487: oracle: case mixup causes ORA-00918: column ambiguously defined error

[Django]

#20487: oracle: case mixup causes ORA-00918: column ambiguously defined error
-+-
 Reporter:  Charlie.Tang@…   |Owner:  shai
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle ORA-00918 | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by CarstenF):

 * cc: carsten.fuchs@… (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/082.5b92003ec136e4c03b9f38fdf9c308b8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24407: Initial migration fails if app name has upper-case letters on Oracle

[Django]

#24407: Initial migration fails if app name has upper-case letters on Oracle
+
 Reporter:  CarstenF|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.7
 Severity:  Normal  |   Resolution:
 Keywords:  oracle  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by CarstenF):

 Ok, many thanks for your feedback! I was not aware that the scope of this
 issue is actually much broader...

 (In hindsight, it is clear to me that faking the initial migration was the
 right workaround, but I deliberately did not use `--fake` because from a
 user's perspective, knowing little about the implementation details, I did
 not want to forgo any other issues it might have identified. I did not
 expect any, but it seemed like a good extra verification step.)

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

Re: [Django] #24411: Creating a model called Item breaks the admin "delete selected" action

[Django]

#24411: Creating a model called Item breaks the admin "delete selected" action
-+-
 Reporter:  yoyoma   |Owner:  timgraham
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.8alpha1
 Severity:  Release blocker  |   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
-+-

Comment (by Tim Graham ):

 In [changeset:"dfcdf64d475418ed579da2621e331cc4d03a78e5"]:
 {{{
 #!CommitTicketReference repository=""
 revision="dfcdf64d475418ed579da2621e331cc4d03a78e5"
 [1.8.x] Fixed #24411 -- Avoided dict key/method clash in admin delete
 views.

 Backport of 47b35b1844b2adc167e64674824873991e9c4c2b from master
 }}}

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

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

Re: [Django] #24411: Creating a model called Item breaks the admin "delete selected" action

[Django]

#24411: Creating a model called Item breaks the admin "delete selected" action
-+-
 Reporter:  yoyoma   |Owner:  timgraham
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.8alpha1
 Severity:  Release blocker  |   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 Tim Graham ):

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


Comment:

 In [changeset:"47b35b1844b2adc167e64674824873991e9c4c2b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="47b35b1844b2adc167e64674824873991e9c4c2b"
 Fixed #24411 -- Avoided dict key/method clash in admin delete views.
 }}}

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

Re: [Django] #24411: Creating a model called Item breaks the admin "delete selected" action

[Django]

#24411: Creating a model called Item breaks the admin "delete selected" action
-+-
 Reporter:  yoyoma   |Owner:  timgraham
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  1.8alpha1
 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):

 * has_patch:  0 => 1
 * severity:  Normal => Release blocker


Comment:

 [https://github.com/django/django/pull/4208 PR]

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

Re: [Django] #24403: makemessages when run for a django app and no settings will fail on settings.STATIC_ROOT and settings.MEDIA_ROOT not being set

[Django]

#24403: makemessages when run for a django app and no settings will fail on
settings.STATIC_ROOT and settings.MEDIA_ROOT not being set
-+-
 Reporter:  silkentrance |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  1.8alpha1
  commands)  |
 Severity:  Normal   |   Resolution:  duplicate
 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 silkentrance):

 Oh, great I did search for makemessages / django-admin but did not search
 for closed issues as well...

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

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

Re: [Django] #24409: Combine filesystem and app directories template loader implementation

[Django]

#24409: Combine filesystem and app directories template loader implementation
--+
 Reporter:  prestontimmons|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Template system   |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #24398: Built in webserver not reloading Python files upon requests

[Django]

#24398: Built in webserver not reloading Python files upon requests
--+--
 Reporter:  hyperknot |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Uncategorized |  Version:  1.7
 Severity:  Normal|   Resolution:  needsinfo
 Keywords:  server runserver  | Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by timgraham):

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


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

Re: [Django] #24411: Creating a model called Item breaks the admin "delete selected" action

[Django]

#24411: Creating a model called Item breaks the admin "delete selected" action
---+-
 Reporter:  yoyoma |Owner:  timgraham
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  1.8alpha1
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by timgraham):

 * status:  new => assigned
 * component:  Template system => contrib.admin
 * version:  master => 1.8alpha1
 * owner:  nobody => timgraham
 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


Comment:

 It's a regression in Django 1.8.

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

Re: [Django] #24408: "pip install .../master.zip" fails with UnicodeEncodeError in pip

[Django]

#24408: "pip install .../master.zip" fails with UnicodeEncodeError in pip
---+--
 Reporter:  blueyed|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Packaging  |  Version:  master
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by timgraham):

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


Comment:

 Looks like a bug in pip not Django. It might be fixed by
 https://github.com/pypa/pip/pull/1473.

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

Re: [Django] #24347: parameter 'widget' of BoundField.as_widget is ignored

[Django]

#24347: parameter 'widget' of BoundField.as_widget is ignored
-+-
 Reporter:  srkunze  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.8alpha1
 Severity:  Normal   |   Resolution:
 Keywords:  BoundField,  | Triage Stage:
  as_widget  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Description changed by srkunze:

Old description:

> 'as_widget' has the parameter 'widget' which renders the field. However,
> this parameter is not used all the time during the 'as_widget' call.
>
> The method 'data', which is (indirectly via 'value') called by
> 'as_widget', ALWAYS uses the default widget of the field which leads to
> issues like formatting etc.
>
> We recognized this issue when using 'show_hidden_initial=True' and
> widgets for datetime objects.
>
> The problem can also be observed when using BoundField.as_hidden as it
> uses 'as_widget' as well.
>
> cf.
> as_widget:
> https://github.com/django/django/blob/master/django/forms/forms.py#L526
> data:
> https://github.com/django/django/blob/master/django/forms/forms.py#L569
> as_hidden:
> https://github.com/django/django/blob/master/django/forms/forms.py#L562
>
> Versions: 1.4, 1.5, 1.6, 1.7, 1.8, master

New description:

 'as_widget' has the parameter 'widget' which renders the field. However,
 this parameter is not used all the time during the 'as_widget' call.

 The method 'data', which is (indirectly via 'value') called by
 'as_widget', ALWAYS uses the default widget of the field which leads to
 issues like formatting etc.

 We recognized this issue when using 'show_hidden_initial=True' and widgets
 for datetime objects.

 The problem can also be observed when using BoundField.as_hidden as it
 uses 'as_widget' as well.

 cf.
 as_widget:
 https://github.com/django/django/blob/1.8a1/django/forms/forms.py#L566
 data:
 https://github.com/django/django/blob/1.8a1/django/forms/forms.py#L609
 as_hidden:
 https://github.com/django/django/blob/1.8a1/django/forms/forms.py#L602

 Versions: 1.4, 1.5, 1.6, 1.7, 1.8, master

--

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

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

Re: [Django] #24369: flush requires migrations

[Django]

#24369: flush requires migrations
-+-
 Reporter:  tanner   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Management |  Version:  1.7
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  flush| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by tanner):

 looks good. thank you

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

Re: [Django] #24352: Coercing ManyRelatedManager to string raises StopIteration exception

[Django]

#24352: Coercing ManyRelatedManager to string raises StopIteration exception
-+-
 Reporter:  rasca|Owner:  gmunumel
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.7
  (models, ORM)  |
 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 gmunumel):

 Yes, I think the bug is 1.7 specific. I try running this test in
 m2m_regress on master branch.

 {{{
 def test_many_related_manager_str(self):
 c1 = TagCollection.objects.create(name='c1')
 self.assertIn('ManyRelatedManager', str(c1.tags))
 }}}

 But always get an error related to:

 {{{
 Traceback (most recent call last):
   File "/home/alucard/workspace/Code/django/tests/m2m_regress/tests.py",
 line 117, in test_many_related_manager_str
 self.assertIn('ManyRelatedManager', str(c1.tags))
 AssertionError: u'ManyRelatedManager' not found in 'm2m_regress.Tag.None'
 }}}

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