Re: [Django] #22564: Migrations generated by Python 2 do not work in Python 3 due to b'' prefix on strings

[Django]

#22564: Migrations generated by Python 2 do not work in Python 3 due to b'' 
prefix
on strings
-+-
 Reporter:  timo |Owner:  claudep
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:
 Severity:  Release blocker  |  1.7-beta-2
 Keywords:   |   Resolution:
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by loic84):

 * stage:  Accepted => Ready for checkin


Comment:

 LGTM.

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

Re: [Django] #22563: Migration of admin.LogEntry.user fails.

[Django]

#22563: Migration of admin.LogEntry.user fails.
-+--
 Reporter:  efrinut@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-beta-2
 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 marfire):

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

Re: [Django] #22570: Form.__getitem__ KeyError should be more descriptive

[Django]

#22570: Form.__getitem__ KeyError should be more descriptive
--+
 Reporter:  bendavis78|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Forms |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"549b65824184711823e6a8c38ccf7365f10023d8"]:
 {{{
 #!CommitTicketReference repository=""
 revision="549b65824184711823e6a8c38ccf7365f10023d8"
 [1.7.x] Fixed #22570 -- Made Form.__getitem__ KeyError more descriptive.

 Backport of df60db0e78 from master
 }}}

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

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

[django/django] 549b65: [1.7.x] Fixed #22570 -- Made Form.__getitem__ KeyE...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 549b65824184711823e6a8c38ccf7365f10023d8
  
https://github.com/django/django/commit/549b65824184711823e6a8c38ccf7365f10023d8
  Author: Ben Davis 
  Date:   2014-05-05 (Mon, 05 May 2014)

  Changed paths:
M django/forms/forms.py
M tests/forms_tests/tests/test_forms.py

  Log Message:
  ---
  [1.7.x] Fixed #22570 -- Made Form.__getitem__ KeyError more descriptive.

Backport of df60db0e78 from master


-- 
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/536826933320b_16451197d4094917%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22570: Form.__getitem__ KeyError should be more descriptive

[Django]

#22570: Form.__getitem__ KeyError should be more descriptive
--+
 Reporter:  bendavis78|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Forms |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"df60db0e7872796b4a48e62e9733f85c8ddf8306"]:
 {{{
 #!CommitTicketReference repository=""
 revision="df60db0e7872796b4a48e62e9733f85c8ddf8306"
 Fixed #22570 -- Made Form.__getitem__ KeyError more descriptive.
 }}}

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

[django/django] df60db: Fixed #22570 -- Made Form.__getitem__ KeyError mor...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: df60db0e7872796b4a48e62e9733f85c8ddf8306
  
https://github.com/django/django/commit/df60db0e7872796b4a48e62e9733f85c8ddf8306
  Author: Ben Davis 
  Date:   2014-05-05 (Mon, 05 May 2014)

  Changed paths:
M django/forms/forms.py
M tests/forms_tests/tests/test_forms.py

  Log Message:
  ---
  Fixed #22570 -- Made Form.__getitem__ KeyError more descriptive.


-- 
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/53682675c6268_ebc1397d3496712%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22424: Default value for TextField

[Django]

#22424: Default value for TextField
-+--
 Reporter:  Nevsky   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-beta-1
 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 loic84):

 * cc: loic84 (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/064.20fc899c872c7c94242203244a678753%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22337: makemigrations not working when Field takes FileSystemStorage parameter

[Django]

#22337: makemigrations not working when Field takes FileSystemStorage parameter
-+-
 Reporter:  nliberg  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:
 Severity:  Release blocker  |  1.7-beta-1
 Keywords:  FileSystemStorage,   |   Resolution:
  migrations | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by loic84):

 Why not using `®deconstructible` from `django.utils.deconstruct`? That
 should work with most subclasses of storage without extra efforts from
 their authors'.

 Regarding skipping storage in `deconstruct()`, that means `FileField`
 wouldn't work in `RunPython` operation, I'd rather keep the fake ORM as
 capable as possible.

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

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

Re: [Django] #22579: validate_email accepts trailing dash

[Django]

#22579: validate_email accepts trailing dash
--+
 Reporter:  jason@…   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by claudep):

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


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

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

Re: [Django] #22580: dumpdata don't work with sub app

[Django]

#22580: dumpdata don't work with sub app
-+-
 Reporter:  Fabio Caritas|Owner:  nobody
  Barrionuevo da Luz   |   Status:  closed
 Type:  Uncategorized|  Version:  1.6
Component:  Core (Management |   Resolution:  invalid
  commands)  | Triage Stage:
 Severity:  Normal   |  Unreviewed
 Keywords:  dumpdata management  |  Needs documentation:  0
  commands subapp|  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by carljm):

 Many management commands accept app labels, so it doesn't make sense to
 document this specifically for dumpdata. It seems like the 1.6 docs don't
 include a clear definition of "app label" (that I can find); however, this
 has already been addressed for 1.7 in
 https://docs.djangoproject.com/en/dev/ref/applications/

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

Re: [Django] #22564: Migrations generated by Python 2 do not work in Python 3 due to b'' prefix on strings

[Django]

#22564: Migrations generated by Python 2 do not work in Python 3 due to b'' 
prefix
on strings
-+--
 Reporter:  timo |Owner:  claudep
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7-beta-2
 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 claudep):

 * has_patch:  0 => 1


Comment:

 PR: https://github.com/django/django/pull/2635

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

Re: [Django] #22424: Default value for TextField

[Django]

#22424: Default value for TextField
-+--
 Reporter:  Nevsky   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-beta-1
 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 loic84):

 @Nevsky could you check if this solves your problem?
 https://github.com/django/django/pull/2634

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

Re: [Django] #22580: dumpdata don't work with sub app

[Django]

#22580: dumpdata don't work with sub app
-+-
 Reporter:  Fabio Caritas|Owner:  nobody
  Barrionuevo da Luz   |   Status:  closed
 Type:  Uncategorized|  Version:  1.6
Component:  Core (Management |   Resolution:  invalid
  commands)  | Triage Stage:
 Severity:  Normal   |  Unreviewed
 Keywords:  dumpdata management  |  Needs documentation:  0
  commands subapp|  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by Fabio Caritas Barrionuevo da Luz ):

 Thank's.
 I'm not speaking english language, use google translator for almost
 everything (I'm still learning). So it was not very clear to me.
 It is possible to include an explicit note about it in the documentation
 and/or help of the dumpdata command?

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

Re: [Django] #22580: dumpdata don't work with sub app

[Django]

#22580: dumpdata don't work with sub app
-+-
 Reporter:  Fabio Caritas|Owner:  nobody
  Barrionuevo da Luz   |   Status:  closed
 Type:  Uncategorized|  Version:  1.6
Component:  Core (Management |   Resolution:  invalid
  commands)  | Triage Stage:
 Severity:  Normal   |  Unreviewed
 Keywords:  dumpdata management  |  Needs documentation:  0
  commands subapp|  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by carljm):

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


