Re: [Django] #35285: Optimize ForeignObject._check_unique_target

[Django]

#35285: Optimize ForeignObject._check_unique_target
-+-
 Reporter:  Adam Johnson |Owner:  Adam
 Type:   |  Johnson
  Cleanup/optimization   |   Status:  closed
Component:  Database layer   |  Version:  dev
  (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 ):

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

Comment:

 In [changeset:"e5ec11a84d6f3725220360e893050cb00403a22e" e5ec11a]:
 {{{#!CommitTicketReference repository=""
 revision="e5ec11a84d6f3725220360e893050cb00403a22e"
 Fixed #35285 -- Optimized ForeignObject._check_unique_target().
 }}}
-- 
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/0107018e2c459651-27b0daa9-cca3-415d-8762-915b3f16fbfc-00%40eu-central-1.amazonses.com.

Re: [Django] #31014: add FromWKB and FromWKT GIS functions

[Django]

#31014: add FromWKB and FromWKT GIS functions
-+
 Reporter:  Sergey Fedoseev  |Owner:  Claude Paroz
 Type:  New feature  |   Status:  assigned
Component:  GIS  |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  wkt, wkb | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by Mariusz Felisiak):

 * needs_better_patch:  0 => 1
 * needs_docs:  0 => 1
 * owner:  (none) => Claude Paroz
 * 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/0107018e2c09f882-938ce3f2-1d79-4de1-93ef-322c69d5e680-00%40eu-central-1.amazonses.com.

Re: [Django] #35287: manage createsuperuser too restrictive

[Django]

#35287: manage createsuperuser too restrictive
-+-
 Reporter:  Matthew Pava |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  5.0
  commands)  |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  createsuperuser  | Triage Stage:
  username   |  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:   => duplicate
 * status:  new => closed

Comment:

 Duplicate of #26412.
-- 
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/0107018e2bf70e8b-73d9061b-8d61-4ade-a01d-7b5c9d7244f1-00%40eu-central-1.amazonses.com.

[Django] #35287: manage createsuperuser too restrictive

[Django]

#35287: manage createsuperuser too restrictive
-+-
   Reporter:  Matthew|  Owner:  nobody
  Pava   |
   Type:  Bug| Status:  new
  Component:  Core   |Version:  5.0
  (Management commands)  |   Keywords:  createsuperuser
   Severity:  Normal |  username
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 I have a custom user model inheriting from `AbstractUser`. I set `username
 = None` because I don't care about usernames. I care about emails. Anyway,
 whenever I do that, I get an error message from the `manage
 createsuperuser` command.

 For example:

 {{{
 TypeError: UserManager.create_superuser() missing 1 required positional
 argument: 'username'
 ValueError: The given username must be set
 TypeError: StudentManager._create_user() takes from 1 to 3 positional
 arguments but 4 were given
 }}}



 This has forced me to customize the `UserManager`:

 {{{
 class MyUserManager(UserManager):
 def _create_user(self, username=None, email=None, password=None,
 **extra_fields):
 email = self.normalize_email(email)
 user = self.model(email=email, **extra_fields)
 user.password = make_password(password)
 user.save(using=self._db)
 return user

 def create_superuser(self, email=None, password=None, **extra_fields):
 super().create_superuser(email, password, **extra_fields)
 }}}

 My rationale for not having or requiring a username is that all valid
 email addresses are unique. I think the `createsuperuser` command ought to
 be more lenient in regard to the `username` field.
-- 
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/0107018e2be916f6-6cc5657d-23bc-41a2-b362-2d4d2e1e9d45-00%40eu-central-1.amazonses.com.

Re: [Django] #35285: Optimize ForeignObject._check_unique_target

[Django]

