[Django] #32276: Adding a UUIDField (default=uuid4, editable=False, unique=True) to an existing model results in IntegrityErrors on the migration

[Django]

#32276: Adding a UUIDField (default=uuid4, editable=False, unique=True) to an
existing model results in IntegrityErrors on the migration
-+-
   Reporter:  GaramNick  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Database   |Version:  3.1
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Hi,

 When adding a UUIDField to an existing model as per the following code I
 run into IntegrityErrors because of UUID collisions.

 Django 3.1 & PostgreSQL 11.8

 Before
 {{{
 from django.db import models

 class Enum(models.Model)
 definition = models.CharField(unique=True, max_length=128)
 }}}

 After
 {{{
 from uuid import uuid4
 from django.db import models

 class Enum(models.Model)
 definition = models.CharField(unique=True, max_length=128)
 uid = models.UUIDField(default=uuid4, editable=False, unique=True)
 }}}

 Migration

 {{{
 Applying main.0039_enum_uid...Traceback (most recent call last):
   File "/home/xxx/.local/share/virtualenvs/xxx--9c6SIiZ/lib/python3.8
 /site-packages/django/db/backends/utils.py", line 84, in _execute
 return self.cursor.execute(sql, params)
 psycopg2.errors.UniqueViolation: could not create unique index
 "main_enum_uid_key"
 DETAIL:  Key (uid)=(cad607b1-6e38-4f99-a5fb-f73c2e3e5ad3) is duplicated.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.3f7e870a97ba9f317daf78729f7daa7d%40djangoproject.com.

Re: [Django] #32273: Document AdminSite.unregister().

[Django]

#32273: Document AdminSite.unregister().
-+-
 Reporter:  Adam (Chainz)|Owner:  Hasan
  Johnson|  Ramezani
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  contrib.admin|  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 Mariusz Felisiak ):

 In [changeset:"8f384505eee8ce95667d77cfc2a07d4abe63557c" 8f38450]:
 {{{
 #!CommitTicketReference repository=""
 revision="8f384505eee8ce95667d77cfc2a07d4abe63557c"
 Refs #32273 -- Completed test coverage for AdminSite.unregister().
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.b8be1fdc93a585c258ca6e89442bc18f%40djangoproject.com.

Re: [Django] #32272: gettext_lazy inconsistent error when nested

[Django]

#32272: gettext_lazy inconsistent error when nested
+--
 Reporter:  John Bazik  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Utilities   |  Version:  3.1
 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 Mariusz Felisiak):

 * cc: Claude Paroz (added)
 * keywords:  claudep =>


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.7d7435daf29ef448f6b5e3449e79afd6%40djangoproject.com.

Re: [Django] #32272: gettext_lazy inconsistent error when nested

[Django]

#32272: gettext_lazy inconsistent error when nested
+--
 Reporter:  John Bazik  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Utilities   |  Version:  3.1
 Severity:  Normal  |   Resolution:
 Keywords:  claudep | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by Carlton Gibson):

 * keywords:   => claudep


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.65059de0fcab26d963b9124d2b986096%40djangoproject.com.

Re: [Django] #32271: Documentation consistency between display views and edit views

[Django]

#32271: Documentation consistency between display views and edit views
-+-
 Reporter:  Carles Pina Estany   |Owner:  Carles
 Type:   |  Pina Estany
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  3.1
 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 Carlton Gibson):

 * owner:  nobody => Carles Pina Estany
 * status:  new => assigned
 * stage:  Unreviewed => Accepted


Comment:

 Hi Carles. Yes, OK… 😄 I think this fits under the small cosmetic changes
 not needing a ticket. If you'd like to make a PR `Fixed #32271 -- Improved
 naming consistency in CBV code examples.` then that would be great.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.c1a55ccd1b43c150daf3034a3e0ebfd2%40djangoproject.com.

Re: [Django] #29867: Allow cache.get_or_set() to cache a None result

[Django]

#29867: Allow cache.get_or_set() to cache a None result
-+-
 Reporter:  Phill Tornroth   |Owner:  Nick Pope
 Type:  Bug  |   Status:  assigned
Component:  Core (Cache system)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.a3367d2b797f3dcac9e95c70dde154fc%40djangoproject.com.

Re: [Django] #32275: Add scrypt password hasher

[Django]

#32275: Add scrypt password hasher
--+--
 Reporter:  Alex Gaynor   |Owner:  Anthony Wright
 Type:  New feature   |   Status:  assigned
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 Anthony Wright):

 * cc: Anthony Wright (added)
 * owner:  nobody => Anthony Wright
 * status:  new => assigned


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

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

Re: [Django] #32089: prefetch_related_objects() does not work for reused model instances.

[Django]

#32089: prefetch_related_objects() does not work for reused model instances.
-+-
 Reporter:  Dennis Kliban|Owner:
 |  AlexeyNigin
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.2
  (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 Mariusz Felisiak ):

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


Comment:

 In [changeset:"b9ba85a7ce582f4821a21119a6c130dacab496c4" b9ba85a]:
 {{{
 #!CommitTicketReference repository=""
 revision="b9ba85a7ce582f4821a21119a6c130dacab496c4"
 Fixed #32089 -- Fixed prefetch_related_objects() when some objects are
 already fetched.

 Thanks Dennis Kliban for the report and Adam Johnson for the initial
 patch.

 Co-authored-by: Adam Johnson 
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.4903284c00d03756b6c234803056d78a%40djangoproject.com.

Re: [Django] #32275: Add scrypt password hasher (was: Offer an scrypt based password hasher)

[Django]

#32275: Add scrypt password hasher
--+
 Reporter:  Alex Gaynor   |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 Mariusz Felisiak):

 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.8b77732332b63257f06c9cc1a6da1a3c%40djangoproject.com.

Re: [Django] #32267: Unable to unapply a branch of migrations

[Django]

#32267: Unable to unapply a branch of migrations
---+--
 Reporter:  Roman Odaisky  |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Migrations |  Version:  3.1
 Severity:  Normal |   Resolution:  wontfix
 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 Mariusz Felisiak):

 You can start a discussion on DevelopersMailingList if you don't agree.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.634b78ef958088d3ed2615f04328a1bb%40djangoproject.com.

Re: [Django] #32267: Unable to unapply a branch of migrations

[Django]

#32267: Unable to unapply a branch of migrations
---+--
 Reporter:  Roman Odaisky  |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Migrations |  Version:  3.1
 Severity:  Normal |   Resolution:  wontfix
 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 Mariusz Felisiak):

 * resolution:  invalid => wontfix


Comment:

 Again, you're trying to fix a really specific situation that we don't want
 to support, IMO. You want to unapply migrations and then (probably) remove
 reverted migrations, this is not a flow that is supported. Also, this can
 corrupt a database if you will have any migrations created after a "merge"
 migration (`0053m` in your example).

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.282ff1fa65419adc2ae1ddcefd81f986%40djangoproject.com.

Re: [Django] #32274: Template Does Not Exist

[Django]

#32274: Template Does Not Exist
-+-
 Reporter:  Aditya Ravindra  |Owner:  nobody
  Tulpule|
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  3.1
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  template issue   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

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


Comment:

 Please don't use Trac as a support channel. Closing per
 TicketClosingReasons/UseSupportChannels.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.f04e7531801e92ed35273c712aa6b6cf%40djangoproject.com.

Re: [Django] #32267: Unable to unapply a branch of migrations

[Django]

#32267: Unable to unapply a branch of migrations
---+--
 Reporter:  Roman Odaisky  |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Migrations |  Version:  3.1
 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 Roman Odaisky):

 It turned out to be rather simple to implement:
 https://github.com/django/django/pull/13781

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.09d4833db55996d63070ec28adb6d564%40djangoproject.com.

Re: [Django] #32275: Offer an scrypt based password hasher

[Django]

#32275: Offer an scrypt based password hasher
--+--
 Reporter:  Alex Gaynor   |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.auth  |  Version:  master
 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 Alex Gaynor):

 I should note, that while I can't make any commitments on behalf of a 3rd
 party, I think there's a reasonable chance this would qualify for a reward
 under Google's Patch Rewards program:
 https://www.google.com/about/appsecurity/patch-rewards/ (I have no
 affiliation with Google)

 Link to the scrypt docs:
 https://docs.python.org/3/library/hashlib.html#hashlib.scrypt

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.6073bcc61a36c3547136a35d1208255b%40djangoproject.com.

[Django] #32275: Offer an scrypt based password hasher

[Django]

#32275: Offer an scrypt based password hasher
+
   Reporter:  Alex Gaynor   |  Owner:  nobody
   Type:  New feature   | 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 |
+
 Currently django defaults to PBKDF2, with options (using third party
 libraries) for bcrypt and argon2 (and then a large number of legacy
 options that should be avoided).

 When PBKDF2 was originally chosen as the default, it was selected because
 it was the most secure option that could reasonably be implemented in pure
 Python with the stdlib.

 As of Python 3.6, scrypt is available in the stdlib. scrypt is also
 substantially more secure than PBKDF2, because it is memory hard. See
 https://www.tarsnap.com/scrypt/scrypt.pdf (page 14) for a table that
 assess the relative cost-to-brute-force of scrypt vs. PBKDF2 at the
 interactive latency.

 For these reasons, I think it'd be appropriate for Django to include an
 scrypt based hasher, and even to default to it for new installations.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/047.2e98935a9af3714bcf6d1a5e9fc5b47b%40djangoproject.com.

[Django] #32274: Template Does Not Exist

[Django]

#32274: Template Does Not Exist
-+-
   Reporter:  Aditya |  Owner:  nobody
  Ravindra Tulpule   |
   Type:  Bug| Status:  new
  Component:  Template   |Version:  3.1
  system |
   Severity:  Normal |   Keywords:  template issue
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 I am trying to render a " html " template file from views. But even after
 registering the right path at DIRS in the settings I am not able to render
 this page. # Need help !

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/049.13264dff049e3f70b7baa63bddf095d1%40djangoproject.com.

Re: [Django] #32267: Unable to unapply a branch of migrations

[Django]

#32267: Unable to unapply a branch of migrations
---+--
 Reporter:  Roman Odaisky  |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Migrations |  Version:  3.1
 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 Roman Odaisky):

 Replying to [comment:4 Mariusz Felisiak]:
 > > Can we at the very least add something like `manage.py migrate
 --unapply-one  ` that would unapply one migration, having
 ensured that no currently applied migrations depend on it? This will solve
 the use case I outlined and maybe some others while not being able to
 corrupt the DB state.
 >
 > Migrations can be reversed, see
 [https://docs.djangoproject.com/en/3.1/topics/migrations/#reversing-
 migrations docs]. However adding an option to reverse a specific migration
 doesn't sound like a good idea, we will not be able to ensure that a
 database state is not corrupted. Migrations history must be continuous.

 If we just do one check: that no children of this particular migration are
 applied. Does that not allow us to reverse the migration while
 guaranteeing consistency?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.530b39e33273181f8fb4d984a470f6a2%40djangoproject.com.

Re: [Django] #21227: Selenium tests terminate with [Errno 10054]

[Django]

#21227: Selenium tests terminate with [Errno 10054]
-+-
 Reporter:  Kevin Christopher|Owner:  nobody
  Henry  |
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  selenium | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

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


Comment:

 Fixed in 772eca0b0219f63129282c3596fc210951433c13 because `WSGIServer` now
 suppress `ConnectionResetError`.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.d4f1bbcca70a8952a9dbe690fbb01a6e%40djangoproject.com.

Re: [Django] #31527: Admindocs' View index assumes settings.ROOT_URLCONF is an import string

[Django]

#31527: Admindocs' View index assumes settings.ROOT_URLCONF is an import string
-+-
 Reporter:  Keryn Knight |Owner:
 Type:   |  Qihao(Jim) Xie
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admindocs|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.4d451153231c706cc6f7f1ee7a9349a1%40djangoproject.com.

Re: [Django] #32089: prefetch_related_objects() does not work for reused model instances.

[Django]

#32089: prefetch_related_objects() does not work for reused model instances.
-+-
 Reporter:  Dennis Kliban|Owner:
 |  AlexeyNigin
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  2.2
  (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 Mariusz Felisiak):

 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.d47151ead41e4f0a1d27991499ecd494%40djangoproject.com.

Re: [Django] #25707: Use py.test for internal testing

[Django]

#25707: Use py.test for internal testing
-+-
 Reporter:  Olivier Le Thanh |Owner:  nobody
  Duong  |
 Type:  New feature  |   Status:  closed
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 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 Mariusz Felisiak):

 * status:  new => closed
 * resolution:   => wontfix
 * stage:  Someday/Maybe => Unreviewed


Comment:

 Closing as `wontfix` after [https://groups.google.com/g/django-
 developers/c/3LCCRh8HgwA discussion] on the mailing list.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.44b07edff701886223a2a06f54b71224%40djangoproject.com.