Re: [Django] #25617: Disallow usernames that differ only in case in UserCreationForm

[Django]

#25617: Disallow usernames that differ only in case in UserCreationForm
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by zachborboa):

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

Re: [Django] #21516: Update the import path for the FormSet classes and factories in documentation.

[Django]

#21516: Update the import path for the FormSet classes and factories in
documentation.
--+
 Reporter:  loic84|Owner:  bxm156
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by charettes):

 * has_patch:  0 => 1


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

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

Re: [Django] #21516: Update the import path for the FormSet classes and factories in documentation.

[Django]

#21516: Update the import path for the FormSet classes and factories in
documentation.
--+
 Reporter:  loic84|Owner:  bxm156
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by bxm156):

 This is my first ticket / contribution to the Django project.

 I have created a topic branch at:
 https://github.com/bxm156/django/tree/ticket_21516

 Commit:
 
https://github.com/bxm156/django/commit/9c117b9bd62ea090f1d8b4d7fb7345ebaaf9e836

 Ran make html in docs locally, the build succeeded.

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

[Django] #25620: URLValidator regex does not trigger on consecutive periods

[Django]

#25620: URLValidator regex does not trigger on consecutive periods
--+
 Reporter:  sully90h  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Core (Other)  |Version:  1.8
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 The regular expression for
 [https://docs.djangoproject.com/en/1.8/ref/validators/#urlvalidator
 URLValidator] accepts consecutive periods as valid. This bug was
 introduced in 1.8.3.


 == Steps to Reproduce ==
 {{{
 #!python
 >>> from django.core.validators import URLValidator
 >>> validate = URLValidator()
 >>> validate('http://example..com')
 >>> validate('http://example...com')
 }}}

 == Expected Result ==
 A [https://docs.djangoproject.com/en/1.8/ref/exceptions/#validationerror
 ValidationError] exception should be raised.


 == Current Result ==
 No exception is raised, and the URL is deemed valid.


 == Reference ==
 [https://tools.ietf.org/html/rfc2181#section-11 RFC 2181]:
The length of any one label is limited to between 1 and 63 octets.  A
 full domain name is limited to 255 octets (including the separators).  The
 zero   length full name is defined as representing the root of the DNS
 tree, and is typically written and displayed as ".".

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

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

Re: [Django] #21516: Update the import path for the FormSet classes and factories in documentation.

[Django]

#21516: Update the import path for the FormSet classes and factories in
documentation.
--+
 Reporter:  loic84|Owner:  bxm156
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by bxm156):

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


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

Re: [Django] #25606: Add support for "__" lookup in RelatedOnlyFieldListFilter

[Django]

#25606: Add support for "__" lookup in RelatedOnlyFieldListFilter
---+
 Reporter:  quarkness  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.8
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timgraham):

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


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

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

Re: [Django] #16734: Set script prefix in django.setup() to allow its usage outside of requests (was: urlresolvers doesn't get a script prefix from manage.py)

[Django]

#16734: Set script prefix in django.setup() to allow its usage outside of 
requests
-+-
 Reporter:  d00gs|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * type:  Bug => New feature
 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #12885: GenericRelation fails to join the related table from a inherited model

[Django]

#12885: GenericRelation fails to join the related table from a inherited model
-+-
 Reporter:  semenov  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  1.1
  contrib.contenttypes   |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #5763: Queryset doesn't have a "not equal" filter operator

[Django]

#5763: Queryset doesn't have a "not equal" filter operator
-+-
 Reporter:  jdetaeye |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  qs-rf| Triage Stage:  Design
 |  decision needed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by timgraham):

 Please first read through the ticket history as well as the mailing list
 threads linked from the the ticket. If you disagree with the conclusions
 that have been reached so far, you are welcome to argue your case on the
 DevelopersMailingList.

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

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

Re: [Django] #25619: Since Django ~1.6.4 the dev runserver uses http_version 1.0, before it was 1.1

[Django]

#25619: Since Django ~1.6.4 the dev runserver uses http_version 1.0, before it 
was
1.1
---+--
 Reporter:  gabn88 |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  HTTP handling  |  Version:  1.7
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by timgraham):

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


Comment:

 What methodology are you using to test? Can you bisect Django's commit
 history to determine where the behavior changed?

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

[Django] #25619: Since Django ~1.6.4 the dev runserver uses http_version 1.0, before it was 1.1

[Django]

#25619: Since Django ~1.6.4 the dev runserver uses http_version 1.0, before it 
was
1.1
---+
 Reporter:  gabn88 |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  HTTP handling  |Version:  1.7
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 And http_version 1.0 is not working with websockets.

 I don't know exactly why this is happening, but I don't think it is meant
 to be like this.

 I think HTTP/1.1 is fine to use for the development runserver.

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

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

Re: [Django] #16734: urlresolvers doesn't get a script prefix from manage.py

[Django]

#16734: urlresolvers doesn't get a script prefix from manage.py
-+-
 Reporter:  d00gs|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

 * needs_docs:  1 => 0


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

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

Re: [Django] #5763: Queryset doesn't have a "not equal" filter operator

[Django]

