Re: [Django] #2259: Primary keys should be readonly by default in admin

[Django]

#2259: Primary keys should be readonly by default in admin
-+-
 Reporter:  ed@… |Owner:  Pathangi
 |  Jatinshravan
 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:  0|UI/UX:  0
-+-

Comment (by michjnich):

 Doesn't appear to be the same issue as it was to start with, if it still
 exists at all. I replicated the original test in comment #1 using the
 Group table, and it works fine now:

 {{{
 >>> from django.contrib.auth.models import Group
 >>> Group.objects.all()
 
 >>> g = Group(name="test")
 >>> g.save()
 >>> Group.objects.all()
 ]>
 >>> g = Group.objects.get(name="test")
 >>> g.name="testx"
 >>> g.save()
 >>> Group.objects.all()
 ]>
 }}}

 I then changed this back to "test" via the admin interface, which also
 resulted in a single record called "test" without any issues. As far as I
 can tell, the original issue no longer exists and this should be closed.

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

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

Re: [Django] #30758: DateTimeRangeField with default crashes in django admin (object has no attribute 'strip').

[Django]

#30758: DateTimeRangeField with default crashes in django admin (object has no
attribute 'strip').
-+-
 Reporter:  yeppus   |Owner:  Nasir
 |  Hussain
 Type:  Bug  |   Status:  assigned
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  DateTimeRangeField   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Nasir Hussain):

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

Re: [Django] #30774: Migrations uses value of enum object instead of its name.

[Django]

#30774: Migrations uses value of enum object instead of its name.
--+--
 Reporter:  oasl  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Migrations|  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  Enum, Migrations  | Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by oasl):

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


Comment:

 To experience the bug:

 In any Django project, set the default value of a CharField as an enum
 object:

 {{{
 class EnumClass(Enum):
  VALUE = _('Value')
 }}}
 where:
 VALUE: is the constant enum object name
 'Value': is the translatable enum object value

 In the model:
 {{{
 field = models.CharField(default=EnumClass.VALUE, max_length=128)
  }}}

 then run: python manage.py makemigrations

 In the generated migration file, you will notice that the default value of
 the field is set to: EnumClass('Value'), so it calls the enum object by
 its value not it is constant name.
 run: python manage.py migrate

 In the settings.py file:
 {{{
 LANGUAGE_CODE = 'fr-FR' # set it to any language code other than English
 }}}

 Run the project after generating, translating, and compiling the messages
 file (see: [https://docs.djangoproject.com/en/2.2/topics/i18n/translation
 /#message-files message-files])

 The project will raise the error: {{{ ValueError: 'Value' is not a valid
 EnumClass }}}, on the generated migration file.

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

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

Re: [Django] #29823: Incorrect Decimal handling in Sum queries

[Django]

#29823: Incorrect Decimal handling in Sum queries
-+-
 Reporter:  Jurica Železnjak |Owner:  Mariusz
 Type:   |  Felisiak 
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  2.1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"f452d4232e1c14269bf2f1bd234d6e4ef462dc55" f452d42]:
 {{{
 #!CommitTicketReference repository=""
 revision="f452d4232e1c14269bf2f1bd234d6e4ef462dc55"
 [2.2.x] Fixed #29823 -- Doc'd limitation of DecimalField on SQLite.

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

Re: [Django] #29823: Incorrect Decimal handling in Sum queries

[Django]

#29823: Incorrect Decimal handling in Sum queries
-+-
 Reporter:  Jurica Železnjak |Owner:  Mariusz
 Type:   |  Felisiak 
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  2.1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

 * owner:  (none) => Mariusz Felisiak 
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"b8dff52f440adfb78b40e19ee8bff45373ca2501" b8dff52f]:
 {{{
 #!CommitTicketReference repository=""
 revision="b8dff52f440adfb78b40e19ee8bff45373ca2501"
 Fixed #29823 -- Doc'd limitation of DecimalField on SQLite.
 }}}

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

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

Re: [Django] #29823: Incorrect Decimal handling in Sum queries

[Django]

#29823: Incorrect Decimal handling in Sum queries
-+-
 Reporter:  Jurica Železnjak |Owner:  Mariusz
 Type:   |  Felisiak 
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  2.1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"c2057205d9f30247e9d512d42114f27d0a93a96e" c2057205]:
 {{{
 #!CommitTicketReference repository=""
 revision="c2057205d9f30247e9d512d42114f27d0a93a96e"
 [3.0.x] Fixed #29823 -- Doc'd limitation of DecimalField on SQLite.

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

Re: [Django] #29446: Include template context in error page when relevant

[Django]

#29446: Include template context in error page when relevant
-+
 Reporter:  Shai Berger  |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Error reporting  |  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  template debug   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+
Changes (by Min ho Kim):

 * cc: Min ho Kim (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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.a1664eec0e856ff19ff2fa27f7da2ce6%40djangoproject.com.

Re: [Django] #29446: Include template context in error page when relevant

[Django]

#29446: Include template context in error page when relevant
-+
 Reporter:  Shai Berger  |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Error reporting  |  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  template debug   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+

Comment (by Min ho Kim):

 Hi Shai Berger,
 Could you give some more information about this feature request?
 It would be nice to have some example of error page you would like to see.

 If anyone else has any idea what the expected error page should look like,
 please comment.

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

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

Re: [Django] #30773: Support Algorithm parameter on MySQL migrations.

[Django]

#30773: Support Algorithm parameter on MySQL migrations.
-+-
 Reporter:  mklauber |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  mysql| 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:   => wontfix
 * component:  Migrations => Database layer (models, ORM)


Comment:

 I totally agree with Simon.

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

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

Re: [Django] #30775: Tutorial part 5 testing often encounters import errors

[Django]

#30775: Tutorial part 5 testing often encounters import errors
-+-
 Reporter:  Katie McLaughlin |Owner:  Katie
 Type:   |  McLaughlin
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  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 Claude Paroz):

 * has_patch:  0 => 1
 * stage:  Unreviewed => Accepted


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

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