date:20190528

Re: [Django] #30479: Autoreloader with StatReloader doesn't track changes in manage.py.

2019-05-28 Thread Django

#30479: Autoreloader with StatReloader doesn't track changes in manage.py.
-+--
 Reporter:  Keryn Knight |Owner:  Tom Forbes
 Type:  Bug  |   Status:  closed
Component:  Utilities|  Version:  2.2
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  autoreload   | Triage Stage:  Accepted
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:"5bf2c87ece216b00a55a6ec0d6c824c9edabf188" 5bf2c87e]:
 {{{
 #!CommitTicketReference repository=""
 revision="5bf2c87ece216b00a55a6ec0d6c824c9edabf188"
 [2.2.x] Fixed #30479 -- Fixed detecting changes in manage.py by
 autoreloader when using StatReloader.

 Regression in c8720e7696ca41f3262d5369365cc1bd72a216ca.

 Backport of b2790f74d4f38c8b297b7c1cef6875d2378f6fa6 from master
 }}}

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

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

Re: [Django] #30479: Autoreloader with StatReloader doesn't track changes in manage.py.

2019-05-28 Thread Django

#30479: Autoreloader with StatReloader doesn't track changes in manage.py.
-+--
 Reporter:  Keryn Knight |Owner:  Tom Forbes
 Type:  Bug  |   Status:  closed
Component:  Utilities|  Version:  2.2
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  autoreload   | 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 ):

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


Comment:

 In [changeset:"b2790f74d4f38c8b297b7c1cef6875d2378f6fa6" b2790f74]:
 {{{
 #!CommitTicketReference repository=""
 revision="b2790f74d4f38c8b297b7c1cef6875d2378f6fa6"
 Fixed #30479 -- Fixed detecting changes in manage.py by autoreloader when
 using StatReloader.

 Regression in c8720e7696ca41f3262d5369365cc1bd72a216ca.
 }}}

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

Re: [Django] #30493: GenericRelation and prefetch_related: wrong caching with cyclic prefetching.

2019-05-28 Thread Django

#30493: GenericRelation and prefetch_related: wrong caching with cyclic
prefetching.
-+-
 Reporter:  Finn Stutzenstein|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  GenericRelation  | Triage Stage:  Accepted
  prefetch_related   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Can Sarıgöl):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/11423 PR]

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

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

Re: [Django] #30315: StringAgg with ordering in subquery generates invalid string_agg() SQL function call

2019-05-28 Thread Django

#30315: StringAgg with ordering in subquery generates invalid string_agg() SQL
function call
-+-
 Reporter:  Reupen Shah  |Owner:  Caio
 |  Ariede
 Type:  Bug  |   Status:  assigned
Component:  contrib.postgres |  Version:  2.2
 Severity:  Release blocker  |   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 felixxm):

 * version:  master => 2.2
 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #30500: Error reporting returns a circular import error on a python formatting error, and does not restart the development server

2019-05-28 Thread Django

#30500: Error reporting returns a circular import error on a python formatting
error, and does not restart the development server
-+-
 Reporter:  Runner15 |Owner:  (none)
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Error reporting  |  Version:  2.2
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  error reporting, | Triage Stage:
  error, circular import |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Keryn Knight):

 * cc: Keryn Knight (added)


Comment:

 Verified the correct error message (`NameError: name 'a' is not defined`)
 turns up under Python 3.5.7, so I guess it is a non-issue overall (fwiw, I
 was verifying under 3.6.2, if Mariusz couldn't reproduce under 3.6.3, it
 got "fixed" upstream in that version).

 (I would argue that the **ergonomics** of Django are harmed by not fixing
 this because it works in the officially-supported point releases, because
 it is more likely to mask problems affecting new users, who are learning
 Django but don't necessarily know the ecosystem well enough to
 install/maintain their own version (eg: by using system python, or
 whatever))

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

Re: [Django] #30517: Add Redis cache backend. (was: refactor BaseMemcachedCache to be a base class for KV engines)

2019-05-28 Thread Django

#30517: Add Redis cache backend.
-+-
 Reporter:  dulmandakh   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Cache system)  |  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  redis cache  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * keywords:  redis => redis cache
 * status:  new => closed
 * type:  Cleanup/optimization => New feature
 * resolution:   => wontfix


Comment:

 Thanks for this proposition. There already exists [https://django-redis-
 cache.readthedocs.io/en/latest/index.html django-redis-cache] 3rd party
 package with a Redis cache backend for Django. I don't think that we
 should move it into core. You can try to start a discussion on the
 [https://docs.djangoproject.com/en/2.2/internals/mailing-lists/#django-
 developers-mailing-list django-developers mailing list] if you feel that
 we can reach a different consensus.

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

Re: [Django] #30491: Document changing primary key behavior in "How Django knows to UPDATE vs. INSERT" section.

2019-05-28 Thread Django

#30491: Document changing primary key behavior in "How Django knows to UPDATE 
vs.
INSERT" section.
--+
 Reporter:  Brad  |Owner:  Brad
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  2.2
 Severity:  Normal|   Resolution:  fixed
 Keywords:  save  | 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 ):

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


Comment:

 In [changeset:"67b6cb7723b2765cb776bd59d5603e3e63eefc2e" 67b6cb77]:
 {{{
 #!CommitTicketReference repository=""
 revision="67b6cb7723b2765cb776bd59d5603e3e63eefc2e"
 Fixed #30491 -- Clarified when save() on object with pk executes INSERT.
 }}}

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