#5763: Queryset doesn't have a "not equal" filter operator
-+-
 Reporter:  jdetaeye |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  qs-rf| Triage Stage:  Design
 |  decision needed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by merutak):

 Since this is an issue that keeps coming up for me, and I'm seeing it in
 discussions on the web as well as on this ticket, and its usefulness has
 been demonstrated by asmoore82 (and I can give more examples) --

 is there an explanation why this shouldn't be implemented? Is there some
 consideration by which this ticket isn't a good idea?

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

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

Re: [Django] #25618: Django migration system breaks with unhelpful error message if south migrations accidentally retained

[Django]

#25618: Django migration system breaks with unhelpful error message if south
migrations accidentally retained
---+
 Reporter:  ryuusenshi |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Migrations |  Version:  1.7
 Severity:  Normal |   Resolution:
 Keywords:  migrations, south  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by timgraham):

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


Comment:

 It's a bit late to add this (in particular, 1.7 is end-of-life Dec. 1 and
 is only receiving security updates), but adding to 1.8/1.9 seems okay
 since you offered a patch, so I converted it to a
 [https://github.com/django/django/pull/5489 pull request]. For 1.10, I
 proposed to [https://github.com/django/django/pull/5488 remove detection
 of south migrations].

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

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

Re: [Django] #25609: Add a more useful error message for invalid nested lookup on a related field

[Django]

#25609: Add a more useful error message for invalid nested lookup on a related
field
-+-
 Reporter:  Ian-Foote|Owner:  Ian-Foote
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.9b1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"32e804cdb7e09c260fa1f224962831d2b672af85" 32e804cd]:
 {{{
 #!CommitTicketReference repository=""
 revision="32e804cdb7e09c260fa1f224962831d2b672af85"
 [1.9.x] Fixed #25609 -- Fixed regression in related field nested lookup
 error.

 Backport of 32ef48aa562e6aaee9983f5d0f1c60f02fd555fb 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/067.58b27cea5e3d429a89b8ef6141f279b1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25609: Add a more useful error message for invalid nested lookup on a related field

[Django]

#25609: Add a more useful error message for invalid nested lookup on a related
field
-+-
 Reporter:  Ian-Foote|Owner:  Ian-Foote
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.9b1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"32ef48aa562e6aaee9983f5d0f1c60f02fd555fb" 32ef48a]:
 {{{
 #!CommitTicketReference repository=""
 revision="32ef48aa562e6aaee9983f5d0f1c60f02fd555fb"
 Fixed #25609 -- Fixed regression in related field nested lookup 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/067.db3578873ed6814f714ca18a2ca3bc07%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25618: Django migration system breaks with unhelpful error message if south migrations accidentally retained

[Django]

#25618: Django migration system breaks with unhelpful error message if south
migrations accidentally retained
---+
 Reporter:  ryuusenshi |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Migrations |Version:  1.7
 Severity:  Normal | Resolution:
 Keywords:  migrations, south  |   Triage Stage:  Unreviewed
Has patch:  1  |  Easy pickings:  1
UI/UX:  0  |
---+
Changes (by ryuusenshi):

 * Attachment "django-south-bug-fix.diff" 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/068.c471a114b937120cfedd000ae92d11a5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25618: Django migration system breaks with unhelpful error message if south migrations accidentally retained

[Django]

#25618: Django migration system breaks with unhelpful error message if south
migrations accidentally retained
---+
 Reporter:  ryuusenshi |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Migrations |Version:  1.7
 Severity:  Normal | Resolution:
 Keywords:  migrations, south  |   Triage Stage:  Unreviewed
Has patch:  1  |  Easy pickings:  1
UI/UX:  0  |
---+
Changes (by ryuusenshi):

 * Attachment "django-south-bug-fix.diff" 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/068.91594aa2f63b2888cfe5ba7ca5d4f43a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #25618: Django migration system breaks with unhelpful error message if south migrations accidentally retained

[Django]

#25618: Django migration system breaks with unhelpful error message if south
migrations accidentally retained
+---
 Reporter:  ryuusenshi  |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  1.7
 Severity:  Normal  |   Keywords:  migrations, south
 Triage Stage:  Unreviewed  |  Has patch:  1
Easy pickings:  1   |  UI/UX:  0
+---
 For an app that contains both django and south type migrations, the
 migration system will become unable to perform any migration task for that
 app, and the error message will not be helpful at all (either "Application
 labels aren't unique, duplicates: x" - django 1.7, or "table x already
 exists" - django 1.8). This happens because the app is treated as both
 migrated and unmigrated at the same time.

 To reproduce this error, you can clone the repo:
 [https://github.com/ryuusenshi/django-south-migrate-bugfix django-south-
 bug]. This repo contains a migrations directory with 2 south type
 migration in it.

 Now run:
 {{{
 python manage.py makemigrations djsouth
 }}}

 followed by:
 {{{
 python manage.py migrate
 }}}

 What is of particular interest here is that the makemigrations command
 created the initial django migration without deleting the other numbered
 (south) migrations, thus putting the app into an erroneous state.

 Additionally, it is worth noting that in this workflow, step 3 from
 [https://docs.djangoproject.com/en/1.7/topics/migrations/#upgrading-from-
 south upgrading-from-south] was skipped, so essentially it is user error,
 however I believe that the error message should not be entirely unhelpful.

 The patch attached can be applied to both django 1.7 and 1.8, since they
 are both affected by this. The patch will break the execution of the
 migration system at the graph construction phase and report with a helpful
 error message.

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

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

Re: [Django] #25617: Disallow usernames that differ only in case in UserCreationForm

[Django]

#25617: Disallow usernames that differ only in case in UserCreationForm
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by claudep):

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

[Django] #25617: Disallow usernames that differ only in case in UserCreationForm

[Django]

#25617: Disallow usernames that differ only in case in UserCreationForm
+
   Reporter:  timgraham |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  contrib.auth  |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 Most applications don't treat user names as case sensitive. While we can't
 treat usernames as case-insensitive everywhere in Django due to backwards
 compatibility (#2273), by using `username__iexact` when checking for
 uniqueness of new usernames in `UserCreationForm`, we can at least prevent
 the creation of new usernames that differ only in case from an existing
 one. This protection won't cover creating a user in the shell or through
 the `createsuperuser` management command, but I don't think this is
 critical.

 This wouldn't affect any usernames that already exist, and users will
 still need to login with the same case that they register with.

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

Re: [Django] #25615: multidb Relation fields do not support nested lookups

[Django]

#25615: multidb Relation fields do not support nested lookups
-+-
 Reporter:  gerdkoetje   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 Let's keep this ticket closed until there is a conclusion on django-users
 that Django is at fault.

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

Re: [Django] #25615: multidb Relation fields do not support nested lookups

[Django]

#25615: multidb Relation fields do not support nested lookups
-+-
 Reporter:  gerdkoetje   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by gerdkoetje):

 you don't get my point.
 seconde is a remote database in my real project.
 and im not able to do reverse lookups on any other db then the default on.
 with did work fine in 1.6.1

 this is what i did try to prove with this project, only i can't add a
 remote database to it so i used a locale database for it.

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

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

Re: [Django] #25615: multidb Relation fields do not support nested lookups

[Django]

#25615: multidb Relation fields do not support nested lookups
-+-
 Reporter:  gerdkoetje   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by gerdkoetje):

 * status:  closed => new
 * 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/068.bcbf61d7e52cbc8dab3e1ff39d2609b2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22330: Model.__reduce__() includes cached lookups

[Django]

#22330: Model.__reduce__() includes cached lookups
-+-
 Reporter:  patrys   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 It might be related to issues like #24381, but I agree we can close this
 until we get a test case to reproduce the problem.

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

Re: [Django] #25615: multidb Relation fields do not support nested lookups

[Django]

#25615: multidb Relation fields do not support nested lookups
-+-
 Reporter:  gerdkoetje   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 I don't understand your reasoning. You cannot import models from
 seconddbapp in otherapp if you don't include it in `INSTALLED_APPS`. Maybe
 you want to set them as `managed=False` if those apps aren't managed by
 the local Django installation. Let's continue the discussion on django-
 users if you need further help. I don't see any bugs in Django yet.

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

Re: [Django] #25615: multidb Relation fields do not support nested lookups

[Django]

#25615: multidb Relation fields do not support nested lookups
-+-
 Reporter:  gerdkoetje   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by gerdkoetje):

 what does this mean?
 
https://github.com/django/django/commit/9f13c3328199d2fa70235cdc63bb06b1efc5b117

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

Re: [Django] #25615: multidb Relation fields do not support nested lookups

[Django]

#25615: multidb Relation fields do not support nested lookups
-+-
 Reporter:  gerdkoetje   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by gerdkoetje):

 in my main project that is a remote database.
 that shouldn't be in installed apps.
 so i did the same here.

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

Re: [Django] #25615: multidb Relation fields do not support nested lookups

[Django]

#25615: multidb Relation fields do not support nested lookups
-+-
 Reporter:  gerdkoetje   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by gerdkoetje):

 * status:  closed => new
 * 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/068.906039846c1248808846468275f77c3f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25615: multidb Relation fields do not support nested lookups

[Django]

#25615: multidb Relation fields do not support nested lookups
-+-
 Reporter:  gerdkoetje   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 Bisected to 9f13c3328199d2fa70235cdc63bb06b1efc5b117. You are missing
 'seconddbapp' in `INSTALLED_APPS`.

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

Re: [Django] #25417: Add a system check for an invalid default on a model field

[Django]

#25417: Add a system check for an invalid default on a model field
-+-
 Reporter:  avorio   |Owner:  charettes
 Type:  New feature  |   Status:  closed
Component:  Core (System |  Version:  master
  checks)|
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  decimal, | Triage Stage:  Ready for
  InvalidOperation, migrations   |  checkin
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette ):

 In [changeset:"da9e9484f2407ea5f2309ba1899fc93c58d206e3" da9e9484]:
 {{{
 #!CommitTicketReference repository=""
 revision="da9e9484f2407ea5f2309ba1899fc93c58d206e3"
 [1.9.x] Revert "Fixed #25417 -- Added a field check for invalid default
 values."

 This reverts commit 71ebcb85b931f43865df5b322b2cf06d3da23f69.

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

Re: [Django] #25395: Add an optional dependency on python-fastpbkdf2

[Django]

#25395: Add an optional dependency on python-fastpbkdf2
-+-
 Reporter:  Ayrx |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 I think the follow up on the mailing list hasn't happened yet.

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

Re: [Django] #25417: Add a system check for an invalid default on a model field

[Django]

#25417: Add a system check for an invalid default on a model field
-+-
 Reporter:  avorio   |Owner:  charettes
 Type:  New feature  |   Status:  closed
Component:  Core (System |  Version:  master
  checks)|
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  decimal, | Triage Stage:  Ready for
  InvalidOperation, migrations   |  checkin
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette ):

 In [changeset:"976bd519a879b2fd7a356cb21bde32696adb545f" 976bd519]:
 {{{
 #!CommitTicketReference repository=""
 revision="976bd519a879b2fd7a356cb21bde32696adb545f"
 Revert "Fixed #25417 -- Added a field check for invalid default values."

 This reverts commit 71ebcb85b931f43865df5b322b2cf06d3da23f69.
 }}}

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

Re: [Django] #17756: GeoDjango missing pyspatialite support

[Django]

#17756: GeoDjango missing pyspatialite support
-+-
 Reporter:  danols   |Owner:
 Type:  New feature  |   Status:  closed
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:  Someday/Maybe
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 pysqlite 2.7.0+ can be installed using pip as C extension loading is now
 
[https://github.com/ghaering/pysqlite/commit/76f34850be582249d9048e6acb2993943b07d31b
 enabled by default]. I believe that removes the motivation for this
 ticket.

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

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

Re: [Django] #25615: multidb Relation fields do not support nested lookups

[Django]

#25615: multidb Relation fields do not support nested lookups
-+-
 Reporter:  gerdkoetje   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by gerdkoetje):

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


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

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

Re: [Django] #16391: New URL tag for reversing urls with placeholder args/kwargs

[Django]

#16391: New URL tag for reversing urls with placeholder args/kwargs
+-
 Reporter:  h.a.clifford@…  |Owner:  nobody
 Type:  New feature |   Status:  closed
Component:  Core (URLs) |  Version:  1.3
 Severity:  Normal  |   Resolution:  wontfix
 Keywords:  | Triage Stage:  Someday/Maybe
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+-
Changes (by timgraham):

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


Comment:

 I haven't heard of much demand for this feature, so living as a third-
 party library seems okay to me.

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

Re: [Django] #21516: Update the import path for the FormSet classes and factories in documentation.

[Django]

#21516: Update the import path for the FormSet classes and factories in
documentation.
--+
 Reporter:  loic84|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timgraham):

 * easy:  0 => 1
 * stage:  Someday/Maybe => Accepted