Comment:

 The app-label for a "subapp" (for any app, really) is just the leaf
 package name, not the full dotted import path. So you should be running
 `python manage.py dumpdata normalapp subapp anothersubapp`.

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

[Django] #22580: dumpdata don't work with sub app

[Django]

#22580: dumpdata don't work with sub app
-+-
 Reporter:  Fabio Caritas|  Owner:  nobody
  Barrionuevo da Luz   | Status:  new
 Type:  Uncategorized|Version:  1.6
Component:  Core (Management |   Keywords:  dumpdata management
  commands)  |  commands subapp
 Severity:  Normal   |  Has patch:  0
 Triage Stage:  Unreviewed   |  UI/UX:  0
Easy pickings:  0|
-+-
 I use django-allauth. The django-allauth has a structure of sub apps.
 I need to export data from some of the sub apps, although Django support
 the sub apps, dumpdata command does not have support to this feature

 I have the following structure of directories:

 django_project:
 manage.py
 test_dumpdata_subapp:
   __init__.py
   settings.py
   ...
 normalapp:
   __init__.py
   models.py
   ...
   subapp:
__init__.py
models.py
...
submodule:
 __init__.py
 anothersubapp:
 __init__.py
 models.py
 ...



 On settings.py file:

 INSTALLED_APPS = (
 ...
 'normalapp',
 'normalapp.subapp',
 'normalapp.subapp.submodule.anothersubapp',
 )


 syncdb works perfectly, but try:

 python manage.py dumpdata normalapp normalapp.subapp
 normalapp.subapp.submodule.anothersubapp

 results in this:
 CommandError: Unknown model: normalapp.subapp


 My test project is attached or can be viewed on github:
 https://github.com/luzfcb/test_dumpdata_subapp

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

[django/django] 2dd52d: [1.7.x] Reordered tutorial 1 so that the database ...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 2dd52d043344c9e9acf65149d8c72b32b40f4643
  
https://github.com/django/django/commit/2dd52d043344c9e9acf65149d8c72b32b40f4643
  Author: Tom 
  Date:   2014-05-05 (Mon, 05 May 2014)

  Changed paths:
M docs/intro/tutorial01.txt

  Log Message:
  ---
  [1.7.x] Reordered tutorial 1 so that the database is configured first.

This change is required after the introduction of
SessionAuthenticationMiddleware to the default middleware

Backport of 6923fdbbf1 from master


-- 
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/5367cd92baf80_2212bedd40544e4%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 6923fd: Reordered tutorial 1 so that the database is confi...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 6923fdbbf1824d6e28cc1d283b48146c7f58c6ea
  
https://github.com/django/django/commit/6923fdbbf1824d6e28cc1d283b48146c7f58c6ea
  Author: Tom 
  Date:   2014-05-05 (Mon, 05 May 2014)

  Changed paths:
M docs/intro/tutorial01.txt

  Log Message:
  ---
  Reordered tutorial 1 so that the database is configured first.

This change is required after the introduction of
SessionAuthenticationMiddleware to the default middleware


-- 
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/5367cd7e48118_b678e7d4412349%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[Django] #22579: validate_email accepts trailing dash

[Django]

#22579: validate_email accepts trailing dash
--+
 Reporter:  jason@…   |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Core (Other)  |Version:  1.6
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 In django 1.6 an EmailField (validate_email) will accept an address with a
 trailing dash at the end. Example: 'f...@bar.com-'
 In django 1.4 it would trigger a ValidationError, so I believe this is a
 regression.

 Tested like so:

 {{{
 >>> from django.core.validators import validate_email
 >>> validate_email('f...@bar.com-')
 }}}


 expected: throws ValidationError
 actual: no error thrown

 This may be related to #12027, about the same behavior, but with a
 trailing dot. As with that bug, a trailing dash causes sendmail to throw
 an 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/064.7d5b314e56b8d6d5134391a5557648ce%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22424: Default value for TextField

[Django]

#22424: Default value for TextField
-+--
 Reporter:  Nevsky   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-beta-1
 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
-+--

Old description:

> Hi! I start testing Django 1.7beta1. I use MySQL database.
> I add new TextField into my model like that:
>
> {{{
> class Article(models.Model):
> title = models.CharField(max_length=200)
> pub_date = models.DateField()
> text = models.TextField()
> text2 = models.TextField() #new TextField
> }}}
>
> When I type "python manage.py migrate" I am asked to enter default value.
> But BLOB/TEXT columns can't have a default value and if i will type
> something like 'blabla' then after command "python manage.py
> makemigrations" i will see error. I think it is bug :)

New description:

 Hi! I start testing Django 1.7beta1. I use MySQL database.
 I add new TextField into my model like that:

 {{{
 class Article(models.Model):
 title = models.CharField(max_length=200)
 pub_date = models.DateField()
 text = models.TextField()
 text2 = models.TextField() #new TextField
 }}}

 When I type "python manage.py makemigrations" I am asked to enter default
 value.
 But BLOB/TEXT columns can't have a default value and if i will type
 something like 'blabla' then after command "python manage.py migrate" i
 will see error. I think it is bug :)

--

Comment (by loic84):

 Fixed the name of the commands in the ticket description.

 I originally assumed this was an issue before the migrate step, but it's
 indeed an SQL issue due to one-off defaults, Django uses db defaults for
 these.

 The fix for MySQL is to not provide a default for BLOB/TEXT in the
 SchemaEditor. Although we'll now need to propagate the default value
 manually.

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

Re: [Django] #21780: Search highlighting on docs.djangoproject.com produces weird results when words overlap

[Django]

#21780: Search highlighting on docs.djangoproject.com produces weird results 
when
words overlap
-+
 Reporter:  bmispelon|Owner:
 Type:  Bug  |   Status:  new
Component:  *.djangoproject.com  |  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 maxocub):

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


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

Re: [Django] #22564: Migrations generated by Python 2 do not work in Python 3 due to b'' prefix on strings

[Django]

#22564: Migrations generated by Python 2 do not work in Python 3 due to b'' 
prefix
on strings
-+--
 Reporter:  timo |Owner:  claudep
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7-beta-2
 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 claudep):

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

[Django] #22578: Comments for translators do not appear if the translatable string is after an indentation

