Re: [Django] #26942: support subtests when running tests in parallel

[Django]

#26942: support subtests when running tests in parallel
---+-
 Reporter:  cjerdonek  |Owner:  cjerdonek
 Type:  New feature|   Status:  assigned
Component:  Testing framework  |  Version:  1.9
 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
---+-

Comment (by cjerdonek):

 [https://github.com/django/django/pull/7063/files PR updated.]

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

Re: [Django] #26942: support subtests when running tests in parallel

[Django]

#26942: support subtests when running tests in parallel
---+-
 Reporter:  cjerdonek  |Owner:  cjerdonek
 Type:  New feature|   Status:  assigned
Component:  Testing framework  |  Version:  1.9
 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 cjerdonek):

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

Re: [Django] #24854: Clean up django.db.models.query._values()

[Django]

#24854: Clean up django.db.models.query._values()
-+-
 Reporter:  jarshwah |Owner:  Ian-Foote
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 Ian-Foote):

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

Re: [Django] #24854: Clean up django.db.models.query._values()

[Django]

#24854: Clean up django.db.models.query._values()
-+-
 Reporter:  jarshwah |Owner:  Ian-Foote
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (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
-+-
Changes (by Ian-Foote):

 * owner:   => Ian-Foote
 * status:  new => assigned


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

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

[Django] #27065: Deferred fields not passed to inherited models' __class__.__dict__

[Django]

#27065: Deferred fields not passed to inherited models' __class__.__dict__
--+
 Reporter:  jarekwg   |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.10
 Severity:  Normal|   Keywords:  defer
  |  inherited
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Possibly a regression, possibly me misunderstanding how this should now
 work in 1.10.

 {{{
 class A(models.Model):
 name = models.CharField(max_length=20)
 addy = models.CharField(max_length=200)


 class B(A):
 name2 = models.CharField(max_length=20)
 }}}


 Calling:
 {{{
 b = B.objects.only('name').first()
 }}}
 we expect `name2` and `addy` to get deferred. Calling
 `b.get_deferred_fields()`, we get both these field names returned as
 expected.

 However, inspecting `b.__class__.__dict__`, we see that only the
 `DeferredAttribute` for `name2` is available. To get the one for `addy`,
 we need to consult `b`'s parent. This was not the case in 1.9.

 See my [https://github.com/carljm/django-model-utils/pull/233 PR] to
 django-model-utils for context.

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

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

Re: [Django] #16735: QuerySet.values() should be aliasable

[Django]

#16735: QuerySet.values() should be aliasable
-+-
 Reporter:  alex.latchford@… |Owner:  Ian-Foote
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  queryset, alias, | Triage Stage:  Accepted
  values |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ian-Foote):

 * owner:   => Ian-Foote
 * status:  new => assigned


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

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

Re: [Django] #26539: Using Annotation As Update Parameter Generates Invalid SQL

[Django]

#26539: Using Annotation As Update Parameter Generates Invalid SQL
-+-
 Reporter:  dsanders11   |Owner:  PREM1980
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (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
-+-
Changes (by PREM1980):

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


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

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

Re: [Django] #26908: jsonfield__key__isnull lookup crashes

[Django]

#26908: jsonfield__key__isnull lookup crashes
--+
 Reporter:  sigfrido  |Owner:  PREM1980
 Type:  Bug   |   Status:  assigned
Component:  contrib.postgres  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:  jsonb,postgresql  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by PREM1980):

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


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

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

Re: [Django] #25871: Allow expressions in values() queryset method

[Django]

#25871: Allow expressions in values() queryset method
-+-
 Reporter:  jarshwah |Owner:  Ian-Foote
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  expressions  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ian-Foote):

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

Re: [Django] #27064: Implement RenameIndex in a backwards compatible way

[Django]

#27064: Implement RenameIndex in a backwards compatible way
-+
 Reporter:  MarkusH  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by MarkusH):

 * type:  Uncategorized => New feature


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

[Django] #27064: Implement RenameIndex in a backwards compatible way

[Django]

#27064: Implement RenameIndex in a backwards compatible way
-+
   Reporter:  MarkusH|  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Migrations |Version:  master
   Severity:  Normal |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  1  |Needs tests:  1
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 In order to eventually deprecate `index_together` we need a way to deal
 with old projects that have unnamed indexes. This proves to be a non-
 trivial problem. Andrew and I came up with these things to consider.

 * `RenameIndex(model, new_name, old_name=None, old_fields=None)` where
 exactly one of `old_name` and `old_field` is given (`old_name ^
 old_fields`)
 * If the old_name is given we use `RENAME INDEX` if available
 * Otherwise look at the state and drop existing indexes and create new the
 index with new name
 * On MySQL (or other DBs) that don't support `RENAME INDEX`, provide SQL
 query to look up index name from information_schema by field names and
 pass in to `DROP INDEX`.
 * If more than one index is found while identifying with field names,
 migrations must error out with an `AmbiguityError`
 * If the autodetector finds an old, unnamed index and a new, named one
 matching field signature, issue a `RenameIndex` operation
 * For backwards operations with unnamed old indexes, `RenameIndex` is a
 noop.

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

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