#35285: Optimize ForeignObject._check_unique_target
-+-
 Reporter:  Adam Johnson |Owner:  Adam
 Type:   |  Johnson
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (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/0107018e2bdb92a1-305d0ebe-cc21-42a5-ad90-5ac5a36f62df-00%40eu-central-1.amazonses.com.

Re: [Django] #35270: Optimize Model._meta._property_names

[Django]

#35270: Optimize Model._meta._property_names
-+-
 Reporter:  Adam Johnson |Owner:  Adam
 Type:   |  Johnson
  Cleanup/optimization   |   Status:  closed
Component:  Database layer   |  Version:  dev
  (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):

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

Comment:

 Fixed by faeb92ea13f0c1b2cc83f45b512f2c41cfb4f02d.
-- 
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/0107018e2bc8e8b2-aae1858e-a673-4722-b905-0c192fcf9c4e-00%40eu-central-1.amazonses.com.

Re: [Django] #22125: Unnecessary creation of index for ManyToManyField

[Django]

#22125: Unnecessary creation of index for ManyToManyField
-+-
 Reporter:  tbhtan3@…|Owner:  Akash
 Type:   |  Kumar Sen
  Cleanup/optimization   |   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  db-indexes   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

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

Comment:

 Replying to [comment:32 django tester]:

 Please don't close ticket without any feedback.
-- 
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/0107018e2bc4529d-5f34550e-0104-434c-ace7-4624b1ad1913-00%40eu-central-1.amazonses.com.

Re: [Django] #22125: Unnecessary creation of index for ManyToManyField

[Django]

#22125: Unnecessary creation of index for ManyToManyField
-+-
 Reporter:  tbhtan3@…|Owner:  Akash
 Type:   |  Kumar Sen
  Cleanup/optimization   |   Status:  closed
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  db-indexes   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by django tester):

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

-- 
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/0107018e2b519827-906ebefc-cf17-42a3-88a8-6d38dc245bf1-00%40eu-central-1.amazonses.com.

Re: [Django] #35233: Push templates checks down to backend engine classes

[Django]

#35233: Push templates checks down to backend engine classes
-+-
 Reporter:  Adam Johnson |Owner:  Giannis
 Type:   |  Terzopoulos
  Cleanup/optimization   |   Status:  assigned
Component:  Core (System |  Version:  dev
  checks)|
 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 Adam Johnson):

 >  Regarding this, am I right in assuming that we want to allow same names
 for tags across different engines; Should this test pass?

 Yes, I think so. You can use two `DjangoTemplates` backends and it would
 still be valid.

 >  And one more thing, I am noticing that the E001 logic is duplicated:

 Indeed, that is true. The system check was added in #24922 because the
 exception would only appear at runtime, because the backend would only be
 created lazily. But by actioning this ticket, we’ll force backends to all
 be instantiated during checks, which will make the exception appear then.
 So we should be able to remove E001 as part of this 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018e2a6da869-ae3091ef-89c9-482d-aa2a-4a7d76661a5b-00%40eu-central-1.amazonses.com.

Re: [Django] #35233: Push templates checks down to backend engine classes

[Django]

#35233: Push templates checks down to backend engine classes
-+-
 Reporter:  Adam Johnson |Owner:  Giannis
 Type:   |  Terzopoulos
  Cleanup/optimization   |   Status:  assigned
Component:  Core (System |  Version:  dev
  checks)|
 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 Giannis Terzopoulos):

 Thank you for the pointers Adam! I finally found the time to look into
 this and I have some questions.
 > 2. `check_for_template_tags_with_the_same_name` is inaccurate because it
 combines `libraries` from all template backends, so might report an issue
 when none exists.
 Regarding this, am I right in assuming that we want to allow same names
 for tags across different engines; Should this test pass?

 {{{
 #!python
 def test_different_backends_may_have_same_tags(self):
 with self.settings(
 TEMPLATES=[
 {"BACKEND": "django.template.backends.django.DjangoTemplates",
  "OPTIONS": {"libraries": {
  "same_tags":
 "check_framework.template_test_apps.same_tags_app_1"
   ".templatetags.same_tags"}}},
 {"BACKEND": "django.template.backends.OtherBackend",
  "OPTIONS": {"libraries": {
  "same_tags":
 "check_framework.template_test_apps.same_tags_app_2"
   ".templatetags.same_tags"}}}
 ]
 ):
 self.assertListEqual(check_for_template_tags_with_the_same_name(None), [])
 }}}

 And one more thing, I am noticing that the `E001` logic is duplicated:
 - in `Engine.__init__` - raises `ImproperlyConfigured`
 