[Django]

#22578: Comments for translators do not appear if the translatable string is 
after
an indentation
---+
 Reporter:  ygbo   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Hi,

 I noticed this issue where the comment for translators does not appear in
 po files, it might also be a documentation clarification need to be added
 in:
 https://docs.djangoproject.com/en/dev/topics/i18n/translation/#comments-
 for-translators

 A small example is shorter than a long explanation:

 {{{
 # Translators: This doesn't work
 ungettext_lazy(
 "singular example 1",
 "plural example 1",
 count
 )
 # Translators: This works
 ungettext_lazy("singular example 2", "plural example 2", count)
 # Translators: This works too
 ungettext_lazy("singular example 3",
"plural example 3",
count)
 }}}

 in my po file I see this:
 {{{
 #: tables/actions.py:652
 msgid "singular example 1"
 msgid_plural "plural example 1"
 msgstr[0] ""
 msgstr[1] ""

 #. Translators: This works
 #: tables/actions.py:657
 msgid "singular example 2"
 msgid_plural "plural example 2"
 msgstr[0] ""
 msgstr[1] ""

 #. Translators: This works too
 #: tables/actions.py:659
 msgid "singular example 3"
 msgid_plural "plural example 3"
 msgstr[0] ""
 msgstr[1] ""
 }}}

 The issue is the same with all *gettext(_lazy) functions.

 As you can see the "#. Translators: This doesn't works" comment doesn't
 appear in the po file after running django_admin makemessages.

 I know that in the doc it says that the comment needs to be preceding the
 string.
 But it also needs to be preceding the *gettext(_lazy) function call with
 the string on the same line too.

 When you really need indentation (for pep8 and/or flake8 reasons) comments
 can't be used inside the function.
 In the example bellow the comment doesn't appear in the po file either,
 while it is well preceding the string (but inside the call to the gettext
 function instead of preceding it too):
 {{{
 ungettext_lazy(
 # Translators: This doesn't work either
 "singular example 1",
 "plural example 1",
 count
 )
 }}}



 If it's a gettext issue, It could be worth mentioning it in the
 documentation.

 In fact the comment has to be preceding both the translation function and
 the string, and the string has to be on the same line as the function
 call, if we want the comment to appear in the po file.

 It isn't a big issue for pgettext because translators have the contextual
 marker to help them, but it is for the other methods.


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

Re: [Django] #22568: FK to proxy model breaks migrate

[Django]

#22568: FK to proxy model breaks migrate
+--
 Reporter:  leftmoose   |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.7-beta-2
 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 timo):

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

Re: [Django] #22577: The makemigrations management command has a problem with migrations dir

[Django]

#22577: The makemigrations management command has a problem with migrations dir
-+-
 Reporter:  japrogramer@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  makemigrations,  | Triage Stage:
  fail, init, file   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 I created an app with an empty migrations folder and ran `makemigrations`,
 but did not get an error.

 {{{
 $ mkdir polls/migrations
 $ python manage.py makemigrations polls
 Migrations for 'polls':
   0001_initial.py:
 - Create model Poll
 - Create model Choice
 }}}

 Could you clarify the steps to reproduce?

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

Re: [Django] #22576: makemigrations requires 'default' database configuration

[Django]

#22576: makemigrations requires 'default' database configuration
-+--
 Reporter:  anonymous|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-beta-2
 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 murfi):

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

Re: [Django] #22572: @override_settings(ROOT_URLCONF) doesn't clear urlresolvers._urlconfs.

[Django]

#22572: @override_settings(ROOT_URLCONF) doesn't clear urlresolvers._urlconfs.
-+-
 Reporter:  loic84   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Loic Bistuer ):

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


Comment:

 In [changeset:"942556df2ffd3276dc127edd3cbb9d177095d882"]:
 {{{
 #!CommitTicketReference repository=""
 revision="942556df2ffd3276dc127edd3cbb9d177095d882"
 Fixed #22572 -- override_settings(ROOT_URLCONF) didn't clear
 urlresolvers._urlconfs.

 Thanks Anubhav Joshi and Tim Graham for the reviews.
 }}}

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

[django/django] 942556: Fixed #22572 -- override_settings(ROOT_URLCONF) di...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 942556df2ffd3276dc127edd3cbb9d177095d882
  
https://github.com/django/django/commit/942556df2ffd3276dc127edd3cbb9d177095d882
  Author: Loic Bistuer 
  Date:   2014-05-05 (Mon, 05 May 2014)

  Changed paths:
M django/test/signals.py
M tests/test_utils/tests.py
M tests/test_utils/views.py

  Log Message:
  ---
  Fixed #22572 -- override_settings(ROOT_URLCONF) didn't clear 
urlresolvers._urlconfs.

Thanks Anubhav Joshi and Tim Graham for the reviews.


-- 
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/536789211f5ad_dc31175d446457e%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #7599: add get_user_permissions method to ModelBackend

[Django]

#7599: add get_user_permissions method to ModelBackend
--+--
 Reporter:  gwilson   |Owner:  jorgecarleitao
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by jorgecarleitao):

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


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

Re: [Django] #22576: makemigrations requires 'default' database configuration

[Django]

#22576: makemigrations requires 'default' database configuration
-+--
 Reporter:  anonymous|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-beta-2
 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 timo):

 * stage:  Unreviewed => Accepted


Comment:

 From `django.core.management.commands.makemigrations`:

 {{{
 # Load the current graph state. Takes a connection, but it's not used
 # (makemigrations doesn't look at the database state).
 # Also make sure the graph is built without unmigrated apps shoehorned in.
 loader = MigrationLoader(connections[DEFAULT_DB_ALIAS])
 }}}

 The comment doesn't seem accurate given the traceback.

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

Re: [Django] #22466: 'ManyToOneRel' object has no attribute 'rel'

[Django]

#22466: 'ManyToOneRel' object has no attribute 'rel'
-+-
 Reporter:  takis|Owner:  akaariai
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |  1.7-beta-2
 Severity:  Release blocker  |   Resolution:  fixed
 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 Anssi Kääriäinen ):

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


