Re: [Django] #29047: test_substr_with_expressions doesn't test expressions

[Django]

#29047: test_substr_with_expressions doesn't test expressions
-+-
 Reporter:  Matthew Pava |Owner:  Daniel
 Type:   |  Hones
  Cleanup/optimization   |   Status:  assigned
Component:  Testing framework|  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  Substr   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Daniel Hones):

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

Re: [Django] #29047: test_substr_with_expressions doesn't test expressions

[Django]

#29047: test_substr_with_expressions doesn't test expressions
-+-
 Reporter:  Matthew Pava |Owner:  Daniel
 Type:   |  Hones
  Cleanup/optimization   |   Status:  assigned
Component:  Testing framework|  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  Substr   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Daniel Hones):

 * owner:  nobody => Daniel Hones
 * status:  new => assigned


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

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

Re: [Django] #29050: using django-admin startproject give AttributeError

[Django]

#29050: using django-admin startproject give AttributeError
-+-
 Reporter:  Akshay Raj   |Owner:  nobody
  Gollahalli |
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  2.0
 Severity:  Normal   |   Resolution:  invalid
 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 Ramiro Morales):

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


Comment:

 TicketClosingReasons/UseSupportChannels

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

Re: [Django] #29050: using django-admin startproject give AttributeError (was: using django startproject give AttributeError)

[Django]

#29050: using django-admin startproject give AttributeError
-+-
 Reporter:  Akshay Raj   |Owner:  nobody
  Gollahalli |
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  2.0
 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
-+-
Description changed by Akshay Raj Gollahalli:

Old description:

> I was trying to create a Django 2 project by using `django startproject`
> gives me `AttributeError: module 'PIL._webp' has no attribute
> 'HAVE_WEBPANIM'`. The full error is
>
> {{{
> Traceback (most recent call last):
>   File "c:\users\aksha\anaconda3\envs\dj2\lib\runpy.py", line 193, in
> _run_module_as_main
> "__main__", mod_spec)
>   File "c:\users\aksha\anaconda3\envs\dj2\lib\runpy.py", line 85, in
> _run_code
> exec(code, run_globals)
>   File "C:\Users\aksha\Anaconda3\envs\dj2\Scripts\django-
> admin.exe\__main__.py", line 9, in 
>   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
> packages\django\core\management\__init__.py", line 371, in
> execute_from_command_line
> utility.execute()
>   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
> packages\django\core\management\__init__.py", line 365, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
> packages\django\core\management\base.py", line 288, in run_from_argv
> self.execute(*args, **cmd_options)
>   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
> packages\django\core\management\base.py", line 335, in execute
> output = self.handle(*args, **options)
>   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
> packages\django\core\management\commands\startproject.py", line 20, in
> handle
> super().handle('project', project_name, target, **options)
>   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
> packages\django\core\management\templates.py", line 117, in handle
> django.setup()
>   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
> packages\django\__init__.py", line 16, in setup
> from django.urls import set_script_prefix
>   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
> packages\django\urls\__init__.py", line 1, in 
> from .base import (
>   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
> packages\django\urls\base.py", line 8, in 
> from .exceptions import NoReverseMatch, Resolver404
>   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
> packages\django\urls\exceptions.py", line 1, in 
> from django.http import Http404
>   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
> packages\django\http\__init__.py", line 5, in 
> from django.http.response import (
>   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
> packages\django\http\response.py", line 13, in 
> from django.core.serializers.json import DjangoJSONEncoder
>   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
> packages\django\core\serializers\__init__.py", line 23, in 
> from django.core.serializers.base import SerializerDoesNotExist
>   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
> packages\django\core\serializers\base.py", line 6, in 
> from django.db import models
>   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
> packages\django\db\models\__init__.py", line 3, in 
> from django.db.models.aggregates import *  # NOQA
>   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
> packages\django\db\models\aggregates.py", line 5, in 
> from django.db.models.expressions import Case, Func, Star, When
>   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
> packages\django\db\models\expressions.py", line 7, in 
> from django.db.models import fields
>   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
> packages\django\db\models\fields\__init__.py", line 11, in 
> from django import forms
>   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
> packages\django\forms\__init__.py", line 7, in 
> from django.forms.fields import *  # NOQA
>   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
> packages\django\forms\fields.py", line 16, in 
> from django.core import validators
>   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
> packages\django\core\validators.py", line 511, in 
> allowed_extensions=get_available_image_extensions(),
>   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
> packages\django\core\validators.py", line 506, in
> get_available_image_extensions
> Image.init()
>   File 

[Django] #29050: using django startproject give AttributeError

[Django]

#29050: using django startproject give AttributeError
-+
   Reporter:  Akshay Raj Gollahalli  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  contrib.admin  |Version:  2.0
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 I was trying to create a Django 2 project by using `django startproject`
 gives me `AttributeError: module 'PIL._webp' has no attribute
 'HAVE_WEBPANIM'`. The full error is

 {{{
 Traceback (most recent call last):
   File "c:\users\aksha\anaconda3\envs\dj2\lib\runpy.py", line 193, in
 _run_module_as_main
 "__main__", mod_spec)
   File "c:\users\aksha\anaconda3\envs\dj2\lib\runpy.py", line 85, in
 _run_code
 exec(code, run_globals)
   File "C:\Users\aksha\Anaconda3\envs\dj2\Scripts\django-
 admin.exe\__main__.py", line 9, in 
   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
 packages\django\core\management\__init__.py", line 371, in
 execute_from_command_line
 utility.execute()
   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
 packages\django\core\management\__init__.py", line 365, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
 packages\django\core\management\base.py", line 288, in run_from_argv
 self.execute(*args, **cmd_options)
   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
 packages\django\core\management\base.py", line 335, in execute
 output = self.handle(*args, **options)
   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
 packages\django\core\management\commands\startproject.py", line 20, in
 handle
 super().handle('project', project_name, target, **options)
   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
 packages\django\core\management\templates.py", line 117, in handle
 django.setup()
   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
 packages\django\__init__.py", line 16, in setup
 from django.urls import set_script_prefix
   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
 packages\django\urls\__init__.py", line 1, in 
 from .base import (
   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
 packages\django\urls\base.py", line 8, in 
 from .exceptions import NoReverseMatch, Resolver404
   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
 packages\django\urls\exceptions.py", line 1, in 
 from django.http import Http404
   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
 packages\django\http\__init__.py", line 5, in 
 from django.http.response import (
   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
 packages\django\http\response.py", line 13, in 
 from django.core.serializers.json import DjangoJSONEncoder
   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
 packages\django\core\serializers\__init__.py", line 23, in 
 from django.core.serializers.base import SerializerDoesNotExist
   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
 packages\django\core\serializers\base.py", line 6, in 
 from django.db import models
   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
 packages\django\db\models\__init__.py", line 3, in 
 from django.db.models.aggregates import *  # NOQA
   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
 packages\django\db\models\aggregates.py", line 5, in 
 from django.db.models.expressions import Case, Func, Star, When
   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
 packages\django\db\models\expressions.py", line 7, in 
 from django.db.models import fields
   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
 packages\django\db\models\fields\__init__.py", line 11, in 
 from django import forms
   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
 packages\django\forms\__init__.py", line 7, in 
 from django.forms.fields import *  # NOQA
   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
 packages\django\forms\fields.py", line 16, in 
 from django.core import validators
   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
 packages\django\core\validators.py", line 511, in 
 allowed_extensions=get_available_image_extensions(),
   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
 packages\django\core\validators.py", line 506, in
 get_available_image_extensions
 Image.init()
   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-packages\PIL\Image.py",
 line 406, in init
 __import__("PIL.%s" % plugin, globals(), locals(), [])
   File "c:\users\aksha\anaconda3\envs\dj2\lib\site-
 packages\PIL\WebPImagePlugin.py", line 313, in 
  

Re: [Django] #29023: running tests in parallel doesn't show exception chain, even with tblib

[Django]

#29023: running tests in parallel doesn't show exception chain, even with tblib
-+-
 Reporter:  Chris Jerdonek   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  parallel,exception,chain,traceback,pickling,tblib|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Chris Jerdonek):

 FYI, I implemented a proof-of-concept for the idea I described in my
 previous comment and posted it here:
 https://github.com/cjerdonek/django/tree/ticket_29023

 In particular, it handles both chained exceptions and non-picklable
 exceptions, and without aborting the test run in the latter case.

 I included example "before" and "after" outputs for both cases of chained
 exceptions and non-picklable exceptions in the commit message of this
 commit:
 
https://github.com/cjerdonek/django/commit/0040040ca4fec08a9980a24f08bcad900e2b0f22

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

Re: [Django] #28988: Multi-table inheritance breaks GenericRelation querying

[Django]

#28988: Multi-table inheritance breaks GenericRelation querying
--+
 Reporter:  robwa |Owner:  Paulo
 Type:  Bug   |   Status:  assigned
Component:  contrib.contenttypes  |  Version:  1.11
 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 Paulo):

 I think the behavior should be consistent with how a normal ForeignKey
 field behaves in multi-table inheritance.
 In the following scenario:


 {{{
 class Car(models.Model):
 owner = models.ForeignKey(Owner, related_name='cars')
 some_id = models.CharField(max_length=100)

 class Car2(Car):
 pass
 }}}


 Running
 {{{
 Owner.objects.filter(cars__isnull=True)
 }}}


 Will output:

 {{{
 SELECT "paulotest_owner"."id",
"paulotest_owner"."nick"
 FROM "paulotest_owner"
 LEFT OUTER JOIN "paulotest_car" ON ("paulotest_owner"."id" =
 "paulotest_car"."owner_id")
 WHERE "paulotest_car"."id" IS NULL
 }}}

 So we should prevent the reverse relationship from being set.

 @Robert, if you would like to work on this, I can un-assign it, I'm
 planning to tackle it within the next two weeks.

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

[Django] #29049: Add slicing notation to F expressions

[Django]

#29049: Add slicing notation to F expressions
-+-
   Reporter:  Matthew|  Owner:  nobody
  Pava   |
   Type:  New| Status:  new
  feature|
  Component:  Database   |Version:  master
  layer (models, ORM)|
   Severity:  Normal |   Keywords:  slice F
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 For fields that are string expressions, the slicing notation should
 utilize database functions `Substr`, `Left`, and `Right`.  Those functions
 could even be deprecated to require the use of slicing notation.

 For fields that are iterable expressions, such as `ArrayField`s or
 `HStoreField`s, those could utilize slicing notation in a Pythonic manner.

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

[Django] #29048: Add **extra_context arg to as_vendor methods in database functions

[Django]

#29048: Add **extra_context arg to as_vendor methods in database functions
-+-
   Reporter:  Matthew|  Owner:  nobody
  Pava   |
   Type: | Status:  new
  Cleanup/optimization   |
  Component:  Database   |Version:  master
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 `Func` inherits from `SQLiteNumericMixin`, which added an extra argument
 to `as_sqlite`: `**extra_context`.  Based on feedback from other
 developers, it seems we should add this argument to each `as_vendor`
 method.

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

[Django] #29047: test_substr_with_expressions doesn't test expressions

[Django]

#29047: test_substr_with_expressions doesn't test expressions
+
   Reporter:  Matthew Pava  |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Testing framework |Version:  2.0
   Severity:  Normal|   Keywords:  Substr
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  1
  UI/UX:  0 |
+
 The method implies that it tries to test the `Substr` function with
 expressions, but it is just duplicated from the `test_substr` function and
 does not use `Expression`s.

 The method is in  tests/db_functions/tests.py

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

Re: [Django] #29046: possible race condition with manager logic

[Django]

#29046: possible race condition with manager logic
-+-
 Reporter:  Andy Grabow  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 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
-+-
Description changed by Andy Grabow:

Old description:

> Hi,
>
> i tried a lot to explain this weird behaviour, but since it happens
> sometimes and doenst at other times i think that its due to some weird
> race condition.
>
> Please have a look at the travis build logs:
> https://travis-ci.org/kakulukia/django-undeletable
> https://travis-ci.org/kakulukia/django-undeletable/builds/331788403
> (build #23)
>
> Most of the time django 1.11 under python2 is failing.
> So please could someone with more knowledge about django manager magic
> have a look at my module?
>
> git clone https://github.com/kakulukia/django-undeletable.git
> git checkout cookiecutter-version
> make init2
> pipenv shell
> pip install django=1.11.9
> make test
>
> BTW: The django sources have been uploaded to pypi resulting in a python2
> pip trying to install django 2 which aint working. Is there a workaround?
> Why are the sources uploaded to pypi?

New description:

 Hi,

 i tried a lot to explain this weird behaviour, but since it happens
 sometimes and doenst at other times i think that its due to some weird
 race condition.

 Please have a look at the travis build logs:
 https://travis-ci.org/kakulukia/django-undeletable
 https://travis-ci.org/kakulukia/django-undeletable/builds/331788403 (build
 #23)

 Most of the time django 1.11 under python2 is failing.
 So please could someone with more knowledge about django manager magic
 have a look at my module?

 git clone https://github.com/kakulukia/django-undeletable.git
 git checkout cookiecutter-version
 make init2
 pipenv shell
 pip install django=1.11.9
 make test

 In the last 4 years of me using that module in different projects, this
 bug never happend. This might be due to the striped to the basics version
 of this unittest compared to a project with multiple other modules to load
 before actually executing any ORM logic. Just a guess.

 BTW: The django sources have been uploaded to pypi resulting in a python2
 pip trying to install django 2 which aint working. Is there a workaround?
 Why are the sources uploaded to pypi?

--

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

[Django] #29046: possible race condition with manager logic

[Django]

#29046: possible race condition with manager logic
-+-
   Reporter:  Andy   |  Owner:  nobody
  Grabow |
   Type:  Bug| Status:  new
  Component:  Database   |Version:  2.0
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Hi,

 i tried a lot to explain this weird behaviour, but since it happens
 sometimes and doenst at other times i think that its due to some weird
 race condition.

 Please have a look at the travis build logs:
 https://travis-ci.org/kakulukia/django-undeletable
 https://travis-ci.org/kakulukia/django-undeletable/builds/331788403 (build
 #23)

 Most of the time django 1.11 under python2 is failing.
 So please could someone with more knowledge about django manager magic
 have a look at my module?

 git clone https://github.com/kakulukia/django-undeletable.git
 git checkout cookiecutter-version
 make init2
 pipenv shell
 pip install django=1.11.9
 make test

 BTW: The django sources have been uploaded to pypi resulting in a python2
 pip trying to install django 2 which aint working. Is there a workaround?
 Why are the sources uploaded to pypi?

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

Re: [Django] #29045: Multiple select widget does not honor size attribute

[Django]

#29045: Multiple select widget does not honor size attribute
---+--
 Reporter:  Jonah Bishop   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.11
 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
---+--
Description changed by Jonah Bishop:

Old description:

> I have an admin page set up for a model like so:
>
> {{{
> @admin.register(p_models.ScheduleType)
> class ScheduleTypeAdmin(admin.ModelAdmin):
> formfield_overrides = {
> models.ManyToManyField: {'widget':
> forms.SelectMultiple(attrs={'size': '30'})},
> }
>
> list_display = ('name',)
> }}}
>
> The resulting ManyToMany field has the **size** attribute set properly,
> but every browser I try only shows about 8 rows (not 30, as I
> instructed). I've cleared cache, and tried in multiple browsers (Chrome
> 63, Firefox 57). My site uses Django 1.11.9.

New description:

 I have an admin page set up for a model like so:

 {{{
 @admin.register(p_models.ScheduleType)
 class ScheduleTypeAdmin(admin.ModelAdmin):
 formfield_overrides = {
 models.ManyToManyField: {'widget':
 forms.SelectMultiple(attrs={'size': '30'})},
 }

 list_display = ('name',)
 }}}

 The resulting ManyToMany field has the **size** attribute set properly,
 but every browser I try only shows about 8 rows (not 30, as I instructed).
 I've cleared cache, and tried in multiple browsers (Chrome 63, Firefox
 57). My site uses Django 1.11.9.

 It looks like the CSS style rules are overriding the **size** attribute.
 I'm guessing adding a **height: auto;** rule to the **select[multiple]**
 style set would fix it (it appears to do so in Chrome, at least).

--

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

[Django] #29045: Multiple select widget does not honor size attribute

[Django]

#29045: Multiple select widget does not honor size attribute
-+
   Reporter:  Jonah Bishop   |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  contrib.admin  |Version:  1.11
   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 have an admin page set up for a model like so:

 {{{
 @admin.register(p_models.ScheduleType)
 class ScheduleTypeAdmin(admin.ModelAdmin):
 formfield_overrides = {
 models.ManyToManyField: {'widget':
 forms.SelectMultiple(attrs={'size': '30'})},
 }

 list_display = ('name',)
 }}}

 The resulting ManyToMany field has the **size** attribute set properly,
 but every browser I try only shows about 8 rows (not 30, as I instructed).
 I've cleared cache, and tried in multiple browsers (Chrome 63, Firefox
 57). My site uses Django 1.11.9.

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

Re: [Django] #29036: HTML5 required validation does not work for SelectDateWidget

[Django]

#29036: HTML5 required validation does not work for SelectDateWidget
+--
 Reporter:  Vlastimil Zíma  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Forms   |  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 Herbert Fortes):

 Hi,

 I am searching for the 'Easy picking' ones. Let me comment:

 It seems that when Django thinks that the field is not required
 the value is 0, right?

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

Re: [Django] #29018: The 'E' date filter format should return lowercase months for Spanish

[Django]

#29018: The 'E' date filter format should return lowercase months for Spanish
-+-
 Reporter:  Michael Terry|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:   |  Version:  master
  Internationalization   |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Ramiro Morales):

 I've just fixed the es_AR translations on Transifex according to Michael
 proposal and taking in account the regression introduced in 1.5. These
 changes won't be visible to users until 2.1 gets released though.

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

Re: [Django] #29018: The 'E' date filter format should return lowercase months for Spanish

[Django]

#29018: The 'E' date filter format should return lowercase months for Spanish
-+-
 Reporter:  Michael Terry|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:   |  Version:  master
  Internationalization   |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Michael Terry):

 I've emailed the django-i18n list about this, in an attempt to discuss it
 with the Spanish team. I couldn't find a specific list for just them.

 https://groups.google.com/forum/#!topic/django-i18n/NzbFpJHtpfI

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

Re: [Django] #28838: annotations + base_manager_name + instance.save() raises exception

[Django]

#28838: annotations + base_manager_name + instance.save() raises exception
-+-
 Reporter:  James Addison|Owner:
 |  shangdahao
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.11
  (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 shangdahao):

 * needs_better_patch:  1 => 0


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

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

Re: [Django] #28889: Use JavaScript to prevent double submission of admin forms

[Django]

#28889: Use JavaScript to prevent double submission of admin forms
-+-
 Reporter:  Manuel Saelices  |Owner:  Karan
 Type:   |  Bedi
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Carlton Gibson):

 Hi Karan,

 Thanks for the input. Your fix includes the changes Nick suggested from
 the original PR. (Great.)

 To get this merged we need to address Tim's concerns.

 * Can we add some selenium tests, to exercise the behaviour?
 * What's your assessment of the article Tim linked to? Do we need to do
 this?

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

Re: [Django] #20218: Default authorization backend returns False when queried for object level permissions

[Django]

#20218: Default authorization backend returns False when queried for object 
level
permissions
--+
 Reporter:  soren@…   |Owner:  Mehmet Dogan
 Type:  Bug   |   Status:  assigned
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  auth  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Carlton Gibson):

 * needs_better_patch:  0 => 1


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

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