Comment:

 This change was made in Django 1.7 and all older versions are now
 unsupported so it seems like a good time to make the change. See
 1c7a83ee8e3da431d9d21dae42da8f1f89973f7c for the functions and classes to
 update.

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

Re: [Django] #25612: django.contrib.auth should include support for 2fa out of the box

[Django]

#25612: django.contrib.auth should include support for 2fa out of the box
--+
 Reporter:  alex  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * stage:  Someday/Maybe => Accepted


Comment:

 The reception on the mailing list has been positive.

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

Re: [Django] #25615: multidb Relation fields do not support nested lookups

[Django]

#25615: multidb Relation fields do not support nested lookups
-+-
 Reporter:  gerdkoetje   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Old description:

> Does anyone know why i can't do any relation lookups on any database
> other then the default database in 1.8.5 this worked fine in 1.6.1. It
> keeps telling me: `Relation fields do not support nested lookups`.
>
> for example on
> `adds =
> ProfielenFlirts.objects.filter(voor__user__profielenuserprofile__fictief=True).filter(Q(antwoord='')
> | Q(antwoord__isnull=True)).count()`
>
> ProfielenFlirts is a non default database, the relation lookup is in the
> same database do.
>

> my router
> {{{
> class DatingRouter(object):
> def db_for_read(self, model, **hints):
> if model._meta.app_label == 'datingmodels':
> return 'dating'
> return 'default'
>
> def db_for_write(self, model, **hints):
> if model._meta.app_label == 'datingmodels':
> return 'dating'
> return 'default'
>
> def allow_relation(self, obj1, obj2, **hints):
> if obj1._meta.app_label == 'datingmodels' and
> obj2._meta.app_label == 'datingmodels':
> return True
> elif 'datingmodels' not in [obj1._meta.app_label,
> obj2._meta.app_label]:
> return True
> return False
>
> def allow_syncdb(self, db, model):
> if db == 'dating' or model._meta.app_label == "datingmodels":
> return False # we're not using syncdb on our legacy database
> else: # but all other models/databases are fine
> return True
> }}}