Comment:

 In [changeset:"76979a257d289b8c463023308c888662d874"]:
 {{{
 #!CommitTicketReference repository=""
 revision="76979a257d289b8c463023308c888662d874"
 [1.7.x] Fixed #22466 -- ordering by reverse foreign key

 Ordering by reverse foreign key was broken by custom lookups patch
 (commit 20bab2cf9d02a5c6477d8aac066a635986e0d3f3).

 Thanks to everybody who helped solving this issue. Special thanks to
 Trac alias takis for reporting this.

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

[django/django] 76979a: [1.7.x] Fixed #22466 -- ordering by reverse foreig...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 76979a257d289b8c463023308c888662d874
  
https://github.com/django/django/commit/76979a257d289b8c463023308c888662d874
  Author: Anssi Kääriäinen 
  Date:   2014-05-05 (Mon, 05 May 2014)

  Changed paths:
M django/db/models/sql/query.py
M tests/queries/tests.py

  Log Message:
  ---
  [1.7.x] Fixed #22466 -- ordering by reverse foreign key

Ordering by reverse foreign key was broken by custom lookups patch
(commit 20bab2cf9d02a5c6477d8aac066a635986e0d3f3).

Thanks to everybody who helped solving this issue. Special thanks to
Trac alias takis for reporting this.

Backport of 3b7c66a3ac from master


-- 
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/5367830d4a747_f394c3d449038c%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 3b7c66: Fixed #22466 -- ordering by reverse foreign key

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 3b7c66a3ac0fcaa5dd02f87888c787d2c735c1a7
  
https://github.com/django/django/commit/3b7c66a3ac0fcaa5dd02f87888c787d2c735c1a7
  Author: Anssi Kääriäinen 
  Date:   2014-05-05 (Mon, 05 May 2014)

  Changed paths:
M django/db/models/sql/query.py
M tests/queries/tests.py

  Log Message:
  ---
  Fixed #22466 -- ordering by reverse foreign key

Ordering by reverse foreign key was broken by custom lookups patch
(commit 20bab2cf9d02a5c6477d8aac066a635986e0d3f3).

Thanks to everybody who helped solving this issue. Special thanks to
Trac alias takis for reporting this.


-- 
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/536782cd10e48_172c12ddd44323b5%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22569: lookup_allowed fails to consider dynamic list_filter

[Django]

#22569: lookup_allowed fails to consider dynamic list_filter
-+-
 Reporter:  Keryn Knight |Owner:  nobody
   |   Status:  new
 Type:  Bug  |  Version:  master
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * needs_docs:   => 0
 * needs_better_patch:   => 0
 * type:  Uncategorized => Bug
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #22570: Form.__getitem__ KeyError should be more descriptive

[Django]

#22570: Form.__getitem__ KeyError should be more descriptive
--+
 Reporter:  bendavis78|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Forms |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timo):

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


Comment:

 Test needs updating to pass on Python 3.

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

Re: [Django] #14030: Use F() objects in aggregates(), annotates() and values()

[Django]

#14030: Use F() objects in aggregates(), annotates() and values()
-+-
 Reporter:  delfick  |Owner:  smeatonj
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  aggregate, annotate  |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by akaariai):

 I am finally having some extra time, so expect review soon.

 I'm wondering if I should write a DEP about this change. I am not sure how
 well DEPs work for this kind of change. I guess I have to try writing one
 to find that out.

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

Re: [Django] #1349: MEDIA_URL and MEDIA_ROOT do not serve the files

[Django]

#1349: MEDIA_URL and MEDIA_ROOT do not serve the files
--+
 Reporter:  lzap@…|Owner:  timo
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:
 Severity:  Normal|   Resolution:  fixed
 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 Tim Graham ):

 In [changeset:"5783088eecddd935be3c641437748040669f91c0"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5783088eecddd935be3c641437748040669f91c0"
 [1.6.x] Fixed #1349 -- Clarified docs on serving files from
 STATIC/MEDIA_URL.

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

Re: [Django] #1349: MEDIA_URL and MEDIA_ROOT do not serve the files

[Django]

#1349: MEDIA_URL and MEDIA_ROOT do not serve the files
--+
 Reporter:  lzap@…|Owner:  timo
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:
 Severity:  Normal|   Resolution:  fixed
 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 Tim Graham ):

 In [changeset:"2a2d7db01f0032c9dbf446757c121fa2a5904a45"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2a2d7db01f0032c9dbf446757c121fa2a5904a45"
 [1.7.x] Fixed #1349 -- Clarified docs on serving files from
 STATIC/MEDIA_URL.

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

[django/django] 578308: [1.6.x] Fixed #1349 -- Clarified docs on serving f...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 5783088eecddd935be3c641437748040669f91c0
  
https://github.com/django/django/commit/5783088eecddd935be3c641437748040669f91c0
  Author: Tim Graham 
  Date:   2014-05-05 (Mon, 05 May 2014)

  Changed paths:
M docs/howto/static-files/index.txt
M docs/ref/settings.txt

  Log Message:
  ---
  [1.6.x] Fixed #1349 -- Clarified docs on serving files from STATIC/MEDIA_URL.

Backport of fb7c347f7b from master


-- 
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/53677862bea0b_9d2e73d4495313%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #1349: MEDIA_URL and MEDIA_ROOT do not serve the files

[Django]

#1349: MEDIA_URL and MEDIA_ROOT do not serve the files
--+
 Reporter:  lzap@…|Owner:  timo
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:
 Severity:  Normal|   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"fb7c347f7bd360b567c0b30697a6a200be2d6778"]:
 {{{
 #!CommitTicketReference repository=""
 revision="fb7c347f7bd360b567c0b30697a6a200be2d6778"
 Fixed #1349 -- Clarified docs on serving files from STATIC/MEDIA_URL.
 }}}

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

[django/django] 2a2d7d: [1.7.x] Fixed #1349 -- Clarified docs on serving f...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 2a2d7db01f0032c9dbf446757c121fa2a5904a45
  
https://github.com/django/django/commit/2a2d7db01f0032c9dbf446757c121fa2a5904a45
  Author: Tim Graham 
  Date:   2014-05-05 (Mon, 05 May 2014)

  Changed paths:
M docs/howto/static-files/index.txt
M docs/ref/settings.txt

  Log Message:
  ---
  [1.7.x] Fixed #1349 -- Clarified docs on serving files from STATIC/MEDIA_URL.

Backport of fb7c347f7b from master


-- 
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/53677864a602c_1b44fe5d4415290%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #1349: MEDIA_URL and MEDIA_ROOT do not serve the files

[Django]

#1349: MEDIA_URL and MEDIA_ROOT do not serve the files
--+
 Reporter:  lzap@…|Owner:  timo
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:
 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 timo):

 * status:  new => assigned
 * severity:  major => Normal
 * component:  Core (Other) => Documentation
 * owner:  adrian => timo
 * type:  defect => Cleanup/optimization
 * 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.de954ff7822361a5f2db1f6e8531a124%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] fb7c34: Fixed #1349 -- Clarified docs on serving files fro...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: fb7c347f7bd360b567c0b30697a6a200be2d6778
  