Re: [Django] #25871: Allow expressions in values() queryset method

[Django]

#25871: Allow expressions in values() queryset method
-+-
 Reporter:  jarshwah |Owner:  Ian-Foote
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  expressions  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ian-Foote):

 * owner:  nobody => Ian-Foote
 * status:  new => assigned


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

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

Re: [Django] #27061: Support creating the TEST PostgreSQL database from a custom template

[Django]

#27061: Support creating the TEST PostgreSQL database from a custom template
---+-
 Reporter:  cjerdonek  |Owner:  cjerdonek
 Type:  New feature|   Status:  assigned
Component:  Testing framework  |  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 cjerdonek):

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


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

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

Re: [Django] #26866: Lazy variant of string format

[Django]

#26866: Lazy variant of string format
--+
 Reporter:  lovmat|Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Internationalization  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by lovmat):

 https://github.com/django/django/pull/7087

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

Re: [Django] #27060: Take indexes into account in inspectdb command

[Django]

#27060: Take indexes into account in inspectdb command
-+-
 Reporter:  akki |Owner:  akki
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  db-indexes   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by akki):

 * has_patch:  0 => 1


Comment:

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

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

Re: [Django] #27063: Regex url routing + Localization (prefix_default_language)

[Django]

#27063: Regex url routing + Localization (prefix_default_language)
+--
 Reporter:  keithhackbarth  |Owner:  nobody
 Type:  Uncategorized   |   Status:  new
Component:  Uncategorized   |  Version:  1.10
 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 claudep):

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


Comment:

 May I ask you to create a new ticket for the second issue? It's better
 practice to have one issue per 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/072.80e6dd062ba94d376d2bee9f5d90fa3e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27061: Support creating the TEST PostgreSQL database from a custom template

[Django]

#27061: Support creating the TEST PostgreSQL database from a custom template
---+
 Reporter:  cjerdonek  |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by cjerdonek):

 Cool, thanks! And not at all! :)

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

Re: [Django] #27061: Support creating the TEST PostgreSQL database from a custom template (was: unable to set CHARSET to UTF8 for TEST database setting with PostgreSQL)

[Django]

#27061: Support creating the TEST PostgreSQL database from a custom template
---+
 Reporter:  cjerdonek  |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Testing framework  |  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):

 * type:  Uncategorized => New feature
 * component:  Uncategorized => Testing framework
 * stage:  Unreviewed => Accepted


Comment:

 Hopefully you don't mind the summary change!

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

[Django] #27063: Regex url routing + Localization (prefix_default_language)

[Django]

#27063: Regex url routing + Localization (prefix_default_language)
+
 Reporter:  keithhackbarth  |  Owner:  nobody
 Type:  Uncategorized   | Status:  new
Component:  Uncategorized   |Version:  1.10
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 I'm having two issues on using a regex based url pattern with
 "prefix_default_language" that I was hoping to shed some insight on.

 My url.py file:

 {{{
 urlpatterns += i18n_patterns(
 url(r'^(?P.+-parking)/?$', CityView.as_view()),
 prefix_default_language=False
 )
 }}}

 Issue 1: Regex that also match language prefixs

 If a city that matches my regex but begins with a language prefix, it
 shows a 404.
 For example: "/de-moines-parking" shows a 404. But "de/de-moines-parking"
 returns a 200. Also, cities that don't match one of my enabled languages
 match as well "/boise-parking" for example.

 Issue 2: Stacking

 Also the urls will stack languages, for example, "/de/fr/it/de-moines-
 parking" is loading a successful page instead of a 404.

 Any insight? Is this a bug or am I missing something obvious in my regex?
 Prior to Django 1.10, I used solid_i18n_patterns plugin and did not have
 these issues. I posted on #django-users but no one responded.

 Thanks in advance,

 Keith

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

Re: [Django] #27061: unable to set CHARSET to UTF8 for TEST database setting with PostgreSQL

[Django]

#27061: unable to set CHARSET to UTF8 for TEST database setting with PostgreSQL
---+--
 Reporter:  cjerdonek  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  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 cjerdonek):

 For future reference, [https://www.postgresql.org/docs/current/static/sql-
 createdatabase.html here] is a link to the official PostgreSQL docs, where
 it explains how to use other encodings without changing any installation
 templates. For example--

 > The encoding and locale settings must match those of the template
 database, except when template0 is used as template. ...  `CREATE DATABASE
 music ENCODING 'LATIN1' TEMPLATE template0;` In this example, the TEMPLATE
 template0 clause would only be required if template1's encoding is not
 ISO-8859-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/067.41a19f682ffba286d762afece70765c5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27061: unable to set CHARSET to UTF8 for TEST database setting with PostgreSQL

[Django]