[Django] #30519: Add sanity checks to Django RasterField deserialization for rasters that are not fully managed through Django.

2019-05-28 Thread Django

#30519: Add sanity checks to Django RasterField deserialization for rasters that
are not fully managed through Django.
+
Reporter: Daniel Wiesmann | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: GIS |Version: master
Severity: Normal| Keywords: raster
Triage Stage: Unreviewed| Has patch: 0
Needs documentation: 0 |Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
+
When using the RasterField for raster columns in PostGIS that are not
fully managed by Django, the raster table could be of a type that is not
supported by the GDALRaster. Examples are out-of-db rasters, or rasters
that have an unsupported pixeltype (single bit rasters, 2 or 4 bit
rasters).

A paragraph about this could be added to the documentation, and some
sanity checks could be added to the raster deserialization here:

https://github.com/django/django/blob/master/django/contrib/gis/db/backends/postgis/pgraster.py

This ticket is related to https://code.djangoproject.com/ticket/30489 and
https://github.com/django/django/pull/11381

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

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

Re: [Django] #30315: StringAgg with ordering in subquery generates invalid string_agg() SQL function call

2019-05-28 Thread Django

#30315: StringAgg with ordering in subquery generates invalid string_agg() SQL
function call
-+-
 Reporter:  Reupen Shah  |Owner:  Caio
 |  Ariede
 Type:  Bug  |   Status:  closed
Component:  contrib.postgres |  Version:  2.2
 Severity:  Release blocker  |   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:"1172f078eb04e0125413b061d3ccf7a283993b89" 1172f078]:
 {{{
 #!CommitTicketReference repository=""
 revision="1172f078eb04e0125413b061d3ccf7a283993b89"
 [2.2.x] Fixed #30315 -- Fixed crash of ArrayAgg and StringAgg with
 ordering when used in Subquery.

 Backport of a3f91891d2c7f4bdc33f48ae70820ef6f36da26e from master.
 }}}

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

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

Re: [Django] #30518: Multiple Count annotation with filter doesn't work properly. (was: Multiple Count annotation with filter doesn't work properly (at least if related modelas has same named fileds))

2019-05-28 Thread Django

#30518: Multiple Count annotation with filter doesn't work properly.
-+-
 Reporter:  farin|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  annotate | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * status:  new => closed
 * version:  2.2 => master
 * resolution:   => duplicate


Comment:

 Duplicate of #10060 (see
 [https://docs.djangoproject.com/en/stable/topics/db/aggregation
 /#combining-multiple-aggregations documentation]).

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

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

Re: [Django] #30491: Document changing primary key behavior in "How Django knows to UPDATE vs. INSERT" section.

2019-05-28 Thread Django

#30491: Document changing primary key behavior in "How Django knows to UPDATE 
vs.
INSERT" section.
--+
 Reporter:  Brad  |Owner:  Brad
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  2.2
 Severity:  Normal|   Resolution:  fixed
 Keywords:  save  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Mariusz Felisiak ):

 In [changeset:"0f0d1cd7722238158011c7717d410fae37513ceb" 0f0d1cd]:
 {{{
 #!CommitTicketReference repository=""
 revision="0f0d1cd7722238158011c7717d410fae37513ceb"
 [2.2.x] Fixed #30491 -- Clarified when save() on object with pk executes
 INSERT.

 Backport of 67b6cb7723b2765cb776bd59d5603e3e63eefc2e from master
 }}}

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

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

Re: [Django] #30519: Add sanity checks to Django RasterField deserialization for rasters that are not fully managed through Django.

2019-05-28 Thread Django

#30519: Add sanity checks to Django RasterField deserialization for rasters that
are not fully managed through Django.
--+
 Reporter:  Daniel Wiesmann   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  GIS   |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  raster| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Claude Paroz):

 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #30315: StringAgg with ordering in subquery generates invalid string_agg() SQL function call

2019-05-28 Thread Django

#30315: StringAgg with ordering in subquery generates invalid string_agg() SQL
function call
-+-
 Reporter:  Reupen Shah  |Owner:  Caio
 |  Ariede
 Type:  Bug  |   Status:  closed
Component:  contrib.postgres |  Version:  2.2
 Severity:  Release blocker  |   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:"a3f91891d2c7f4bdc33f48ae70820ef6f36da26e" a3f91891]:
 {{{
 #!CommitTicketReference repository=""
 revision="a3f91891d2c7f4bdc33f48ae70820ef6f36da26e"
 Fixed #30315 -- Fixed crash of ArrayAgg and StringAgg with ordering when
 used in Subquery.
 }}}

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

[Django] #30518: Multiple Count annotation with filter doesn't work properly (at least if related modelas has same named fileds)

2019-05-28 Thread Django

#30518: Multiple Count annotation with filter doesn't work properly (at least if
related modelas has same named fileds)
-+-
   Reporter:  farin  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Database   |Version:  2.2
  layer (models, ORM)|
   Severity:  Normal |   Keywords:  annotate
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Lets have following models

 {{{
 class User(models.Model):
pass

 class Subscription(models.Model):
 user = models.ForeignKey(User, models.CASCADE)
 valid_to = models.DateTimeField()

 class SubscriptionToAuthor(models.Model):
 user = models.ForeignKey(User, models.CASCADE)
 valid_to = models.DateTimeField()
 }}}

 then annotate on only one related model works fine

 {{{
 # this is ok

 User.objects.annotate(
 subscribed_authors=Count('subscriptiontoauthor',
 filter=Q(subscriptiontoauthor__valid_to__gt=now))
 )
 }}}

 or
 {{{
 # this is ok

 User.objects.annotate(
 subscribed_newspapers=Count('subscription',
 filter=Q(subscription__valid_to__gt=now))
 )
 }}}

 but Count returns incorrect (too big) count numbers when both annotations
 are used on single query set

 {{{
 # wrong result

 User.objects.annotate(
   subscribed_authors=Count('subscriptiontoauthor',
 filter=Q(subscriptiontoauthor__valid_to__gt=now))
 ).annotate(
   subscribed_newspapers=Count('subscription',
 filter=Q(subscription__valid_to__gt=now))
 )
 }}}

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

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