https://github.com/django/django/commit/fb7c347f7bd360b567c0b30697a6a200be2d6778
  Author: Tim Graham 
  Date:   2014-05-05 (Mon, 05 May 2014)

  Changed paths:
M docs/howto/static-files/index.txt
M docs/ref/settings.txt

  Log Message:
  ---
  Fixed #1349 -- Clarified docs on serving files from STATIC/MEDIA_URL.


-- 
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/5367784a8c029_13fadb9d40101350%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22489: Missing as_sql() implementation for __search lookup

[Django]

#22489: Missing as_sql() implementation for __search lookup
-+-
 Reporter:  jakub|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  mysql, search,   |  Needs documentation:  0
  full-text, __search, lookup|  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  0|
-+-

Comment (by Anssi Kääriäinen ):

 In [changeset:"4b6ba2c1d1dcf6d7d587ee19b3565879ab8ee219"]:
 {{{
 #!CommitTicketReference repository=""
 revision="4b6ba2c1d1dcf6d7d587ee19b3565879ab8ee219"
 [1.7.x] Fixed #22489 -- missing implemenation for search lookup

 When custom lookups were added, converting the search lookup to use
 the new Lookup infrastructure wasn't done.

 Some changes were needed to the added test, main change done by
 committer was ensuring the test works on MySQL versions prior to 5.6.

 Backport of 7131e14d00 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/063.7cbcc7a5729cef7471569a90204f237b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 4b6ba2: [1.7.x] Fixed #22489 -- missing implemenation for ...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 4b6ba2c1d1dcf6d7d587ee19b3565879ab8ee219
  
https://github.com/django/django/commit/4b6ba2c1d1dcf6d7d587ee19b3565879ab8ee219
  Author: Jakub Roztocil 
  Date:   2014-05-05 (Mon, 05 May 2014)

  Changed paths:
M django/db/models/lookups.py
M tests/lookup/models.py
M tests/lookup/tests.py

  Log Message:
  ---
  [1.7.x] Fixed #22489 -- missing implemenation for search lookup

When custom lookups were added, converting the search lookup to use
the new Lookup infrastructure wasn't done.

Some changes were needed to the added test, main change done by
committer was ensuring the test works on MySQL versions prior to 5.6.

Backport of 7131e14d00 from master


-- 
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/53677780ee542_1a3ea03d4022040%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22489: Missing as_sql() implementation for __search lookup

[Django]

#22489: Missing as_sql() implementation for __search lookup
-+-
 Reporter:  jakub|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  mysql, search,   |  Needs documentation:  0
  full-text, __search, lookup|  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  0|
-+-
Changes (by Anssi Kääriäinen ):

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


Comment:

 In [changeset:"7131e14d00b9b293cec4608925f2be6f94474350"]:
 {{{
 #!CommitTicketReference repository=""
 revision="7131e14d00b9b293cec4608925f2be6f94474350"
 Fixed #22489 -- missing implemenation for search lookup

 When custom lookups were added, converting the search lookup to use
 the new Lookup infrastructure wasn't done.

 Some changes were needed to the added test, main change done by
 committer was ensuring the test works on MySQL versions prior to 5.6.
 }}}

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

[django/django] 7131e1: Fixed #22489 -- missing implemenation for search l...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 7131e14d00b9b293cec4608925f2be6f94474350
  
https://github.com/django/django/commit/7131e14d00b9b293cec4608925f2be6f94474350
  Author: Jakub Roztocil 
  Date:   2014-05-05 (Mon, 05 May 2014)

  Changed paths:
M django/db/models/lookups.py
M tests/lookup/models.py
M tests/lookup/tests.py

  Log Message:
  ---
  Fixed #22489 -- missing implemenation for search lookup

When custom lookups were added, converting the search lookup to use
the new Lookup infrastructure wasn't done.

Some changes were needed to the added test, main change done by
committer was ensuring the test works on MySQL versions prior to 5.6.


-- 
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/53677741959f1_121313b5d345946b%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22577: The makemigrations management command has a problem with migrations dir

[Django]

#22577: The makemigrations management command has a problem with migrations dir
-+-
 Reporter:  japrogramer@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  makemigrations,  | Triage Stage:
  fail, init, file   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by timo:

Old description:

> When the migration folder does not have an init
> http://codepad.com/U2nGptor
> {{{
>
> File "/home/archie/git/django/django/db/migrations/writer.py", line 150,
> in path basedir = os.path.dirname(migrations_module.__file__)
> AttributeError: 'module' object has no attribute '__file__'
>
> }}}
>
> the problem lies with makemigrations.py line 134-36 they are checking to
> see if an init file exists in the migrations dir but it checks using  a
> line that depends on the existence of __init__.py. line 130 ,
> writer.path, following to see where this code comees from led me to
> line149 and 150 which need there to be an init file for __file__ to be an
> attribute there ..
> tl;dr
> makemigrations checks for an init file using os.path.isdir but with a
> call that depends on an __init__.py for it treats it as a module before
> it knows if it is a module

New description:

 When the migration folder does not have an init
 http://codepad.org/U2nGptor
 {{{

 File "/home/archie/git/django/django/db/migrations/writer.py", line 150,
 in path basedir = os.path.dirname(migrations_module.__file__)
 AttributeError: 'module' object has no attribute '__file__'

 }}}

 the problem lies with `makemigrations.py` line 134-36 they are checking to
 see if an init file exists in the migrations dir but it checks using  a
 line that depends on the existence of `__init__.py`. line 130 ,
 `writer.path`, following to see where this code comes from led me to line
 149 and 150 which need there to be an init file for `__file__` to be an
 attribute there ..
 tl;dr
 `makemigrations` checks for an init file using `os.path.isdir` but with a
 call that depends on an `__init__.py` for it treats it as a module before
 it knows if it is a module

--

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

Re: [Django] #22577: The makemigrations management command has a problem with migrations dir

[Django]

#22577: The makemigrations management command has a problem with migrations dir
-+-
 Reporter:  japrogramer@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  makemigrations,  | Triage Stage:
  fail, init, file   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by anonymous):

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


Comment:

 It is  dot org not dot com

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

Re: [Django] #22571: Document implications of using auto_now_add=True and get_or_create (was: DateTimeField(auto_now_add=True) Breaks)

[Django]

#22571: Document implications of using auto_now_add=True and get_or_create
-+-
 Reporter:  nu.everest@… |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.4
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  integrityerror   |  Needs documentation:  0
  auto_now_add get_or_create |  Patch needs improvement:  0
  duplicatekey   |UI/UX:  0
Has patch:  0|
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timo):

 * needs_better_patch:   => 0
 * component:  Uncategorized => Documentation
 * needs_tests:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 I suppose the documentation could have a note about 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/078.de4a9fd22dc897633cd07aaf6adef222%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #22577: The makemigrations management command has a problem with migrations dir

[Django]

#22577: The makemigrations management command has a problem with migrations dir
+--
 Reporter:  |  Owner:  nobody
  japrogramer@… | Status:  new
 Type:  Bug |Version:  master
Component:  Migrations  |   Keywords:  makemigrations, fail, init, file
 Severity:  Normal  |  Has patch:  0
 Triage Stage:  Unreviewed  |  UI/UX:  0
Easy pickings:  0   |
+--
 When the migration folder does not have an init
 http://codepad.com/U2nGptor
 {{{

 File "/home/archie/git/django/django/db/migrations/writer.py", line 150,
 in path basedir = os.path.dirname(migrations_module.__file__)
 AttributeError: 'module' object has no attribute '__file__'

 }}}

 the problem lies with makemigrations.py line 134-36 they are checking to
 see if an init file exists in the migrations dir but it checks using  a
 line that depends on the existence of __init__.py. line 130 , writer.path,
 following to see where this code comees from led me to line149 and 150
 which need there to be an init file for __file__ to be an attribute there
 ..
 tl;dr
 makemigrations checks for an init file using os.path.isdir but with a call
 that depends on an __init__.py for it treats it as a module before it
 knows if it is a module

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

Re: [Django] #22572: @override_settings(ROOT_URLCONF) doesn't clear urlresolvers._urlconfs.

[Django]

#22572: @override_settings(ROOT_URLCONF) doesn't clear urlresolvers._urlconfs.
-+-
 Reporter:  loic84   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by timo):

 * stage:  Unreviewed => 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/064.ec04994e0c4be591a9c256fd0331e16b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22480: "django-admin.py dumpdata" - unable to serialize

