Re: [Django] #30515: Document django.shortcuts.resolve_url.

[Django]

#30515: Document django.shortcuts.resolve_url.
-+-
 Reporter:  sage |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by felixxm):

 The way how `resolve_url()` works is already described in the
 [https://docs.djangoproject.com/en/2.2/topics/http/shortcuts/#redirect
 redirect()] documentation. Have you checked it? Can you describe any use
 cases for `resolve_url()` (except the current)?


 Please see
 [https://docs.djangoproject.com/en/stable/internals/contributing/triaging-
 tickets/#closing-tickets follow triaging guidelines with regards to
 wontfix tickets.]

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

Re: [Django] #30542: Float-valued aggregations and annotations with filters fail with AttributeError

[Django]

#30542: Float-valued aggregations and annotations with filters fail with
AttributeError
-+-
 Reporter:  Chuan-Zheng Lee  |Owner:  Étienne
 |  Beaulé
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  aggregation, | Triage Stage:  Accepted
  annotation, filter |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Nick Pope):

 * version:  2.0 => 2.2
 * severity:  Normal => Release blocker


Comment:

 Correct, this is a regression in
 
[https://github.com/django/django/pull/10764/commits/c690afb873cac8035a3cb3be7c597a5ff0e4b261
 c690afb] which affects `Avg()`. `StdDev()` and `Variance()` are affected
 by
 
[https://github.com/django/django/pull/10764/commits/e85afa5943695457c85e9bc1c5dc0d985004e303
 e85afa5] and
 
[https://github.com/django/django/pull/10764/commits/6d4efa8e6a4cc7be4ba957dec71f6f63cd58700d
 6d4efa8] respectively.

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

Re: [Django] #30542: Float-valued aggregations and annotations with filters fail with AttributeError

[Django]

#30542: Float-valued aggregations and annotations with filters fail with
AttributeError
-+-
 Reporter:  Chuan-Zheng Lee  |Owner:  Étienne
 |  Beaulé
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  aggregation, | Triage Stage:  Accepted
  annotation, filter |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Chuan-Zheng Lee):

 Contrary to my earlier guess, the first commit with the issue is
 c690afb873cac8035a3cb3be7c597a5ff0e4b261, which modifies `Avg` to use the
 new logic. Its parent, 3d5e0f8394688d40036e27cfcfac295e6fe622609, works
 fine, because while it modified the mixin to its current form, it didn't
 touch `Avg`.

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

Re: [Django] #30536: Allow running custom logic in django.setup().

[Django]

#30536: Allow running custom logic in django.setup().
+
 Reporter:  pascal chambon  |Owner:  nobody
 Type:  New feature |   Status:  new
Component:  Core (Other)|  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  setup   | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+

Comment (by pascal chambon):

 Ok the PR is pending for  #28752  B-)

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

Re: [Django] #30542: Float-valued aggregations and annotations with filters fail with AttributeError

[Django]

#30542: Float-valued aggregations and annotations with filters fail with
AttributeError
-+-
 Reporter:  Chuan-Zheng Lee  |Owner:  Étienne
 |  Beaulé
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  aggregation, | Triage Stage:  Accepted
  annotation, filter |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Étienne Beaulé):

 * status:  new => assigned
 * owner:  nobody => Étienne Beaulé
 * has_patch:  0 => 1
 * version:  2.2 => 2.0
 * stage:  Unreviewed => Accepted


Comment:

 [https://github.com/django/django/pull/11443 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/063.df3bf64c2149bc1aa71781d09187%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30515: Document django.shortcuts.resolve_url.

[Django]

#30515: Document django.shortcuts.resolve_url.
-+-
 Reporter:  sage |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Adam (Chainz) Johnson):

 * cc: Adam (Chainz) Johnson (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/067.675f99a0e6c0cf843d8ec1d550ed7148%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30515: Document django.shortcuts.resolve_url.

[Django]

#30515: Document django.shortcuts.resolve_url.
-+-
 Reporter:  sage |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Adam (Chainz) Johnson):

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