[Django] #30524: on_delete doesn't work properly with MySql.

2019-05-28 Thread Django

#30524: on_delete doesn't work properly with MySql.
-+-
   Reporter: |  Owner:  nobody
  dheeraj135 |
   Type:  Bug| Status:  new
  Component: |Version:  2.2
  Uncategorized  |   Keywords:  Foreign Key,
   Severity:  Normal |  indexes
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Model:

 {{{
 class Attempt(models.Model):
 student = models.ForeignKey(Student, models.CASCADE,
 related_name='quiz_attempts',null=False)
 quiz =
 models.ForeignKey(Quiz,on_delete=models.CASCADE,related_name='quiz_attempts')
 score = models.FloatField()
 over = models.BooleanField(default=False)
 date = models.DateTimeField(auto_now_add=True)
 currquestion =
 models.ForeignKey(Question,null=True,default=None,on_delete=models.SET_NULL)

 class Meta:
 indexes = [
 models.Index(fields=['student']),
 models.Index(fields=['quiz']),
 ]

 }}}
 Table created in MySql:

 {{{
 CREATE TABLE `classroom_attempt` (
   `id` int(11) NOT NULL AUTO_INCREMENT,
   `score` double NOT NULL,
   `over` tinyint(1) NOT NULL,
   `date` datetime(6) NOT NULL,
   `currquestion_id` int(11) DEFAULT NULL,
   `quiz_id` int(11) NOT NULL,
   `student_id` int(11) NOT NULL,
   PRIMARY KEY (`id`),
   KEY `classroom_a_student_1a21bc_idx` (`student_id`),
   KEY `classroom_a_quiz_id_eef64a_idx` (`quiz_id`),
   KEY `classroom_attempt_currquestion_id_545301ef_fk_classroom`
 (`currquestion_id`),
   CONSTRAINT `classroom_attempt_currquestion_id_545301ef_fk_classroom`
 FOREIGN KEY (`currquestion_id`) REFERENCES `classroom_question` (`id`),
   CONSTRAINT `classroom_attempt_quiz_id_e227b203_fk_classroom_quiz_id`
 FOREIGN KEY (`quiz_id`) REFERENCES `classroom_quiz` (`id`),
   CONSTRAINT `classroom_attempt_student_id_a4dc81cd_fk_classroom` FOREIGN
 KEY (`student_id`) REFERENCES `classroom_student` (`user_id`)
 ) ENGINE=InnoDB DEFAULT CHARSET=latin1 |
 +---+-
 }}}

 As you can notice, indexes and models.CASCADE is not applied.

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

Re: [Django] #30457: on_commit should be triggered in a TestCase

2019-05-28 Thread Django

#30457: on_commit should be triggered in a TestCase
+
 Reporter:  Bernhard Mäder  |Owner:  nobody
 Type:  New feature |   Status:  new
Component:  Documentation   |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  on_commit TestCase  | 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 (Chainz) Johnson):

 I've also tested this with unittest.mock.patch on transaction.on_commit,
 checking it was invoked enough times, then invoking the collected
 functions in the tests.

 A helper in django.test.utils would be cool.

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

Re: [Django] #30524: on_delete doesn't work properly with MySql.

2019-05-28 Thread Django

#30524: on_delete doesn't work properly with MySql.
---+--
 Reporter:  dheeraj135 |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Uncategorized  |  Version:  2.2
 Severity:  Normal |   Resolution:  invalid
 Keywords:  Foreign Key| Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Simon Charette):

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


Comment:

 Django doesn't support database level foreign keys yet, this is tracked in
 #11964.

 The `models.CASCADE` value implements cascade deletion at the
 application/Python level in order to support signals.

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

[Django] #30523: StatReloader does not update file times if notify_file_changed() is triggered

2019-05-28 Thread Django

#30523: StatReloader does not update file times if notify_file_changed() is
triggered
-+
   Reporter:  Tom Forbes |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Uncategorized  |Version:  2.2
   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  |
-+
 If notify_file_changed is triggered then the files mtime is not updated.
 This can cause notify_file_changed() to be triggered many times if a
 translation is changed.

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

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

Re: [Django] #30523: StatReloader does not update file times if notify_file_changed() is triggered

2019-05-28 Thread Django

#30523: StatReloader does not update file times if notify_file_changed() is
triggered
+--
 Reporter:  Tom Forbes  |Owner:  Tom Forbes
 Type:  Bug |   Status:  assigned
Component:  Utilities   |  Version:  2.2
 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 Tom Forbes):

 * status:  new => assigned
 * component:  Uncategorized => Utilities
 * owner:  nobody => Tom Forbes
 * has_patch:  0 => 1
 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


Comment:

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

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

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

Re: [Django] #30524: on_delete doesn't work properly with MySql.

2019-05-28 Thread Django