[Django]

#22480: "django-admin.py dumpdata" - unable to serialize
-+-
 Reporter:  yn   |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Core |  Version:  1.6
  (Serialization)|   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

 * status:  new => closed
 * component:  Uncategorized => Core (Serialization)
 * resolution:   => invalid


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

[django/django] 6a6f29: [1.7.x] Fixed #22575 -- Fixed typo in docs/topics/...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 6a6f294f518a96334c73b2e5f934cdd2f0feda7e
  
https://github.com/django/django/commit/6a6f294f518a96334c73b2e5f934cdd2f0feda7e
  Author: Tim Graham 
  Date:   2014-05-05 (Mon, 05 May 2014)

  Changed paths:
M docs/topics/class-based-views/generic-editing.txt

  Log Message:
  ---
  [1.7.x] Fixed #22575 -- Fixed typo in 
docs/topics/class-based-views/generic-editing.txt.

Thanks adminq80 at gmail.com.

Backport of 87776859af from master


-- 
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/53676b2d40131_11e28d9d34437ef%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22575: auth.User model doesn't exist

[Django]

#22575: auth.User model doesn't exist
---+
 Reporter:  adminq80@… |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.6
 Severity:  Normal |   Resolution:  fixed
 Keywords:  auth.User  | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+

Comment (by Tim Graham ):

 In [changeset:"6a6f294f518a96334c73b2e5f934cdd2f0feda7e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="6a6f294f518a96334c73b2e5f934cdd2f0feda7e"
 [1.7.x] Fixed #22575 -- Fixed typo in docs/topics/class-based-views
 /generic-editing.txt.

 Thanks adminq80 at gmail.com.

 Backport of 87776859af 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/076.e141f892a22622d9d67fce6971214440%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 41ab97: [1.5.x] Fixed #22575 -- Fixed typo in docs/topics/...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 41ab97b6a4e785a35b6199134aad39091b6b1aab
  
https://github.com/django/django/commit/41ab97b6a4e785a35b6199134aad39091b6b1aab
  Author: Tim Graham 
  Date:   2014-05-05 (Mon, 05 May 2014)

  Changed paths:
M docs/topics/class-based-views/generic-editing.txt

  Log Message:
  ---
  [1.5.x] Fixed #22575 -- Fixed typo in 
docs/topics/class-based-views/generic-editing.txt.

Thanks adminq80 at gmail.com.

Backport of 87776859af from master


-- 
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/53676b2e33ff7_1a1c1113d38100624%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22575: auth.User model doesn't exist

[Django]

#22575: auth.User model doesn't exist
---+
 Reporter:  adminq80@… |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.6
 Severity:  Normal |   Resolution:  fixed
 Keywords:  auth.User  | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+

Comment (by Tim Graham ):

 In [changeset:"cddbaca6976a1e6faba8e846b87e27b35e268198"]:
 {{{
 #!CommitTicketReference repository=""
 revision="cddbaca6976a1e6faba8e846b87e27b35e268198"
 [1.6.x] Fixed #22575 -- Fixed typo in docs/topics/class-based-views
 /generic-editing.txt.

 Thanks adminq80 at gmail.com.

 Backport of 87776859af 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/076.292bbed2d4295b9747d6ee8414f9b5b7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] cddbac: [1.6.x] Fixed #22575 -- Fixed typo in docs/topics/...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: cddbaca6976a1e6faba8e846b87e27b35e268198
  
https://github.com/django/django/commit/cddbaca6976a1e6faba8e846b87e27b35e268198
  Author: Tim Graham 
  Date:   2014-05-05 (Mon, 05 May 2014)

  Changed paths:
M docs/topics/class-based-views/generic-editing.txt

  Log Message:
  ---
  [1.6.x] Fixed #22575 -- Fixed typo in 
docs/topics/class-based-views/generic-editing.txt.

Thanks adminq80 at gmail.com.

Backport of 87776859af from master


-- 
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/53676b2c3406d_154313ddd34999b6%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22575: auth.User model doesn't exist

[Django]

#22575: auth.User model doesn't exist
---+
 Reporter:  adminq80@… |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.6
 Severity:  Normal |   Resolution:  fixed
 Keywords:  auth.User  | 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:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"87776859affc45b9b485d8377c046dd464aaeef4"]:
 {{{
 #!CommitTicketReference repository=""
 revision="87776859affc45b9b485d8377c046dd464aaeef4"
 Fixed #22575 -- Fixed typo in docs/topics/class-based-views/generic-
 editing.txt.

 Thanks adminq80 at gmail.com.
 }}}

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

Re: [Django] #22575: auth.User model doesn't exist

[Django]

#22575: auth.User model doesn't exist
---+
 Reporter:  adminq80@… |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.6
 Severity:  Normal |   Resolution:  fixed
 Keywords:  auth.User  | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+

Comment (by Tim Graham ):

 In [changeset:"41ab97b6a4e785a35b6199134aad39091b6b1aab"]:
 {{{
 #!CommitTicketReference repository=""
 revision="41ab97b6a4e785a35b6199134aad39091b6b1aab"
 [1.5.x] Fixed #22575 -- Fixed typo in docs/topics/class-based-views
 /generic-editing.txt.

 Thanks adminq80 at gmail.com.

 Backport of 87776859af 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/076.3021fc8e778f9de968e28248f67e701a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 877768: Fixed #22575 -- Fixed typo in docs/topics/class-ba...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 87776859affc45b9b485d8377c046dd464aaeef4
  
https://github.com/django/django/commit/87776859affc45b9b485d8377c046dd464aaeef4
  Author: Tim Graham 
  Date:   2014-05-05 (Mon, 05 May 2014)

  Changed paths:
M docs/topics/class-based-views/generic-editing.txt

  Log Message:
  ---
  Fixed #22575 -- Fixed typo in 
docs/topics/class-based-views/generic-editing.txt.

Thanks adminq80 at gmail.com.


-- 
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/53676b092d03_1e20e3bd40463a7%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 0e3704: [1.6.x] Fixed #22429 -- Incorrect SQL when using ~...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 0e3704963693ddfaaa525054c42333f6ffdb4b47
  
https://github.com/django/django/commit/0e3704963693ddfaaa525054c42333f6ffdb4b47
  Author: Anssi Kääriäinen 
  Date:   2014-05-05 (Mon, 05 May 2014)

  Changed paths:
M django/db/models/sql/query.py
M docs/releases/1.6.5.txt
M tests/queries/models.py
M tests/queries/tests.py

  Log Message:
  ---
  [1.6.x] Fixed #22429 -- Incorrect SQL when using ~Q and F

Backpatch of 5e1f4656b98816c96a1cc051224c1b699db480e0 from master.

Conflicts:
django/db/models/sql/query.py
tests/queries/models.py
tests/queries/tests.py


-- 
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/536766d6d5262_115e543d3c12174%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22429: Wrong SQL generated when using ~Q and F

[Django]

#22429: Wrong SQL generated when using ~Q and F
-+-
 Reporter:  sipp11   |Owner:
 Type:  Bug  |  superemily
Component:  Database layer   |   Status:  closed
  (models, ORM)  |  Version:  master
 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 Anssi Kääriäinen ):

 In [changeset:"0e3704963693ddfaaa525054c42333f6ffdb4b47"]:
 {{{
 #!CommitTicketReference repository=""
 revision="0e3704963693ddfaaa525054c42333f6ffdb4b47"
 [1.6.x] Fixed #22429 -- Incorrect SQL when using ~Q and F

 Backpatch of 5e1f4656b98816c96a1cc051224c1b699db480e0 from master.

 Conflicts:
 django/db/models/sql/query.py
 tests/queries/models.py
 tests/queries/tests.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/064.524c763b78b7c0ba07762669b8677bd7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22575: auth.User model doesn't exist

[Django]

#22575: auth.User model doesn't exist
---+
 Reporter:  adminq80@… |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords:  auth.User  | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by aaugustin):

 * status:  closed => new
 * resolution:  invalid =>
 * stage:  Unreviewed => Accepted


Comment:

 Oh, yeah, there's a typo in the import line. I was misled by the
 suggestion to switch to `get_user_model()`.

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

[django/django] 402fc4: [1.7.x] Fixed #22429 -- Incorrect SQL when using ~...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 402fc4f6c9921f56eecbb6e3fc69154270be6468
  
https://github.com/django/django/commit/402fc4f6c9921f56eecbb6e3fc69154270be6468
  Author: Anssi Kääriäinen 
  Date:   2014-05-05 (Mon, 05 May 2014)

  Changed paths:
M django/db/models/sql/query.py
M docs/releases/1.6.5.txt
M tests/queries/models.py
M tests/queries/tests.py

  Log Message:
  ---
  [1.7.x] Fixed #22429 -- Incorrect SQL when using ~Q and F

Backport of 5e1f4656b9 from master


-- 
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/53676376cf33b_dc31175d44581f6%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22429: Wrong SQL generated when using ~Q and F

[Django]

#22429: Wrong SQL generated when using ~Q and F
-+-
 Reporter:  sipp11   |Owner:
 Type:  Bug  |  superemily
Component:  Database layer   |   Status:  closed
  (models, ORM)  |  Version:  master
 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 Anssi Kääriäinen ):

 In [changeset:"402fc4f6c9921f56eecbb6e3fc69154270be6468"]:
 {{{
 #!CommitTicketReference repository=""
 revision="402fc4f6c9921f56eecbb6e3fc69154270be6468"
 [1.7.x] Fixed #22429 -- Incorrect SQL when using ~Q and F

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

Re: [Django] #22429: Wrong SQL generated when using ~Q and F

[Django]

#22429: Wrong SQL generated when using ~Q and F
-+-
 Reporter:  sipp11   |Owner:
 Type:  Bug  |  superemily
Component:  Database layer   |   Status:  closed
  (models, ORM)  |  Version:  master
 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 Anssi Kääriäinen ):

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


Comment:

 In [changeset:"5e1f4656b98816c96a1cc051224c1b699db480e0"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5e1f4656b98816c96a1cc051224c1b699db480e0"
 Fixed #22429 -- Incorrect SQL when using ~Q and F
 }}}

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

[django/django] 5e1f46: Fixed #22429 -- Incorrect SQL when using ~Q and F

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 5e1f4656b98816c96a1cc051224c1b699db480e0
  
https://github.com/django/django/commit/5e1f4656b98816c96a1cc051224c1b699db480e0
  Author: Anssi Kääriäinen 
  Date:   2014-05-05 (Mon, 05 May 2014)

  Changed paths:
M django/db/models/sql/query.py
M docs/releases/1.6.5.txt
M tests/queries/models.py
M tests/queries/tests.py

  Log Message:
  ---
  Fixed #22429 -- Incorrect SQL when using ~Q and F


-- 
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/536760ff8e6c8_2212bedd4031626%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22575: auth.User model doesn't exist

[Django]

#22575: auth.User model doesn't exist
---+--
 Reporter:  adminq80@… |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.6
 Severity:  Normal |   Resolution:  invalid
 Keywords:  auth.User  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--

Comment (by abdul):

 I am using Django 1.6.4 and I tried `from django.contrib.auth import User`
 and it didn't work for me. I propose to modify the importing path to look
 like `from django.contrib.auth.models import User`.

 Sincerely,
 Abdul

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

Re: [Django] #22576: makemigrations requires 'default' database configuration

[Django]

#22576: makemigrations requires 'default' database configuration
-+--
 Reporter:  anonymous|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-beta-2
 Severity:  Release blocker  |   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 anonymous):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * component:  Uncategorized => Migrations
 * needs_tests:   => 0
 * type:  Uncategorized => Bug


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

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

[Django] #22576: makemigrations requires 'default' database configuration

[Django]

#22576: makemigrations requires 'default' database configuration
-+
 Reporter:  anonymous|  Owner:  nobody
 Type:  Uncategorized| Status:  new
Component:  Uncategorized|Version:  1.7-beta-2
 Severity:  Release blocker  |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 According to https://docs.djangoproject.com/en/1.7/topics/db/multi-db/, it
 is OK use an empty dictionary as the 'default' entry in settins.DATABASES
 in a multi-database setup, but the makemigations management command
 insists on it being configured.

 To reproduce, do "django-admin startproject mmtest", and edit the
 settings.py:


 {{{
 class DbRouter(object):
def db_for_read(self, model, **hints):
 return 'nondefault';
db_for_write = db_for_read

 DATABASE_ROUTERS = ('mmtest.settings.DbRouter', )

 DATABASES = {
 'default': {},
 'nondefault': {
 'ENGINE': 'django.db.backends.sqlite3',
 'NAME': os.path.join(BASE_DIR, 'db.sqlite3'),
 }
 }
 }}}


 Stacktrace:

 {{{
 (mmtest)vagrant@localhost:~/mmtest$ ./manage.py makemigrations
 Traceback (most recent call last):
   File "./manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "/home/vagrant/.virtualenvs/mmtest/local/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 427, in
 execute_from_command_line
 utility.execute()
   File "/home/vagrant/.virtualenvs/mmtest/local/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 419, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/vagrant/.virtualenvs/mmtest/local/lib/python2.7/site-
 packages/django/core/management/base.py", line 288, in run_from_argv
 self.execute(*args, **options.__dict__)
   File "/home/vagrant/.virtualenvs/mmtest/local/lib/python2.7/site-
 packages/django/core/management/base.py", line 337, in execute
 output = self.handle(*args, **options)
   File "/home/vagrant/.virtualenvs/mmtest/local/lib/python2.7/site-
 packages/django/core/management/commands/makemigrations.py", line 56, in
 handle
 loader.build_graph(ignore_unmigrated=True)
   File "/home/vagrant/.virtualenvs/mmtest/local/lib/python2.7/site-
 packages/django/db/migrations/loader.py", line 148, in build_graph
 self.applied_migrations = recorder.applied_migrations()
   File "/home/vagrant/.virtualenvs/mmtest/local/lib/python2.7/site-
 packages/django/db/migrations/recorder.py", line 48, in applied_migrations
 self.ensure_schema()
   File "/home/vagrant/.virtualenvs/mmtest/local/lib/python2.7/site-
 packages/django/db/migrations/recorder.py", line 38, in ensure_schema
 if self.Migration._meta.db_table in
 self.connection.introspection.get_table_list(self.connection.cursor()):
   File "/home/vagrant/.virtualenvs/mmtest/local/lib/python2.7/site-
 packages/django/db/backends/__init__.py", line 162, in cursor
 cursor = self.make_debug_cursor(self._cursor())
   File "/home/vagrant/.virtualenvs/mmtest/local/lib/python2.7/site-
 packages/django/db/backends/dummy/base.py", line 18, in complain
 raise ImproperlyConfigured("settings.DATABASES is improperly
 configured. "
 django.core.exceptions.ImproperlyConfigured: settings.DATABASES is
 improperly configured. Please supply the ENGINE value. Check settings
 documentation for more details.
 }}}

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

Re: [Django] #22466: 'ManyToOneRel' object has no attribute 'rel'

[Django]

#22466: 'ManyToOneRel' object has no attribute 'rel'
-+-
 Reporter:  takis|Owner:  akaariai
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:
  (models, ORM)  |  1.7-beta-2
 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 akaariai):

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


Comment:

 Ordering by reverse FK is something that is possible even if it usually
 doesn't make any sense. The interpretation is that one gets duplicate
 results.

 I'll assign this to myself.

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

Re: [Django] #22575: auth.User model doesn't exist

[Django]

#22575: auth.User model doesn't exist
---+--
 Reporter:  adminq80@… |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.6
 Severity:  Normal |   Resolution:  invalid
 Keywords:  auth.User  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by aaugustin):

 * resolution:  fixed => invalid


Comment:

 - Importing the `User` model certainly works; if you run into trouble,
 please see TicketClosingReasons/UseSupportChannels for ways to get help.
 - Using `get_user_model()` in a `ForeignKey` declaration is wrong and will
 raise an exception in Django 1.7; if you want to support custom user
 models, the proper idiom is `ForeignKey(settings.AUTH_USER_MODEL)`
 - The change proposed above wasn't committed, so the ticket should have
 stayed open until someone had either committed the change or rejected the
 ticket — which I'm doing now.

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

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

Re: [Django] #22575: auth.User model doesn't exist

[Django]

#22575: auth.User model doesn't exist
---+--
 Reporter:  adminq80@… |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.6
 Severity:  Normal |   Resolution:  fixed
 Keywords:  auth.User  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by anonymous):

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


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

Re: [Django] #22575: auth.User model doesn't exist

[Django]

#22575: auth.User model doesn't exist
---+--
 Reporter:  adminq80@… |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords:  auth.User  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by abdul):

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


Comment:

 The documentation is now updated.

 Sincerely,
 Abdul

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

[Django] #22575: auth.User model doesn't exist

[Django]

#22575: auth.User model doesn't exist
---+---
 Reporter:  adminq80@… |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.6
 Severity:  Normal |   Keywords:  auth.User
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+---
 Hello all, I was trying to follow the documentation and importing User
 from auth module but it didn't work, so I used auth.get_user_model()
 instead. Would you update the documentation accordingly, please?

 The documentation link that has the error is
 https://docs.djangoproject.com/en/1.6/topics/class-based-views/generic-
 editing/

 I am using Django version 1.6.4 final

 Sincerely,
 Abdul

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

Re: [Django] #22563: Migration of admin.LogEntry.user fails.

[Django]

#22563: Migration of admin.LogEntry.user fails.
-+--
 Reporter:  efrinut@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-beta-2
 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 melinath):

 * cc: stephen.r.burrows@… (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/075.906960d3b3696a9d5a3085bde72ed47f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.