New description:

 He all,

 Does anyone know why i can't do any relation lookups on any database other
 then the default database in 1.8.5 this worked fine in 1.6.1
 it keeps trowing me: Relation fields do not support nested lookups

 for example on
 adds =
 
ProfielenFlirts.objects.filter(voor__user__profielenuserprofile__fictief=True).filter(Q(antwoord='')
 | Q(antwoord__isnull=True)).count()

 ProfielenFlirts is a non default database, the relation lookup is in the
 same database do.


 my router
 class DatingRouter(object):
 def db_for_read(self, model, **hints):
 if model._meta.app_label == 'datingmodels':
 return 'dating'
 return 'default'

 def db_for_write(self, model, **hints):
 if model._meta.app_label == 'datingmodels':
 return 'dating'
 return 'default'

 def allow_relation(self, obj1, obj2, **hints):
 if obj1._meta.app_label == 'datingmodels' and obj2._meta.app_label
 == 'datingmodels':
 return True
 elif 'datingmodels' not in [obj1._meta.app_label,
 obj2._meta.app_label]:
 return True
 return False

 def allow_syncdb(self, db, model):
 if db == 'dating' or model._meta.app_label == "datingmodels":
 return False # we're not using syncdb on our legacy database
 else: # but all other models/databases are fine
 return True

 any help would be appriciated