#30524: on_delete doesn't work properly with MySql.
---+--
 Reporter:  dheeraj135 |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  2.2
 Severity:  Normal |   Resolution:
 Keywords:  Foreign Key| Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by dheeraj135):

 * keywords:  Foreign Key, indexes => Foreign Key


Old description:

> Model:
>
> {{{
> class Attempt(models.Model):
> student = models.ForeignKey(Student, models.CASCADE,
> related_name='quiz_attempts',null=False)
> quiz =
> models.ForeignKey(Quiz,on_delete=models.CASCADE,related_name='quiz_attempts')
> score = models.FloatField()
> over = models.BooleanField(default=False)
> date = models.DateTimeField(auto_now_add=True)
> currquestion =
> models.ForeignKey(Question,null=True,default=None,on_delete=models.SET_NULL)
>
> class Meta:
> indexes = [
> models.Index(fields=['student']),
> models.Index(fields=['quiz']),
> ]
>
> }}}
> Table created in MySql:
>
> {{{
> CREATE TABLE `classroom_attempt` (
>   `id` int(11) NOT NULL AUTO_INCREMENT,
>   `score` double NOT NULL,
>   `over` tinyint(1) NOT NULL,
>   `date` datetime(6) NOT NULL,
>   `currquestion_id` int(11) DEFAULT NULL,
>   `quiz_id` int(11) NOT NULL,
>   `student_id` int(11) NOT NULL,
>   PRIMARY KEY (`id`),
>   KEY `classroom_a_student_1a21bc_idx` (`student_id`),
>   KEY `classroom_a_quiz_id_eef64a_idx` (`quiz_id`),
>   KEY `classroom_attempt_currquestion_id_545301ef_fk_classroom`
> (`currquestion_id`),
>   CONSTRAINT `classroom_attempt_currquestion_id_545301ef_fk_classroom`
> FOREIGN KEY (`currquestion_id`) REFERENCES `classroom_question` (`id`),
>   CONSTRAINT `classroom_attempt_quiz_id_e227b203_fk_classroom_quiz_id`
> FOREIGN KEY (`quiz_id`) REFERENCES `classroom_quiz` (`id`),
>   CONSTRAINT `classroom_attempt_student_id_a4dc81cd_fk_classroom` FOREIGN
> KEY (`student_id`) REFERENCES `classroom_student` (`user_id`)
> ) ENGINE=InnoDB DEFAULT CHARSET=latin1 |
> +---+-
> }}}
>
> As you can notice, indexes and models.CASCADE is not applied.

New description:

 Model:

 {{{
 class Attempt(models.Model):
 student = models.ForeignKey(Student, models.CASCADE,
 related_name='quiz_attempts',null=False)
 quiz =
 models.ForeignKey(Quiz,on_delete=models.CASCADE,related_name='quiz_attempts')
 score = models.FloatField()
 over = models.BooleanField(default=False)
 date = models.DateTimeField(auto_now_add=True)
 currquestion =
 models.ForeignKey(Question,null=True,default=None,on_delete=models.SET_NULL)

 class Meta:
 indexes = [
 models.Index(fields=['student']),
 models.Index(fields=['quiz']),
 ]

 }}}
 Table created in MySql:

 {{{
 CREATE TABLE `classroom_attempt` (
   `id` int(11) NOT NULL AUTO_INCREMENT,
   `score` double NOT NULL,
   `over` tinyint(1) NOT NULL,
   `date` datetime(6) NOT NULL,
   `currquestion_id` int(11) DEFAULT NULL,
   `quiz_id` int(11) NOT NULL,
   `student_id` int(11) NOT NULL,
   PRIMARY KEY (`id`),
   KEY `classroom_a_student_1a21bc_idx` (`student_id`),
   KEY `classroom_a_quiz_id_eef64a_idx` (`quiz_id`),
   KEY `classroom_attempt_currquestion_id_545301ef_fk_classroom`
 (`currquestion_id`),
   CONSTRAINT `classroom_attempt_currquestion_id_545301ef_fk_classroom`
 FOREIGN KEY (`currquestion_id`) REFERENCES `classroom_question` (`id`),
   CONSTRAINT `classroom_attempt_quiz_id_e227b203_fk_classroom_quiz_id`
 FOREIGN KEY (`quiz_id`) REFERENCES `classroom_quiz` (`id`),
   CONSTRAINT `classroom_attempt_student_id_a4dc81cd_fk_classroom` FOREIGN
 KEY (`student_id`) REFERENCES `classroom_student` (`user_id`)
 ) ENGINE=InnoDB DEFAULT CHARSET=latin1 |
 +---+-
 }}}

 As you can notice models.CASCADE is not applied.

--

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

Re: [Django] #30521: Default error webpages are not correctly-formed html pages. (was: Default error webpages are not correctly-formed html pages)

2019-05-28 Thread Django

#30521: Default error webpages are not correctly-formed html pages.
--+
Reporter: Ruben Garcia |Owner: (none)
Type: Cleanup/optimization | Status: new
Component: Error reporting | Version: master
Severity: Normal| Resolution:
Keywords:| Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 |UI/UX: 0
--+
Changes (by felixxm):

* ui_ux: 1 => 0
* version: 2.2 => master
* stage: Unreviewed => Accepted

Comment:

Thanks for the report. I'm not sure if we should complicate all default
error pages. It is [https://docs.djangoproject.com/en/stable/ref/views
/#error-views documented] that by default error views produce a very
simple messages and it is also still recommended as good practice to
provide custom templates in order to present pretty error pages to the
user. You can also
[https://docs.djangoproject.com/en/stable/topics/http/views/#customizing-
error-views customize error views]. To sum up default error pages are just
a fallback, but OK we can accept this as a simple cleanup.

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

Re: [Django] #30526: migration to UUID id field doesn't properly convert integers (SQLite)

2019-05-28 Thread Django

#30526: migration to UUID id field doesn't properly convert integers (SQLite)
--+--
 Reporter:  Martin Baker  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Migrations|  Version:  2.2
 Severity:  Normal|   Resolution:
 Keywords:  UUID  | Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Description changed by Martin Baker:

Old description:

> This may be present in other DBs, but I've noticed it with SQLite under
> Django 2.2.1.
>
> Steps to reproduce:
>
> 1. Start a model with an implicit integer id, and create and run the
> migration:
>
> {{{#!python
> from django.db import models
>
> class Something(models.Model):
> name = models.CharField(max_length=32)
> }}}
>
> 2. Then create one instance via the shell (`python manage.py shell`):
>
> {{{#!python
> from uuidbug.models import Something
> s = Something(name="One")
> s.save()
> }}}
>
> In the DB it looks like this (can use `python manage.py dbshell`):
> {{{
> sqlite> .headers on
> sqlite> select * from uuiditem_something;
> name|id
> One|1
> }}}
>
> 3. Edit the model to use UUIDs:
>
> {{{#!python
> import uuid
>
> from django.db import models
>
> class Something(models.Model):
> name = models.CharField(max_length=32)
> id = models.UUIDField(primary_key=True, default=uuid.uuid4,
> editable=False)
> }}}
>
> 4. After creating and running the migration, add another instance:
>
> {{{#!python
> from uuidbug.models import Something
> s = Something(name="After UUID-ization")
> s.save()
> }}}
>
> DB now looks like this:
>
> {{{
> sqlite> select * from uuiditem_something;
> name|id
> One|1
> After UUID-ization|693e1942d7d142289bb9fb3664f2c11a
> }}}
>
> Note that the id for the first instance has not been converted to a UUID
> properly. If you try to access the objects, you get an error:
>
> {{{#!python
> >>> Something.objects.all()
> Traceback (most recent call last):
>   File "", line 1, in 
>   File "/Users/martin/Connery/opencc-backend/venv/lib/python3.7/site-
> packages/django/db/models/manager.py", line 82, in manager_method
> return getattr(self.get_queryset(), name)(*args, **kwargs)
>   File "/Users/martin/Connery/opencc-backend/venv/lib/python3.7/site-
> packages/django/db/models/query.py", line 653, in first
> for obj in (self if self.ordered else self.order_by('pk'))[:1]:
>   File "/Users/martin/Connery/opencc-backend/venv/lib/python3.7/site-
> packages/django/db/models/query.py", line 274, in __iter__
> self._fetch_all()
>   File "/Users/martin/Connery/opencc-backend/venv/lib/python3.7/site-
> packages/django/db/models/query.py", line 1242, in _fetch_all
> self._result_cache = list(self._iterable_class(self))
>   File "/Users/martin/Connery/opencc-backend/venv/lib/python3.7/site-
> packages/django/db/models/query.py", line 72, in __iter__
> for row in compiler.results_iter(results):
>   File "/Users/martin/Connery/opencc-backend/venv/lib/python3.7/site-
> packages/django/db/models/sql/compiler.py", line 1044, in
> apply_converters
> value = converter(value, expression, connection)
>   File "/Users/martin/Connery/opencc-backend/venv/lib/python3.7/site-
> packages/django/db/backends/sqlite3/operations.py", line 294, in
> convert_uuidfield_value
> value = uuid.UUID(value)
>   File
> "/usr/local/Cellar/python/3.7.3/Frameworks/Python.framework/Versions/3.7/lib/python3.7/uuid.py",
> line 160, in __init__
> raise ValueError('badly formed hexadecimal UUID string')
> ValueError: badly formed hexadecimal UUID string
> }}}

New description:

 This may be present in other DBs, but I've noticed it with SQLite under
 Django 2.2.1.

 Steps to reproduce:

 1. Start a model with an implicit integer id, and create and run the
 migration:

 {{{#!python
 from django.db import models

 class Something(models.Model):
 name = models.CharField(max_length=32)
 }}}

 2. Then create one instance via the shell (`python manage.py shell`):

 {{{#!python
 from uuidbug.models import Something
 s = Something(name="One")
 s.save()
 }}}

 In the DB it looks like this (can use `python manage.py dbshell`):
 {{{
 sqlite> .headers on
 sqlite> select * from uuiditem_something;
 name|id
 One|1
 }}}

 3. Edit the model to use UUIDs:

 {{{#!python
 import uuid

 from django.db import models

 class Something(models.Model):
 name = models.CharField(max_length=32)
 id = models.UUIDField(primary_key=True, default=uuid.uuid4,
 editable=False)
 }}}

 4. After creating and running the migration, add another instance:

 {{{#!python
 from uuidbug.models import Something
 s = Something(name="After UUID-ization")
 s.save()

[Django] #30525: --skip-checks management command needs backported

2019-05-28 Thread Django

#30525: --skip-checks management command needs backported
-+-
   Reporter:  Doug   |  Owner:  nobody
  Fultz  |
   Type: | Status:  new
  Uncategorized  |
  Component:  Core   |Version:  1.11
  (Management commands)  |
   Severity:  Normal |   Keywords:  skip-checks
   Triage Stage: |  Has patch:  1
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 This commit is missing from the 1.11.x branch.  Please backport it.

 Commit:
 
https://github.com/django/django/commit/6866c91b638de5368c18713fa851bfe56253ea55
 1.11.x Branch:
 
https://github.com/django/django/blob/stable/1.11.x/django/core/management/base.py#L326

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

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

Re: [Django] #30525: --skip-checks management command needs backported

2019-05-28 Thread Django

#30525: --skip-checks management command needs backported
-+-
 Reporter:  Doug Fultz   |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Core (Management |  Version:  1.11
  commands)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  skip-checks  | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Simon Charette):

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


Comment:

 The `--skip-checks` is a new feature that is planned for
 
[https://github.com/django/django/commit/6866c91b638de5368c18713fa851bfe56253ea55
 #diff-b5ea25a58e9c8adf1a328182844020caR1729 Django 3.0] and
 [https://docs.djangoproject.com/en/2.2/internals/release-process
 /#supported-versions won't be backported to the 1.11 which is currently
 only receiving security and data losses bug fixing patches].

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

[Django] #30526: migration to UUID id field doesn't properly convert integers (SQLite)

2019-05-28 Thread Django

#30526: migration to UUID id field doesn't properly convert integers (SQLite)
+
   Reporter:  Martin Baker  |  Owner:  nobody
   Type:  Bug   | Status:  new
  Component:  Migrations|Version:  2.2
   Severity:  Normal|   Keywords:  UUID
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 This may be present in other DBs, but I've noticed it with SQLite under
 Django 2.2.1.

 Steps to reproduce:

 1. Start a model with an implicit integer id, and create and run the
 migration:

 {{{#!python
 from django.db import models

 class Something(models.Model):
 name = models.CharField(max_length=32)
 }}}

 2. Then create one instance via the shell (`python manage.py shell`):

 {{{#!python
 from uuidbug.models import Something
 s = Something(name="One")
 s.save()
 }}}

 In the DB it looks like this (can use `python manage.py dbshell`):
 {{{
 sqlite> .headers on
 sqlite> select * from uuiditem_something;
 name|id
 One|1
 }}}

 3. Edit the model to use UUIDs:

 {{{#!python
 import uuid

 from django.db import models

 class Something(models.Model):
 name = models.CharField(max_length=32)
 id = models.UUIDField(primary_key=True, default=uuid.uuid4,
 editable=False)
 }}}

 4. After creating and running the migration, add another instance:

 {{{#!python
 from uuidbug.models import Something
 s = Something(name="After UUID-ization")
 s.save()
 }}}

 DB now looks like this:

 {{{
 sqlite> select * from uuiditem_something;
 name|id
 One|1
 After UUID-ization|693e1942d7d142289bb9fb3664f2c11a
 }}}

 Note that the id for the first instance has not been converted to a UUID
 properly. If you try to access the objects, you get an error:

 {{{#!python
 >>> Something.objects.all()
 Traceback (most recent call last):
   File "", line 1, in 
   File "/Users/martin/Connery/opencc-backend/venv/lib/python3.7/site-
 packages/django/db/models/manager.py", line 82, in manager_method
 return getattr(self.get_queryset(), name)(*args, **kwargs)
   File "/Users/martin/Connery/opencc-backend/venv/lib/python3.7/site-
 packages/django/db/models/query.py", line 653, in first
 for obj in (self if self.ordered else self.order_by('pk'))[:1]:
   File "/Users/martin/Connery/opencc-backend/venv/lib/python3.7/site-
 packages/django/db/models/query.py", line 274, in __iter__
 self._fetch_all()
   File "/Users/martin/Connery/opencc-backend/venv/lib/python3.7/site-
 packages/django/db/models/query.py", line 1242, in _fetch_all
 self._result_cache = list(self._iterable_class(self))
   File "/Users/martin/Connery/opencc-backend/venv/lib/python3.7/site-
 packages/django/db/models/query.py", line 72, in __iter__
 for row in compiler.results_iter(results):
   File "/Users/martin/Connery/opencc-backend/venv/lib/python3.7/site-
 packages/django/db/models/sql/compiler.py", line 1044, in apply_converters
 value = converter(value, expression, connection)
   File "/Users/martin/Connery/opencc-backend/venv/lib/python3.7/site-
 packages/django/db/backends/sqlite3/operations.py", line 294, in
 convert_uuidfield_value
 value = uuid.UUID(value)
   File
 
"/usr/local/Cellar/python/3.7.3/Frameworks/Python.framework/Versions/3.7/lib/python3.7/uuid.py",
 line 160, in __init__
 raise ValueError('badly formed hexadecimal UUID string')
 ValueError: badly formed hexadecimal UUID string
 }}}

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

Re: [Django] #30522: How to use Custom install Sqlite3 in Django. (was: How to use Custom install Sqlite3 in Django)

2019-05-28 Thread Django

#30522: How to use Custom install Sqlite3 in Django.
-+-
 Reporter:  Ananthraj|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  sqlite   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * status:  new => closed
 * resolution:   => invalid
 * version:  2.2 => master
 * keywords:   => sqlite
 * type:  Uncategorized => Bug


Comment:

 Thanks for the report, but I agree that it is probably some issue with
 your custom SQLite installation. Closing per
 TicketClosingReasons/UseSupportChannels.

 Refs #28376.

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

Re: [Django] #28053: Allow fields to specify arbitrary indexes via db_index=Index()

2019-05-28 Thread Django

#28053: Allow fields to specify arbitrary indexes via db_index=Index()
-+-
 Reporter:  Marc Tamlyn  |Owner:  Can
 |  Sarıgöl
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  indexes migrations   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Can Sarıgöl):

 * needs_docs:  1 => 0
 * needs_tests:  1 => 0


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

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

Re: [Django] #30520: ModelForm with field without label crashes when used in InlineModelAdmin.

2019-05-28 Thread Django

#30520: ModelForm with field without label crashes when used in 
InlineModelAdmin.
-+
 Reporter:  George Tantiras  |Owner:  Jones
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+
Changes (by Jones):

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


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

Re: [Django] #28935: Template error raised in an {% extends %} child template shows incorrect source location on debug page

2019-05-28 Thread Django

#28935: Template error raised in an {% extends %} child template shows incorrect
source location on debug page
-+--
 Reporter:  Matt Westcott|Owner:  Ankur Jain
 Type:  Bug  |   Status:  assigned
Component:  Template system  |  Version:  2.0
 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 pascal chambon):

 * cc: pascal chambon (added)


Comment:

 Error confirmed on Django2.2.1, it makes the debug page much less helpful
 in case of TemplateError, since most websites inherit their templates from
 some kind of "base.html" skeleton.

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

[Django] #30521: Default error webpages are not correctly-formed html pages

2019-05-28 Thread Django

#30521: Default error webpages are not correctly-formed html pages
+
   Reporter:  Ruben Garcia  |  Owner:  (none)
   Type:  Cleanup/optimization  | Status:  new
  Component:  Error reporting   |Version:  2.2
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  1
  UI/UX:  1 |
+
 The default page served for the 404 error in "DEBUG=False" mode is (django
 2.2.1):
 Not FoundThe requested resource was not found on this
 server.

 I would expect that by default, a full webpage is sent to the user, thus:
 
 
 Not FoundThe requested resource was not found on this
 server.
 
 

 In "DEBUG=True" mode, the webpage served is correct html:
 
 
 ...
 

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

Re: [Django] #30520: ModelForm with field without label crashes when used in InlineModelAdmin. (was: Extra field of ModelForm without label, raises error in InlineModelAdmin)

2019-05-28 Thread Django

#30520: ModelForm with field without label crashes when used in 
InlineModelAdmin.
-+
 Reporter:  George Tantiras  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+
Changes (by felixxm):

 * component:  Uncategorized => contrib.admin
 * version:  2.2 => master
 * easy:  0 => 1
 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


Comment:

 Thanks for the report. I think that passing an empty form to the
 `label_for_field()` should fix this issue, e.g.
 {{{
 diff --git a/django/contrib/admin/helpers.py
 b/django/contrib/admin/helpers.py
 index 83719f4346..aa07581391 100644
 --- a/django/contrib/admin/helpers.py
 +++ b/django/contrib/admin/helpers.py
 @@ -289,7 +289,7 @@ class InlineAdminFormSet:
  form_field = empty_form.fields[field_name]
  label = form_field.label
  if label is None:
 -label = label_for_field(field_name, self.opts.model,
 self.opts)
 +label = label_for_field(field_name, self.opts.model,
 self.opts, form=empty_form)
  yield {
  'name': field_name,
  'label': label,
 }}}

 Reproduced at 67b6cb7723b2765cb776bd59d5603e3e63eefc2e.

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

Re: [Django] #28944: Chaining values()/values_list() after QuerySet.select_for_update(of=()) crashes

2019-05-28 Thread Django

#28944: Chaining values()/values_list() after QuerySet.select_for_update(of=())
crashes
-+-
 Reporter:  Thierry Bastian  |Owner:  Can
 |  Sarıgöl
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  2.0
  (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 Can Sarıgöl):

 * status:  new => assigned
 * needs_better_patch:  1 => 0
 * cc: Can Sarıgöl (added)
 * owner:  nobody => Can Sarıgöl


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

Re: [Django] #28944: Chaining values()/values_list() after QuerySet.select_for_update(of=()) crashes

2019-05-28 Thread Django

#28944: Chaining values()/values_list() after QuerySet.select_for_update(of=())
crashes
-+-
 Reporter:  Thierry Bastian  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 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 Can Sarıgöl):

 [https://github.com/django/django/pull/11387 PR]

 a different approach

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

Re: [Django] #28567: Unclear documentation for 'next' parameter of set_language view

2019-05-28 Thread Django

#28567: Unclear documentation for 'next' parameter of set_language view
--+
 Reporter:  George Tantiras   |Owner:  (none)
 Type:  Bug   |   Status:  closed
Component:  Internationalization  |  Version:  1.11
 Severity:  Normal|   Resolution:  invalid
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by George Tantiras):

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


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

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

Re: [Django] #26192: Cannot order query by constant value on PostgreSQL

2019-05-28 Thread Django

#26192: Cannot order query by constant value on PostgreSQL
-+-
 Reporter:  Sven R. Kunze|Owner:  (none)
 Type:  Bug  |   Status:  new
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 Can Sarıgöl):

 * owner:  Can Sarıgöl => (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 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.55098f4fead13bcfa4792bbca7ca8379%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #30520: Extra field of ModelForm without label, raises error in InlineModelAdmin

2019-05-28 Thread Django

#30520: Extra field of ModelForm without label, raises error in InlineModelAdmin
---+
   Reporter:  George Tantiras  |  Owner:  nobody
   Type:  Uncategorized| Status:  new
  Component:  Uncategorized|Version:  2.2
   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|
---+
 As per [https://stackoverflow.com/questions/56156039/extra-field-of-
 modelform-without-label-does-not-render-in-inlinemodeladmin this] and
 [https://stackoverflow.com/questions/54511865/django-extra-fields-in-
 custommodelform-is-giving-unable-to-lookuup-error-i that] S.O. issues,
 although a ModelForm with an extra field which has no label works at the
 model's change view, it raises an error when the same ModelForm is used
 for an inline:

 models.py:
 {{{#!python
 class Parent(models.Model):
 pass


 class Child(models.Model):
 parent = models.ForeignKey(Parent, on_delete=models.PROTECT)
 }}}

 forms.py:
 {{{#!python
 class ChildForm(forms.ModelForm):
 extra_field = forms.CharField()

 class Meta:
 model = Child
 fields = '__all__'
 }}}
 admin.py:
 {{{#!python
 @admin.register(models.Child)
 class ChildAdmin(admin.ModelAdmin):
 '''The ModelForm renders as expected'''
 form = forms.ChildForm


 class ChildInline(admin.TabularInline):
 '''Here the ModelForm without a label in the extra field, will raise
 error'''
 model = models.Child
 form = forms.ChildForm


 @admin.register(models.Parent)
 class ParentAdmin(admin.ModelAdmin):
 inlines = (ChildInline,)
 }}}
 {{{#!python
  File "/home/venv/lined/lib/python3.7/site-
 packages/django/contrib/admin/utils.py", line 364, in label_for_field
  raise AttributeError(message)
  AttributeError: Unable to lookup 'extra_field' on Child or
 ChildInline
 }}}
 Full error message:
 https://pastebin.com/89MUGchf

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

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

Re: [Django] #28567: Unclear documentation for 'next' parameter of set_language view

2019-05-28 Thread Django

#28567: Unclear documentation for 'next' parameter of set_language view
--+
 Reporter:  George Tantiras   |Owner:  (none)
 Type:  Bug   |   Status:  new
Component:  Internationalization  |  Version:  1.11
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by George Tantiras):

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


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

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

Re: [Django] #26192: Cannot order query by constant value on PostgreSQL

2019-05-28 Thread Django

#26192: Cannot order query by constant value on PostgreSQL
-+-
 Reporter:  Sven R. Kunze|Owner:  (none)
 Type:  Bug  |   Status:  new
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 Can Sarıgöl):

 * cc: Can Sarıgöl (added)


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

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