(`template_backends.test_utils.TemplateUtilsTests.test_backend_improperly_configured`)
 - and in `check_setting_app_dirs_loaders` (tests under
 `check_framework.test_templates.CheckTemplateSettingsAppDirsTest`)
 and I am wondering if it's enough to keep one of the two, perhaps the
 check? 🤔
-- 
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/0107018e2a421d21-84a6da70-fc24-4b0e-9290-57b24af7d009-00%40eu-central-1.amazonses.com.

Re: [Django] #31014: add FromWKB and FromWKT GIS functions

[Django]

#31014: add FromWKB and FromWKT GIS functions
-+
 Reporter:  Sergey Fedoseev  |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  GIS  |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  wkt, wkb | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Claude Paroz):

 * has_patch:  0 => 1

Comment:

 [https://github.com/django/django/pull/17963 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018e29cb8693-8bc87aba-05fc-4482-94d9-838fcf867e48-00%40eu-central-1.amazonses.com.

Re: [Django] #35286: dead top-down parsing reference URL is dead

[Django]

#35286: dead top-down parsing reference URL is dead
-+-
 Reporter:  umair mehmood|Owner:  umair
 Type:   |  mehmood
  Cleanup/optimization   |   Status:  closed
Component:  Template system  |  Version:  5.0
 Severity:  Normal   |   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 GitHub ):

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

Comment:

 In [changeset:"4114179ca7e025c044b721953b90aa33e4c4e442" 4114179c]:
 {{{#!CommitTicketReference repository=""
 revision="4114179ca7e025c044b721953b90aa33e4c4e442"
 Fixed #35286 -- Updated broken link in django/template/smartif.py
 docstring.
 }}}
-- 
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/0107018e29c15b6b-4519fc20-0728-458c-a648-5e5462da525b-00%40eu-central-1.amazonses.com.

Re: [Django] #35280: iriencode example incorrect

[Django]

#35280: iriencode example incorrect
-+-
 Reporter:  minusf   |Owner:  Can Huynh
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  5.0
 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:  1|UI/UX:  0
-+-
Comment (by Mariusz Felisiak ):

 In [changeset:"ef23305a19c39b26bc25e2df68355743652e77ab" ef23305]:
 {{{#!CommitTicketReference repository=""
 revision="ef23305a19c39b26bc25e2df68355743652e77ab"
 [5.0.x] Fixed #35280 -- Improved iriencode filter example in docs.

 Backport of a7baa874d8452859060ecd28c83cecd566f756e3 from main
 }}}
-- 
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/0107018e297cbdca-23eb9f18-56cc-4ded-8f53-9c0f84b45669-00%40eu-central-1.amazonses.com.

Re: [Django] #35280: iriencode example incorrect

[Django]

#35280: iriencode example incorrect
-+-
 Reporter:  minusf   |Owner:  Can Huynh
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  5.0
 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:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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

Comment:

 In [changeset:"a7baa874d8452859060ecd28c83cecd566f756e3" a7baa87]:
 {{{#!CommitTicketReference repository=""
 revision="a7baa874d8452859060ecd28c83cecd566f756e3"
 Fixed #35280 -- Improved iriencode filter example in docs.
 }}}
-- 
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/0107018e297c76f1-f495b437-cf9c-49c2-84c8-84663ef66fa0-00%40eu-central-1.amazonses.com.

Re: [Django] #35286: dead top-down parsing reference URL is dead

[Django]

#35286: dead top-down parsing reference URL is dead
-+-
 Reporter:  umair mehmood|Owner:  umair
 Type:   |  mehmood
  Cleanup/optimization   |   Status:  assigned
Component:  Template system  |  Version:  5.0
 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 umair mehmood):

 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018e294a1bf7-3b0cfdbf-4903-4a68-ba55-767d8e3f19cd-00%40eu-central-1.amazonses.com.

Re: [Django] #35286: dead top-down parsing reference URL is dead

[Django]

#35286: dead top-down parsing reference URL is dead
-+-
 Reporter:  umair mehmood|Owner:  umair
 Type:   |  mehmood
  Cleanup/optimization   |   Status:  assigned