--

Comment (by gerdkoetje):

 test project proving this issue
 https://github.com/gerdkoetje/dualdbtest

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

Re: [Django] #25616: Add note regarding missing dependencies on LookupError for migrations

[Django]

#25616: Add note regarding missing dependencies on LookupError for migrations
--+
 Reporter:  mcfletch  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timgraham):

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


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

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

[Django] #25616: Add note regarding missing dependencies on LookupError for migrations

[Django]

#25616: Add note regarding missing dependencies on LookupError for migrations
--+
 Reporter:  mcfletch  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Migrations|Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+
 If you have a product package that includes migrations which depend on a
 plugin package, and you forget to include a dependency on the migration,
 you wind up with a confusing error message (raised from
 Apps.get_app_config):
 {{{
  LookupError("No installed app with label '%s'"%(label,))
 }}}
 where label is the name of the "missing" app. Which then leads the user to
 trying to figure out why the app, which is in settings.py is not showing
 up.

 It would be helpful, in `django.db.migrations.state` if we were to
 annotate the LookupError with the common issue the user is likely seeing,
 something like (on StateApps):
 {{{
 def get_app_config(self, app_label):
 try:
 return super(StateApps, self).get_app_config(app_label)
 except LookupError as err:
 err.args += ('Possibly missing dependency on a migration?', )
 raise
 }}}
 I'm not attached to the particular implementation or wording, just
 suggesting that the error message should be cleaner in the migrations-
 can't-find-app case, which is different than the general "can't find an
 app of that name" case.

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

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

Re: [Django] #25441: Add support for negative filesize to filesizeformat template filter

[Django]

#25441: Add support for negative filesize to filesizeformat template filter
-+-
 Reporter:  suffrage |Owner:  darkryder
 Type:  New feature  |   Status:  closed
Component:  Template system  |  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"ce7dd1273e5ee3d927dbfda0b38aff2517fe004b" ce7dd127]:
 {{{
 #!CommitTicketReference repository=""
 revision="ce7dd1273e5ee3d927dbfda0b38aff2517fe004b"
 Fixed #25441 -- Added support for negative filesize to filesizeformat
 template filter.

 Thanks Andrey Yakovlev for the initial patch.
 }}}

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

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

Re: [Django] #17133: get_script_name goofs when there is Apache URL rewriting

[Django]

#17133: get_script_name goofs when there is Apache URL rewriting
-+-
 Reporter:  gjanee@… |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"ea2f48ce8bd865874108af79766cdef2d197e540" ea2f48c]:
 {{{
 #!CommitTicketReference repository=""
 revision="ea2f48ce8bd865874108af79766cdef2d197e540"
 Refs #17133 -- Optimized script_url handling in get_script_name

 10ace52a added some regex processing for each request with SCRIPT_URL set.
 In a speed critical section, conditionally apply of the regex will save
 some
 resources.
 }}}

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

Re: [Django] #25615: multidb Relation fields do not support nested lookups

[Django]

#25615: multidb Relation fields do not support nested lookups
-+-
 Reporter:  gerdkoetje   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Old description:

> He all,
>
> Does anyone know why i can't do any relation lookups on any database
> other then the default database in 1.8.5 this worked fine in 1.6.1
> it keeps trowing me: Relation fields do not support nested lookups
>
> for example on
> adds =
> ProfielenFlirts.objects.filter(voor__user__profielenuserprofile__fictief=True).filter(Q(antwoord='')
> | Q(antwoord__isnull=True)).count()
>
> ProfielenFlirts is a non default database, the relation lookup is in the
> same database do.
>

> my router
> class DatingRouter(object):
> def db_for_read(self, model, **hints):
> if model._meta.app_label == 'datingmodels':
> return 'dating'
> return 'default'
>
> def db_for_write(self, model, **hints):
> if model._meta.app_label == 'datingmodels':
> return 'dating'
> return 'default'
>
> def allow_relation(self, obj1, obj2, **hints):
> if obj1._meta.app_label == 'datingmodels' and
> obj2._meta.app_label == 'datingmodels':
> return True
> elif 'datingmodels' not in [obj1._meta.app_label,
> obj2._meta.app_label]:
> return True
> return False
>
> def allow_syncdb(self, db, model):
> if db == 'dating' or model._meta.app_label == "datingmodels":
> return False # we're not using syncdb on our legacy database
> else: # but all other models/databases are fine
> return True
>
> any help would be appriciated