Re: [Django] #30493: GenericRelation and prefetch_related: wrong caching with cyclic prefetching.

2019-05-28 Thread Django

#30493: GenericRelation and prefetch_related: wrong caching with cyclic
prefetching.
-+-
 Reporter:  Finn Stutzenstein|Owner:  Can
 |  Sarıgöl
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  GenericRelation  | Triage Stage:  Accepted
  prefetch_related   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Can Sarıgöl):

 * status:  new => assigned
 * owner:  nobody => Can Sarıgöl


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

Re: [Django] #30520: ModelForm with field without label crashes when used in InlineModelAdmin.

2019-05-28 Thread Django

#30520: ModelForm with field without label crashes when used in 
InlineModelAdmin.
-+
 Reporter:  George Tantiras  |Owner:  Jones
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+

Comment (by Jones):

 [https://github.com/django/django/pull/11426 PR]

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

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

[Django] #30522: How to use Custom install Sqlite3 in Django

2019-05-28 Thread Django

django.core.exceptions.ImproperlyConfigured: SQLite 3.8.3 or later is
required (found 3.6.20).

So I have custom installed "SQLite3 3.28.0" then set ENVs for
LD_LIBRARY_PATH and LD_RUN_PATH to use the latest SQLite3. In Shell and
Python IDLE or normal SQL script, am able to access "3.28.0" versions
Sqlite. But when running manage.py, am getting the error below:

conn = Database.connect(**conn_params)
django.db.utils.NotSupportedError: URIs not supported

Please try once the steps I have followed and then to consider to keep or
closing the ticket by referencing "28376"

1. Custom install SQLite3
2. Set env for PATH , LD_LIBRARY_PATH and LD_RUN_PATH
3. Try accessing sqlite3 in Python scripts to check the versions.

If you are able to connect, kindly share the steps to overcome the issue
from our side.

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

Re: [Django] #30520: ModelForm with field without label crashes when used in InlineModelAdmin.

2019-05-28 Thread Django

#30520: ModelForm with field without label crashes when used in 
InlineModelAdmin.
-+-
 Reporter:  George Tantiras  |Owner:  Jones
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Jones):

 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #30520: ModelForm with field without label crashes when used in InlineModelAdmin.

2019-05-28 Thread Django

#30520: ModelForm with field without label crashes when used in 
InlineModelAdmin.
-+
 Reporter:  George Tantiras  |Owner:  Jones
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+
Changes (by Jones):

 * stage:  Ready for checkin => 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/066.cd6959cdaf285c9630fa30634bf4b267%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30516: Autoreloader crashes on re-raising exceptions with custom signature.

2019-05-28 Thread Django

#30516: Autoreloader crashes on re-raising exceptions with custom signature.
-+--
 Reporter:  Alan Trick   |Owner:  Tom Forbes
 Type:  Bug  |   Status:  assigned
Component:  Utilities|  Version:  2.2
 Severity:  Release blocker  |   Resolution:
 Keywords:  autoreload   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by Tom Forbes):

 * owner:  nobody => Tom Forbes
 * status:  new => assigned
 * has_patch:  0 => 1


Comment:

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

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

44 matches

Mail list logo