Component:  Template system  |  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Comment (by umair mehmood):

 Replying to [comment:2 Simon Charette]:
 > [http://web.archive.org/web/20160304015821/http://effbot.org/zone
 /simple-iterator-parser.htm This archived link] referred to by [https
 ://11l-lang.org/archive/simple-top-down-parsing/ what appears to be the
 author] seems to be a better alternative.

 Thanks for sharing this, I have update the URL.
-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018e2941777c-65662f0c-1103-4e28-8d04-d7c8a0ad142c-00%40eu-central-1.amazonses.com.

Re: [Django] #35286: dead top-down parsing reference URL is dead

[Django]

#35286: dead top-down parsing reference URL is dead
-+-
 Reporter:  umair mehmood|Owner:  umair
 Type:   |  mehmood
  Cleanup/optimization   |   Status:  assigned
Component:  Template system  |  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by umair mehmood):

 * 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/0107018e29401924-56f972b3-9333-4ab4-86e5-84cde276a964-00%40eu-central-1.amazonses.com.

Re: [Django] #35286: dead top-down parsing reference URL is dead

[Django]

#35286: dead top-down parsing reference URL is dead
-+-
 Reporter:  umair mehmood|Owner:  umair
 Type:   |  mehmood
  Cleanup/optimization   |   Status:  assigned
Component:  Template system  |  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Simon Charette):

 * stage:  Ready for checkin => Accepted

Comment:

 [http://web.archive.org/web/20160304015821/http://effbot.org/zone/simple-
 iterator-parser.htm This archived link] referred to by [https://11l-
 lang.org/archive/simple-top-down-parsing/ what appears to be the author]
 seems to be a better alternative.
-- 
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/0107018e28ee2e75-289bcb36-766f-4ed5-a4f1-2febb22e6894-00%40eu-central-1.amazonses.com.

Re: [Django] #35280: iriencode example incorrect

[Django]

#35280: iriencode example incorrect
-+-
 Reporter:  minusf   |Owner:  Can Huynh
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  1 => 0
 * 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/0107018e28a8b746-06695500-cee7-432a-a421-636112fc86c7-00%40eu-central-1.amazonses.com.

Re: [Django] #34943: Support passing unique constraint names to bulk_create().

[Django]

#34943: Support passing unique constraint names to bulk_create().
-+-
 Reporter:  Alex Vandiver|Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  bulk insert update   | Triage Stage:  Accepted
  upsert |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Sujay):

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

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018e287ff258-e47790ed-4775-4a70-9ccf-a400197ce59a-00%40eu-central-1.amazonses.com.

Re: [Django] #35286: dead top-down parsing reference URL is dead

[Django]

#35286: dead top-down parsing reference URL is dead
-+-
 Reporter:  umair mehmood|Owner:  umair
 Type:   |  mehmood
  Cleanup/optimization   |   Status:  assigned
Component:  Template system  |  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  0|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by umair mehmood):

 * cc: umair mehmood (added)
 * component:  Uncategorized => Template system
 * easy:  0 => 1
 * needs_docs:  0 => 1
 * stage:  Unreviewed => Ready for checkin
 * type:  Uncategorized => Cleanup/optimization

-- 
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/0107018e27f41876-69c78833-509c-4279-90fd-804fb0218b40-00%40eu-central-1.amazonses.com.

[Django] #35286: dead top-down parsing reference URL is dead

[Django]

#35286: dead top-down parsing reference URL is dead
-+---
   Reporter:  umair mehmood  |  Owner:  umair mehmood
   Type:  Uncategorized  | Status:  assigned
  Component:  Uncategorized  |Version:  5.0
   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  |
-+---
 in `django/templates/smartif.py`  this url [effbot-simple-top-down-
 parer](http://effbot.org/zone/simple-top-down-parsing.htm.) is dead. we
 can replace it with https://pdfcoffee.com/simple-top-down-parsing-in-
 python-pt-pdf-free.html found this only similar link
-- 
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/0107018e27f24aca-3d68d513-3483-4a3c-95b6-3bfc2ab386b8-00%40eu-central-1.amazonses.com.