New description:

 Does anyone know why i can't do any relation lookups on any database other
 then the default database in 1.8.5 this worked fine in 1.6.1. It keeps
 telling me: `Relation fields do not support nested lookups`.

 for example on
 `adds =
 
ProfielenFlirts.objects.filter(voor__user__profielenuserprofile__fictief=True).filter(Q(antwoord='')
 | Q(antwoord__isnull=True)).count()`

 ProfielenFlirts is a non default database, the relation lookup is in the
 same database do.


 my router
 {{{
 class DatingRouter(object):
 def db_for_read(self, model, **hints):
 if model._meta.app_label == 'datingmodels':
 return 'dating'
 return 'default'

 def db_for_write(self, model, **hints):
 if model._meta.app_label == 'datingmodels':
 return 'dating'
 return 'default'

 def allow_relation(self, obj1, obj2, **hints):
 if obj1._meta.app_label == 'datingmodels' and obj2._meta.app_label
 == 'datingmodels':
 return True
 elif 'datingmodels' not in [obj1._meta.app_label,
 obj2._meta.app_label]:
 return True
 return False

 def allow_syncdb(self, db, model):
 if db == 'dating' or model._meta.app_label == "datingmodels":
 return False # we're not using syncdb on our legacy database
 else: # but all other models/databases are fine
 return True
 }}}

--

Comment:

 Please provide a minimal sample project that works on 1.6 and fails on
 1.8. The simpler you can make the sample project, the easier it will be to
 determine if it's a bug in your application or in Django. 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/068.702eda1bbf64b785764e47d4b9b0f887%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25441: Add support for negative filesize to filesizeformat template filter

[Django]

#25441: Add support for negative filesize to filesizeformat template filter
-+-
 Reporter:  suffrage |Owner:  darkryder
 Type:  New feature  |   Status:  assigned
Component:  Template system  |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #25609: Add a more useful error message for invalid nested lookup on a related field

[Django]

#25609: Add a more useful error message for invalid nested lookup on a related
field
-+-
 Reporter:  Ian-Foote|Owner:  Ian-Foote
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.9b1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * version:  master => 1.9b1
 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #24244: Document contrib.admin.models.LogEntry

[Django]

#24244: Document contrib.admin.models.LogEntry
--+
 Reporter:  timgraham |Owner:  varun
 Type:  New feature   |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by varun):

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


Comment:

 Patch almost ready. Creating PR by tomorrow.

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

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

Re: [Django] #25615: multidb Relation fields do not support nested lookups (was: multidm Relation fields do not support nested lookups)

[Django]

#25615: multidb Relation fields do not support nested lookups
-+-
 Reporter:  gerdkoetje   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

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

Re: [Django] #25615: multidm Relation fields do not support nested lookups

[Django]

#25615: multidm Relation fields do not support nested lookups
-+-
 Reporter:  gerdkoetje   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by gerdkoetje):

 * component:  Uncategorized => Database layer (models, ORM)
 * needs_better_patch:   => 0
 * type:  Uncategorized => Bug
 * needs_tests:   => 0
 * needs_docs:   => 0


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

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

[Django] #25615: multidm Relation fields do not support nested lookups

[Django]

#25615: multidm Relation fields do not support nested lookups
---+
 Reporter:  gerdkoetje |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.8
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 He all,

 Does anyone know why i can't do any relation lookups on any database other
 then the default database in 1.8.5 this worked fine in 1.6.1
 it keeps trowing me: Relation fields do not support nested lookups

 for example on
 adds =
 
ProfielenFlirts.objects.filter(voor__user__profielenuserprofile__fictief=True).filter(Q(antwoord='')
 | Q(antwoord__isnull=True)).count()

 ProfielenFlirts is a non default database, the relation lookup is in the
 same database do.


 my router
 class DatingRouter(object):
 def db_for_read(self, model, **hints):
 if model._meta.app_label == 'datingmodels':
 return 'dating'
 return 'default'

 def db_for_write(self, model, **hints):
 if model._meta.app_label == 'datingmodels':
 return 'dating'
 return 'default'

 def allow_relation(self, obj1, obj2, **hints):
 if obj1._meta.app_label == 'datingmodels' and obj2._meta.app_label
 == 'datingmodels':
 return True
 elif 'datingmodels' not in [obj1._meta.app_label,
 obj2._meta.app_label]:
 return True
 return False

 def allow_syncdb(self, db, model):
 if db == 'dating' or model._meta.app_label == "datingmodels":
 return False # we're not using syncdb on our legacy database
 else: # but all other models/databases are fine
 return True

 any help would be appriciated

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

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

Re: [Django] #24244: Document contrib.admin.models.LogEntry

[Django]

#24244: Document contrib.admin.models.LogEntry
--+
 Reporter:  timgraham |Owner:
 Type:  New feature   |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by claudep):

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


Comment:

 When no progress has been made after several months, feel free to take any
 ticket!

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

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