#27061: unable to set CHARSET to UTF8 for TEST database setting with PostgreSQL
---+--
 Reporter:  cjerdonek  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  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 cjerdonek):

 > I still think you should fix your main template encoding.

 There's no need for me to change the PostgreSQL installation or change the
 template encoding because I'm able to run the following CREATE statement
 in my environment setup:

 {{{
 CREATE DATABASE  WITH TEMPLATE template0 ENCODING 'UTF8'
 }}}

 But Django doesn't support this option.

 If Django could clone a test database from an existing database, that
 would be another option.  It already has syntax like the following in
 postgresql's `_clone_test_db()` to clone a test database from another test
 database (from
 
[https://github.com/django/django/blob/d7e0cf04b77c859d895e81ddb7af06a2ccfda5a7/django/db/backends/postgresql/creation.py#L26
 here]:

 {{{
 cursor.execute("CREATE DATABASE %s WITH TEMPLATE %s" % (
 qn(target_database_name), qn(source_database_name)))
 }}}

 So it's almost there.  It's just the bootstrapping part that's missing,
 which we would get for free if the Django code were more DRY.

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

Re: [Django] #27062: Add support for for_update for MSSQL

[Django]

#27062: Add support for for_update for MSSQL
-+-
 Reporter:  denisenkom   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  mssql for_update | Triage Stage:
  database orm   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by denisenkom):

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


Comment:

 Because of this there is no way to add MSSQL support without monkey
 patching entire as_sql method, see: https://github.com/denisenkom/django-
 sqlserver/blob/master/sqlserver/compiler.py#L24

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

[Django] #27062: Add support for for_update for MSSQL

[Django]

#27062: Add support for for_update for MSSQL
-+-
 Reporter:  denisenkom   |  Owner:  nobody
 Type:  New feature  | Status:  new
Component:  Database layer   |Version:  1.10
  (models, ORM)  |   Keywords:  mssql for_update
 Severity:  Normal   |  database orm
 Triage Stage:  Unreviewed   |  Has patch:  1
Easy pickings:  0|  UI/UX:  0
-+-
 Currently SQL generator adds FOR UPDATE clause at the end of the query but
 MSSQL requires it to be after FROM clause.  SQL generator should be
 updated to allow for MSSQL syntax.

 Patch: https://github.com/django/django/pull/5667

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

Re: [Django] #26866: Lazy variant of string format

[Django]

#26866: Lazy variant of string format
--+
 Reporter:  lovmat|Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Internationalization  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by claudep):

 Please make it a pull request so as we can comment on the patch.
 Also please make the `string_concat` move/renaming to another commit, even
 a separate ticket/patch in my opinion.

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

Re: [Django] #27061: unable to set CHARSET to UTF8 for TEST database setting with PostgreSQL

[Django]

#27061: unable to set CHARSET to UTF8 for TEST database setting with PostgreSQL
---+--
 Reporter:  cjerdonek  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  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
---+--
Changes (by claudep):

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


Comment:

 This was already handled in #17207 and #18710 as documentation/wont' fix
 resolutions. I still think you should fix your main template encoding.
 I'm letting the ticket open for another opinion.

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

Re: [Django] #27060: Take indexes into account in inspectdb command

[Django]

#27060: Take indexes into account in inspectdb command
-+-
 Reporter:  akki |Owner:  akki
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  db-indexes   | 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/062.e33bd2960d6ae6774da25765eac019ec%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24112: Inconsistency in TestCase.assertInHTML

[Django]

#24112: Inconsistency in TestCase.assertInHTML
---+
 Reporter:  plumdog|Owner:  adamzap
 Type:  Bug|   Status:  assigned
Component:  Testing framework  |  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 claudep):

 * needs_better_patch:  1 => 0
 * version:  1.7 => master


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

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

Re: [Django] #26866: Lazy variant of string format

[Django]

#26866: Lazy variant of string format
--+
 Reporter:  lovmat|Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Internationalization  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by lovmat):

 I agree django.utils.text is a better place. New attempt here:
 https://github.com/lovmat/django/tree/ticket_26866_format_lazy

 I also encountered an issue with my first implementation of format_lazy -
 it could not handle dictionaries properly since they were forced to text
 immediately. E.g.:

 {{{
 format_lazy('{0[a]}', {'a': 'django'})
 }}}

 Left todo: update docs.

 What do you think?

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

Re: [Django] #26961: Run admin checks if DEBUG is False

[Django]

#26961: Run admin checks if DEBUG is False
--+
 Reporter:  adamchainz|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.admin |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:  checks| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by adamchainz):

 OK I couldn't figure out an easy way around the above confusion. I thing
 it's straight up wrong to run 'check' with `INSTALLED_APPS` overridden. As
 such I've deleted or modified the few tests that did so.

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

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

[Django]

#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  akaariai |Owner:
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-

Comment (by mscott250):

 Hi,

 I'm interested in contributing to Django and have been advised to start
 with some of the 'easy pickings' tasks. I've seen it's been unassigned and
 is still open, is this something I can pick up?

 Cheers,
 Michael

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