Comment:

 I disagree, I think this could be pretty useful and it seems well
 documented internally already

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

Re: [Django] #30542: Float-valued aggregations and annotations with filters fail with AttributeError

[Django]

#30542: Float-valued aggregations and annotations with filters fail with
AttributeError
-+-
 Reporter:  Chuan-Zheng Lee  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  aggregation, | Triage Stage:
  annotation, filter |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Chuan-Zheng Lee):

 I couldn't tell you for sure because I haven't actually tried reproducing
 it on this commit or its parent, but if I had to take a guess as to which
 commit introduced the issue, I'd try
 a0b19a0f5b1731cf575546175034da53f5af5367, which introduced
 `OutputFieldMixin`, a precursor to `NumericOutputFieldMixin` with similar
 logic. I'll say something if I manage to give this a go.

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

[Django] #30542: Float-valued aggregations and annotations with filters fail with AttributeError

[Django]

#30542: Float-valued aggregations and annotations with filters fail with
AttributeError
-+-
   Reporter:  Chuan- |  Owner:  nobody
  Zheng Lee  |
   Type:  Bug| Status:  new
  Component:  Database   |Version:  2.2
  layer (models, ORM)|   Keywords:  aggregation,
   Severity:  Normal |  annotation, filter
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 When any float-valued aggregation or annotation (`Avg`, `StdDev`,
 `Variance`) is used with the `filter=` keyword argument, the following
 exception is raised:
 {{{
 AttributeError: 'WhereNode' object has no attribute 'output_field'
 }}}

 For example, these queries all fail with this error:
 {{{#!python
 Speaker.objects.annotate(average=Avg('speakerscore__score',
 filter=Q(speakerscore__ghost=False)))
 Speaker.objects.annotate(average=StdDev('speakerscore__score',
 filter=Q(speakerscore__ghost=False)))
 Team.objects.annotate(average=Avg('debateteam__teamscore__score',
 filter=Q(debateteam__teamscore__forfeit=False)))
 }}}

 The error seems to be raised irrespective of what's in the database
 (''e.g.'', it's raised even for an empty database). However, it doesn't
 affect aggregations like `Sum`, `Max` or `Min` that don't use
 `NumericOutputFieldMixin`. Also, queries that don't use the `filter=`
 keyword in the aggregation work fine.

 The exception in question is raised from line 46 of
 django/db/models/functions/mixins.py, which looks for an `output_field`
 attribute of every element of `self.get_source_expressions()`, where
 `self` is the object containing `NumericOutputFieldMixin`, in this case
 `Avg` or some other subclass of `Aggregate`. But
 `Aggregate.get_source_expressions()` includes `self.filter` in its list,
 and (post-compilation) `self.filter` is a `WhereNode`, which doesn't have
 an `output_field` attribute.

 This issue is new in version 2.2. Everything works fine in version 2.1
 (where I believe `NumericOutputFieldMixin` didn't exist, or at least
 wasn't on the MRO for `Avg`, `StdDev` or `Variance`).

 === Minimal reproducible example

 In a blank (or any) project, insert in models.py:
 {{{#!python
 from django.db.models import Model, FloatField, BooleanField

 class Book(Model):
 price = FloatField()
 fiction = BooleanField()
 }}}
 then run migrations and in `python manage.py shell`:
 {{{
 $ python manage.py shell
 Python 3.6.7 (default, Oct 22 2018, 11:32:17)
 [GCC 8.2.0] on linux
 Type "help", "copyright", "credits" or "license" for more information.
 (InteractiveConsole)
 >>> from django22_output_field_bug.models import Book
 >>> from django.db.models import Avg, Q
 >>> Book.objects.annotate(average=Avg('price', filter=Q(fiction=True)))
 Traceback (most recent call last):
 [...]
   File "/[...]/django/db/models/functions/mixins.py", line 46, in
 
 if any(isinstance(s.output_field, DecimalField) for s in
 source_expressions):
 AttributeError: 'WhereNode' object has no attribute 'output_field'
 >>> Book.objects.aggregate(average=Avg('price', filter=Q(fiction=True)))
 Traceback (most recent call last):
 [...]
   File "/[...]/django/db/models/functions/mixins.py", line 46, in
 
 if any(isinstance(s.output_field, DecimalField) for s in
 source_expressions):
 AttributeError: 'WhereNode' object has no attribute 'output_field'
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To 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.1d8992093063682dc93e81858a194906%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

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

[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:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by George Tantiras):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/11442 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.8a0366862d59a8c3a48c3e6d3472b79f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28490: Descriptors on Models are reported as nonexistent by System Check Framework for ModelAdmin.list_display if they return None

[Django]

#28490: Descriptors on Models are reported as nonexistent by System Check 
Framework
for ModelAdmin.list_display if they return None
-+-
 Reporter:  Hunter Richards  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  admin, descriptor,   | Triage Stage:  Accepted
  system, checks, framework, |
  validation |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by ajcsimons):

 Unfortuantely this fix causes other bugs:
 1. if hasattr(obj.model, item) returns false then we go straight to the
 else clause which returns the error,
 2. whereas before the else clause did another check for
 model._meta.get_field(item) and would only return the error if that raised
 a FieldDoesNotExist exception
 3. So how is it that hasattr(model, item) can return false, but
 model._meta.get_field(item) will return something meaning the check should
 not return an error?
 4. Answer: the field is a special one which is only valid to access on
 instances of the model (whose ModelAdmin we are verifying) and not the
 model class itself. An example of this is the PositionField from the
 django-positions library (which inherits from djangos
 models.IntegerField):
 {{{
 def __get__(self, instance, owner):
 if instance is None:
 raise AttributeError("%s must be accessed via instance." %
 self.name)
 current, updated = getattr(instance, self.get_cache_name())
 return current if updated is None else 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.8b4d46cc4197dfcb962245f369bf0207%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #30541: Django MultiDB tests not loading fixtures as expected

[Django]

#30541: Django MultiDB tests not loading fixtures as expected
-+
   Reporter:  Vackar Afzal   |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Testing framework  |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  |
-+
 I've recently upgraded from Django 2.0 to Django 2.2 and have found the
 fixture loading logic appears to have changed. The core issue seems to be
 related to the introduction of `databases`

 Given the following test case:

 {{{
 class BaseTestCase(TestCase, TestUtilsMixin):

 databases = '__all__'
 fixtures = [
 'data_x1.default.yaml',
 'data_x2.default.yaml',
 'data_x3.default.yaml',
 'data_x4.default.yaml',
 'data_x5.default.yaml',
 'data_x6.default.yaml'
 ]

 }}}

 I would expect data_xx fixtures to only to be loaded into the 'default'
 alias, but it appears to be loading into all connections defined in
 `DATABASES`, resulting in the following error

 {{{
 Error
 Traceback (most recent call last):
   File "django/db/backends/utils.py", line 84, in _execute
 return self.cursor.execute(sql, params)
   File "django/db/backends/oracle/base.py", line 510, in execute
 return self.cursor.execute(query, self._param_generator(params))
 cx_Oracle.DatabaseError: ORA-00942: table or view does not exist

 The above exception was the direct cause of the following exception:

 Traceback (most recent call last):
   File "django/core/serializers/pyyaml.py", line 73, in Deserializer
 yield from PythonDeserializer(yaml.load(stream, Loader=SafeLoader),
 **options)
   File "django/core/serializers/python.py", line 147, in Deserializer
 obj = base.build_instance(Model, data, using)
   File "django/core/serializers/base.py", line 266, in build_instance
 default_manager.db_manager(db).get_by_natural_key(*natural_key).pk
   File "managers.py", line 15, in get_by_natural_key
 return self.get(name=name)
   File "django/db/models/manager.py", line 82, in manager_method
 return getattr(self.get_queryset(), name)(*args, **kwargs)
   File "django/db/models/query.py", line 402, in get
 num = len(clone)
   File "django/db/models/query.py", line 256, in __len__
 self._fetch_all()
   File "django/db/models/query.py", line 1242, in _fetch_all
 self._result_cache = list(self._iterable_class(self))
   File "django/db/models/query.py", line 55, in __iter__
 results = compiler.execute_sql(chunked_fetch=self.chunked_fetch,
 chunk_size=self.chunk_size)
   File "django/db/models/sql/compiler.py", line 1100, in execute_sql
 cursor.execute(sql, params)
   File "raven/contrib/django/client.py", line 127, in execute
 return real_execute(self, sql, params)
   File "django/db/backends/utils.py", line 67, in execute
 return self._execute_with_wrappers(sql, params, many=False,
 executor=self._execute)
   File "django/db/backends/utils.py", line 76, in _execute_with_wrappers
 return executor(sql, params, many, context)
   File "django/db/backends/utils.py", line 84, in _execute
 return self.cursor.execute(sql, params)
   File "django/db/utils.py", line 89, in __exit__
 raise dj_exc_value.with_traceback(traceback) from exc_value
   File "django/db/backends/utils.py", line 84, in _execute
 return self.cursor.execute(sql, params)
   File "django/db/backends/oracle/base.py", line 510, in execute
 return self.cursor.execute(query, self._param_generator(params))
 django.db.utils.DatabaseError: ORA-00942: table or view does not exist

 The above exception was the direct cause of the following exception:

 Traceback (most recent call last):
   File "django/test/testcases.py", line 1131, in setUpClass
 call_command('loaddata', *cls.fixtures, **{'verbosity': 0, 'database':
 db_name})
   File "django/core/management/__init__.py", line 148, in call_command
 return command.execute(*args, **defaults)
   File "django/core/management/base.py", line 364, in execute
 output = self.handle(*args, **options)
   File "django/core/management/commands/loaddata.py", line 72, in handle
 self.loaddata(fixture_labels)
   File "django/core/management/commands/loaddata.py", line 114, in
 loaddata
 self.load_label(fixture_label)
   File "django/core/management/commands/loaddata.py", line 172, in
 load_label
 for obj in objects:
   File "django/core/serializers/pyyaml.py", line 77, in Deserializer
 raise DeserializationError() from exc
 }}}



 I've hacked together a workaround by overriding setUpClass as follows:

 

Re: [Django] #56: Primary key columns should be UNSIGNED

[Django]

#56: Primary key columns should be UNSIGNED
-+-
 Reporter:  Manuzhai |Owner:  Caio
 |  Ariede
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  mysql| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Caio Ariede):

 * owner:  (none) => Caio Ariede
 * status:  new => assigned


Comment:

 I'll try to revive this 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/085.c9f8f77597fecf976af0741491b22b08%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30505: Ordering of Field.choices is significant for makemigrations

[Django]

#30505: Ordering of Field.choices is significant for makemigrations
-+-
 Reporter:  Marnanel Thurman |Owner:  Caio
 Type:   |  Ariede
  Cleanup/optimization   |   Status:  closed
Component:  Migrations   |  Version:  master
 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:"d6d65c1e87d0da52e43d6359290a7b3f77367576" d6d65c1]:
 {{{
 #!CommitTicketReference repository=""
 revision="d6d65c1e87d0da52e43d6359290a7b3f77367576"
 [2.2.x] Fixed #30505 -- Doc'd how changes in the order of Field.choices
 affect migrations.

 Backport of 5248abe9b0425c1fc989c60a55860cdb4d135bcf 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/066.5e3f3eaf45ebf6f5050b46f55d134be3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30505: Ordering of Field.choices is significant for makemigrations

[Django]

#30505: Ordering of Field.choices is significant for makemigrations
-+-
 Reporter:  Marnanel Thurman |Owner:  Caio
 Type:   |  Ariede
  Cleanup/optimization   |   Status:  closed
Component:  Migrations   |  Version:  master
 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 ):

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


Comment:

 In [changeset:"5248abe9b0425c1fc989c60a55860cdb4d135bcf" 5248abe9]:
 {{{
 #!CommitTicketReference repository=""
 revision="5248abe9b0425c1fc989c60a55860cdb4d135bcf"
 Fixed #30505 -- Doc'd how changes in the order of Field.choices affect
 migrations.
 }}}

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

Re: [Django] #30475: Use of i18n_patterns and a buggy 404 template trigger internal server error without a backtrace.

[Django]

#30475: Use of i18n_patterns and a buggy 404 template trigger internal server 
error
without a backtrace.
-+--
 Reporter:  Erik Stein   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (URLs)  |  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 Erik Stein):

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


Comment:

 Please forgive me for reopening the ticket again!

 I guess my original question and reason to open a ticket was that I'm
 irritated that i18n_patterns will break in production mode if you have a
 buggy 404 template, instead of just redirecting to the correct URL. This
 doesn't seem to be correct behaviour in my eyes.

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

Re: [Django] #25287: Multiplying and dividing connectors for datetime expressions are not supported by sqlite backed.

[Django]

#25287: Multiplying and dividing connectors for datetime expressions are not
supported by sqlite backed.
-+-
 Reporter:  Ahmet DAL|Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  sqlite3, | Triage Stage:  Accepted
  combine_duration_expression, F |
  expressions,   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Caio Ariede):

 * owner:  Caio Ariede => (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/066.2710614d75bdbbac92f33f2f3f495cc6%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.

[Django]

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

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


Comment:

 In [changeset:"f9561144d79bad88ee5781e3b2c09fb7c8f7fd7d" f9561144]:
 {{{
 #!CommitTicketReference repository=""
 revision="f9561144d79bad88ee5781e3b2c09fb7c8f7fd7d"
 Fixed #30520 -- Fixed crash of admin model inlines on custom fields
 without labels.
 }}}

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

Re: [Django] #30534: Allow `cleaned_data` to overwrite fields' default values.

[Django]

#30534: Allow `cleaned_data` to overwrite fields' default values.
-+-
 Reporter:  Robin (Robert)   |Owner:  Robin
  Thomas |  (Robert) Thomas
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  forms, models| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"aa94f7c899b98f547fc1d26797ba892c38eaf415" aa94f7c8]:
 {{{
 #!CommitTicketReference repository=""
 revision="aa94f7c899b98f547fc1d26797ba892c38eaf415"
 Fixed #30534 -- Fixed overriding a field's default in
 ModelForm.cleaned_data().
 }}}

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

Re: [Django] #27147: Add support for defining bounds in postgres range fields

[Django]

#27147: Add support for defining bounds in postgres range fields
-+-
 Reporter:  Kirill Stepanov  |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  postgres range   | Triage Stage:  Accepted
  bounds |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by George Tantiras):

 * cc: George Tantiras (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.5beef07d8e1acd4b4631637a1cbd1080%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30402: Django default_site admin configuration doesn't register anything. (was: Django default_site admin configuration doesn't register anything)

[Django]

#30402: Django default_site admin configuration doesn't register anything.
+--
 Reporter:  Przemek Pawlas  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  contrib.admin   |  Version:  master
 Severity:  Normal  |   Resolution:  worksforme
 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 felixxm):

 * status:  new => closed
 * resolution:   => worksforme
 * stage:  Unreviewed => Accepted


Comment:

 Thanks for an extra info, however you should customize a default admin
 site inside a main project directory (like described in the documentation)
 not in an app.

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