Re: [Django] #25596: Can't change user's password in admin when using custom User model

[Django]

#25596: Can't change user's password in admin when using custom User model
-+-
 Reporter:  user0007 |Owner:  timgraham
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.9b1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"0b4d11e1751a4e2368f0e4faa121e10ff1f73167" 0b4d11e1]:
 {{{
 #!CommitTicketReference repository=""
 revision="0b4d11e1751a4e2368f0e4faa121e10ff1f73167"
 [1.9.x] Fixed #25596 -- Fixed regression in password change view with
 custom user model.

 The reverse() added in 50aa1a790ca66c2a93e0a52e00c53375b269ff49
 crashed on a custom user model.

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

Re: [Django] #25614: Changing ForeignKey(on_delete=...) unnecessarily drops and recreates constraints (was: MigrationAutodetector is too greedy when ForeignKey(on_delete=...) is changed)

[Django]

#25614: Changing ForeignKey(on_delete=...) unnecessarily drops and recreates
constraints
+--
 Reporter:  jdunck  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.8
 Severity:  Normal  |   Resolution:  duplicate
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by timgraham):

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


Comment:

 Looks like a duplicate of #25253. We don't currently exclude any model
 field attributes from deconstruct so that's unlikely to be the solution
 unless we change the design decision around that.

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

Re: [Django] #25253: MySQL migrations drop & recreate constraints unnecessarily when changing attributes that don't affect the schema (was: Migrations do unnecessary work when adding `blank=True` to M

[Django]

#25253: MySQL migrations drop & recreate constraints unnecessarily when changing
attributes that don't affect the schema
--+
 Reporter:  trecouvr  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:  migrations m2m mysql  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by timgraham):

 #25614 reported the same unnecessary dropping/adding of constraints when
 changing `ForeignKey.on_delete`. I assume that's a duplicate of this
 ticket, but please reopen it if fixing this issue doesn't also fix it.

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

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

Re: [Django] #25596: Can't change user's password in admin when using custom User model

[Django]

#25596: Can't change user's password in admin when using custom User model
-+-
 Reporter:  user0007 |Owner:  timgraham
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.9b1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"5acf203db2e9562dbe4073bf85d5043ef3121ea9" 5acf203]:
 {{{
 #!CommitTicketReference repository=""
 revision="5acf203db2e9562dbe4073bf85d5043ef3121ea9"
 Fixed #25596 -- Fixed regression in password change view with custom user
 model.

 The reverse() added in 50aa1a790ca66c2a93e0a52e00c53375b269ff49
 crashed on a custom 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/066.7a775f4088c10391ad5bc4dc209cc5aa%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25597: Python 3 compatibility error in PostgreSQL array form fields

[Django]

#25597: Python 3 compatibility error in PostgreSQL array form fields
-+-
 Reporter:  BertrandBordage  |Owner:  Tim
 |  Graham 
 Type:  Bug  |   Status:  closed
Component:  contrib.postgres |  Version:  1.8
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"64a9115bcecf48bce2e7a84d165a6628e2ce607c" 64a9115b]:
 {{{
 #!CommitTicketReference repository=""
 revision="64a9115bcecf48bce2e7a84d165a6628e2ce607c"
 [1.9.x] Fixed #25597 -- Fixed crash with SplitArrayField and IntegerField
 on invalid value.

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

Re: [Django] #25597: Python 3 compatibility error in PostgreSQL array form fields

[Django]

#25597: Python 3 compatibility error in PostgreSQL array form fields
-+-
 Reporter:  BertrandBordage  |Owner:  Tim
 |  Graham 
 Type:  Bug  |   Status:  closed
Component:  contrib.postgres |  Version:  1.8
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"69e6045ceb18d859a1586bcd5e64f9b786d87c32" 69e6045c]:
 {{{
 #!CommitTicketReference repository=""
 revision="69e6045ceb18d859a1586bcd5e64f9b786d87c32"
 [1.8.x] Fixed #25597 -- Fixed crash with SplitArrayField and IntegerField
 on invalid value.

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

Re: [Django] #25597: Python 3 compatibility error in PostgreSQL array form fields

[Django]

#25597: Python 3 compatibility error in PostgreSQL array form fields
-+-
 Reporter:  BertrandBordage  |Owner:  Tim
 |  Graham 
 Type:  Bug  |   Status:  closed
Component:  contrib.postgres |  Version:  1.8
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham ):

 * status:  new => closed
 * owner:   => Tim Graham 
 * resolution:   => fixed


Comment:

 In [changeset:"1f07da3e29c7c3d47968e1c4531dd9bf902575b7" 1f07da3e]:
 {{{
 #!CommitTicketReference repository=""
 revision="1f07da3e29c7c3d47968e1c4531dd9bf902575b7"
 Fixed #25597 -- Fixed crash with SplitArrayField and IntegerField on
 invalid value.
 }}}

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

Re: [Django] #25550: Deprecate direct assignment to the reverse side of a related set

[Django]

#25550: Deprecate direct assignment to the reverse side of a related set
-+-
 Reporter:  timgraham|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"9c5e272860c076736237d4b280c7c922c46ba273" 9c5e2728]:
 {{{
 #!CommitTicketReference repository=""
 revision="9c5e272860c076736237d4b280c7c922c46ba273"
 Fixed #25550 -- Deprecated direct assignment to the reverse side of a
 related set.
 }}}

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

Re: [Django] #25605: GeoDjango DB functions doesn't really work with expressions

[Django]

#25605: GeoDjango DB functions doesn't really work with expressions
+
 Reporter:  sir-sigurd  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  GIS |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+
Changes (by timgraham):

 * needs_better_patch:  0 => 1


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

Re: [Django] #9025: Nested Inline Support in Admin

[Django]

#9025: Nested Inline Support in Admin
---+
 Reporter:  pixelcort  |Owner:  auvipy
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  Bug?   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  1
---+
Changes (by timgraham):

 * cc: datakid@… (removed)


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

Re: [Django] #12885: GenericRelation fails to join the related table from a inherited model

[Django]

#12885: GenericRelation fails to join the related table from a inherited model
--+
 Reporter:  semenov   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.contenttypes  |  Version:  1.1
 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 akaariai):

 * has_patch:  0 => 1


Comment:

 I've created a PR for this (see
 https://github.com/django/django/pull/5487). Luckily the changes needed
 here were only to contrib.contenttypes. This is always a good sign, we
 likely don't have a more fundamental problem. Lets see what CI things of
 my PR...

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

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

Re: [Django] #15130: Model.validate_unique method doesn't take in account multi-db

[Django]

#15130: Model.validate_unique method doesn't take in account multi-db
-+-
 Reporter:  t2y  |Owner:
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  multi-db | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by akaariai):

 Hmmh, I think the core problem is that .validate() doesn't take a using
 argument, while some of the checks are dependent on the used database. I
 don't think we can fix this without adding the using argument.

 If we do that, then ModelForms should likely also have
 .is_valid(using=...) keyword argument. The next question is should the
 using argument be used for ModelChoiceField queryset checks, too? I say
 yes, with the exception that if the queryset has an explicit using
 argument, then honor that.

 We can start with adding using argument to .validate() only, and then
 continue to further changes if wanted.

 Any opinions if we should go forward with 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/061.d82b39231c0463c2a3d6c99801542746%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24421: Querying a reverse ForeignObject relation using exclude() fails

[Django]

#24421: Querying a reverse ForeignObject relation using exclude() fails
-+-
 Reporter:  animan1  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.7
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ForeignObject,   | Triage Stage:  Accepted
  MySQL, SQLite  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by akaariai):

 We don't have the smarts to handle exclude() queries for multicolumn joins
 just yet in Django. Fixing this requires changing Django to use EXISTS
 queries, as not all backends support multicolumn IN clauses of the form
 (WHERE col1, col2 IN (SELECT innercol1, innercol2 FROM ...).

 We have other reasons to prefer EXISTS queries, too.  For one, PostgreSQL
 performs very badly with NOT IN queries.

 Unfortunately fixing this properly will likely require multiple days of
 work.

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

Re: [Django] #22330: Model.__reduce__() includes cached lookups

[Django]

#22330: Model.__reduce__() includes cached lookups
-+-
 Reporter:  patrys   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by akaariai):

 If nobody offers a good reason why this must be changed, I think we should
 opt for keeping the current behavior. Sometimes you might actually want to
 pickle the related instances,  too. And, changes here might result in
 performance changes for deployed applications, which are nasty to detect
 when updating Django. One example is that caching results of
 select_related queryset would not cache the related selections after the
 change.

 Above, the RuntimeError thrown by pickling looks like a good argument for
 fixing. But as long as we don't have a test to reproduce this issue, it is
 hard to say if the problem is in Django or how to fix the problem if it is
 in Django.

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

Re: [Django] #8467: For ManyToMany manager, we should convert objects being added or removed to the pk type if they are not.

[Django]

#8467: For ManyToMany manager, we should convert objects being added or removed 
to
the pk type if they are not.
-+-
 Reporter:  Wonlay   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  Duplicate entry, | Triage Stage:  Accepted
  add, remove, ManyToManyField   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by akaariai):

 I think we should fix this on the basis that using b.a.add('1') works
 partly, but the duplication check doesn't work. Either we should reject
 strings where ints are required, or handle type coercions fully.

 To fix this, we should coerce the input values to right type right at the
 beginning of add() and remove(). The same applies likely also to reverse
 foreign key sets. Still, we need to convert to the primary key type of the
 target model, that is, the code should work also when A had a custom
 primary key (for example, A.name was primary key).

 Tests for m2m.add can be found from
 
https://github.com/akaariai/django/commit/b1308c114f601db2f3f0c8d76c55acd966a14672.
 Similar tests should be added for .remove(), and for reverse foreign key
 .add() and .remove().

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

Re: [Django] #9368: Clean up code for getting columns for select query

[Django]

#9368: Clean up code for getting columns for select query
-+-
 Reporter:  adunar   |Owner:
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:
  (models, ORM)  |
 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 akaariai):

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


Comment:

 There is likely more we can clean in select clause generation, but the
 main issue of this ticket (duplication of login) has been 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/064.6c12558f07473eea8cbdeb1a1675a877%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.