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:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin, descriptor,   | Triage Stage:
  system, checks, framework, |  Unreviewed
  validation |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Hunter Richards):

 * Attachment "modeladmin_none_descriptor_error.diff" 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.3a6b472ec20f8e7525a8481f9e2378a3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[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 |  Owner:  nobody
  Richards   |
   Type:  Bug| Status:  new
  Component: |Version:  master
  contrib.admin  |   Keywords:  admin, descriptor,
   Severity:  Normal |  system, checks, framework,
   Triage Stage: |  validation
  Unreviewed |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 = Brief Description

 The Django ModelAdmin System Checks will erroneously mark as invalid any
 reference in `list_display` to a Descriptor on that ModelAdmin's model
 that returns `None` when accessed on that model's class, even if the
 Descriptor would return non-null values in the resulting ListView.

 This error is due to code that subtly conflates a reference to a field
 descriptor with the return value of that descriptor.  In this ticket, I
 give an in-depth explanation of the bug and a short fix, presented inline,
 for demonstration purposes, and a larger fix containing an exciting
 refactor and a justification for it.


 = Example

 Given a model with a field that is a Descriptor that returns `None`:

 {{{#!python
 class DescriptorThatReturnsNone(object):
 def __get__(self, obj, objtype):
 return None

 def __set__(self, obj, value):
 pass


 class ValidationTestModel(models.Model):
 some_other_field = models.CharField(max_length=100)
 none_descriptor = DescriptorThatReturnsNone()
 }}}

 and a ModelAdmin that includes that Descriptor field in `list_display`:

 {{{#!python
 class TestModelAdmin(ModelAdmin):
 list_display = ('some_other_field', 'none_descriptor')
 }}}

 then the system checks that run at project start will fail to find that
 Descriptor attribute with the following error message:

 {{{
 (admin.E108) The value of 'list_display[4]' refers to 'none_descriptor',
 which is not a callable, an attribute of 'TestModelAdmin', or an attribute
 or method on 'modeladmin.ValidationTestModel'.
 }}}


 = Location of Error

 The location of the error is in the following code:

 
https://github.com/django/django/blob/335aa088245a4cc6f1b04ba098458845344290bd/django/contrib/admin/checks.py#L586-L607

 {{{#!python
 elif hasattr(model, item):
 # getattr(model, item) could be an X_RelatedObjectsDescriptor
 try:
 field = model._meta.get_field(item)
 except FieldDoesNotExist:
 try:
 field = getattr(model, item)
 except AttributeError:
 field = None

 if field is None:
 return [
 checks.Error([...]
 }}}

 We follow the branch for `has_attr(model, item)`, and `field =
 model._meta.get_field(item)` throws an error, so we call `field =
 getattr(model, item)` for the purpose of either getting a reference to
 this non-field attribute or its value itself, depending on the type of
 `item`.  Supposedly, if `getattr` were to throw an error, we'd set `field`
 to none and return E108 (more on this below), but in the Descriptor case
 above, we don't.  But `field` is still `None`, i.e. the return value of
 the descriptor, so E108 is triggered anyway, even though the Descriptor
 field is a perfectly valid value to display in a ListView.

 The cause of the error comes from confusing the "type" of `field`: when
 using Descriptors, it is not always the case that `getattr(SomeClass,
 some_attr_name)` will return a reference to the field in question and
 `getattr(some_class_instance, some_attr_name)` will return the actual
 value of the attribute, which is the unstated assumption of the quoted
 code.  Therefore, `field` sometimes references a field itself, and
 sometimes a field's value.


 = A Workaround and a Quick Fix

 I triggered this error with a slightly more complicated Descriptor that
 returned the value of a related field on its declared model, and `None` if
 that were not possible.  Realizing the special value `None` was at the
 heart of the error, as a workaround I rewrote the Descriptor to return the
 empty string as an "empty" value instead of `None` which is
 indistinguishable from `None` in a ListView.

 As an example of how I intend to fix the error, here's The Simplest Thing
 that Could Possibly Work:

 {{{#!diff
 diff --git a/django/contrib/admin/checks.py
 b/django/contrib/admin/checks.py
 index 830a190..b6b49a5 100644
 --- a/django/contrib/admin/checks.py
 +++ b/django/contrib/admin/checks.py
 

Re: [Django] #28487: runserver crashes with UncodeDecodeError as of Django 1.11.4

[Django]

#28487: runserver crashes with UncodeDecodeError as of Django 1.11.4
-+-
 Reporter:  newerBkl |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  1.11
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by newerBkl):

 Replying to [comment:3 Tim Graham]:
 > You can add `print(key, new_environ[key])` before the line with
 `force_bytes(new_environ[key], encoding=encoding)` to see the problematic
 value.
 **Thanks , here is the output**

 {{{
 ('TMP', 'C:\\Users\\10\\AppData\\Local\\Temp')
 ('PSMODULEPATH',
 'C:\\Windows\\system32\\WindowsPowerShell\\v1.0\\Modules\\')
 ('PROCESSOR_LEVEL', '6')
 ('_OLD_VIRTUAL_PATH', 'C:\\Program Files (x86)\\Common
 
Files\\NetSarang;C:\\Python27\\;C:\\Python27\\Scripts;C:\\Windows\\system32;C:\\Windows
 
;C:\\Windows\\System32\\Wbem;C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\;C:\\Program
 Files (x86)\\\xb8\xbb\xbb\xf9\xd0\xfd\xb7\xe7\xbf\xc
 6\xbc\xbc\\appSys01;C:\\Program Files
 (x86)\\\xb8\xbb\xbb\xf9\xd0\xfd\xb7\xe7\xbf\xc6\xbc\xbc\\appSys02;C:\\Program
 Files (x86)\\\xb8\xbb\xbb\
 xf9\xd0\xfd\xb7\xe7\xbf\xc6\xbc\xbc\\appSys01;C:\\Program Files
 (x86)\\\xb8\xbb\xbb\xf9\xd0\xfd\xb7\xe7\xbf\xc6\xbc\xbc\\appSys02;C:\\Program
 Files
 (x86)\\\xb8\xbb\xbb\xf9\xd0\xfd\xb7\xe7\xbf\xc6\xbc\xbc\\appSys03;C:\\Program
 Files\\TortoiseSVN\\bin;;C:\\Program Files\\Microsoft VS C
 ode\\bin')
 Traceback (most recent call last):
 }}}
 **
 there was a path with Chinese in my system_path.After removing ,it works
 well**

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

Re: [Django] #28351: "Conflicting migrations detected" CommandError due to replacement Migration being removed

[Django]

#28351: "Conflicting migrations detected" CommandError due to replacement 
Migration
being removed
---+
 Reporter:  Daniel Hahler  |Owner:  Windson yang
 Type:  Bug|   Status:  closed
Component:  Migrations |  Version:  1.11
 Severity:  Normal |   Resolution:  needsinfo
 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 Tim Graham):

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


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

Re: [Django] #28485: Make ExceptionReporter.get_traceback_frames() include frames without source code

[Django]

#28485: Make ExceptionReporter.get_traceback_frames() include frames without 
source
code
-+-
 Reporter:  Martin von Gagern|Owner:  Tim
 |  Graham 
 Type:  Bug  |   Status:  closed
Component:  Error reporting  |  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 Tim Graham ):

 * status:  new => closed
 * owner:  (none) => Tim Graham 
 * resolution:   => fixed


Comment:

 In [changeset:"71d39571f46701a5a65adf8bf21005a177cda11f" 71d39571]:
 {{{
 #!CommitTicketReference repository=""
 revision="71d39571f46701a5a65adf8bf21005a177cda11f"
 Fixed #28485 -- Made ExceptionReporter.get_traceback_frames() include
 frames without source code.
 }}}

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

Re: [Django] #28201: Make CharField form field prohibit null characters

[Django]

#28201: Make CharField form field prohibit null characters
-+-
 Reporter:  CM Lubinski  |Owner:  Alejandro
 Type:   |  Zamora Fonseca
  Cleanup/optimization   |   Status:  closed
Component:  Forms|  Version:  1.11
 Severity:  Normal   |   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 Tim Graham ):

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


Comment:

 In [changeset:"90d7b912b9c451dfdfb38f5f1f598af3b879257f" 90d7b91]:
 {{{
 #!CommitTicketReference repository=""
 revision="90d7b912b9c451dfdfb38f5f1f598af3b879257f"
 Fixed #28201 -- Added ProhibitNullCharactersValidator and used it on
 CharField form 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/067.c0b8cf0510ce186ff039e68fbd1f7bda%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27849: Add SQL 2003 FILTER syntax support with Case(When()) fallback to aggregates

[Django]

#27849: Add SQL 2003 FILTER syntax support with Case(When()) fallback to 
aggregates
-+-
 Reporter:  Tom  |Owner:  Tom
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   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 Tim Graham ):

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


Comment:

 In [changeset:"b78d100fa62cd4fbbc70f2bae77c192cb36c1ccd" b78d100f]:
 {{{
 #!CommitTicketReference repository=""
 revision="b78d100fa62cd4fbbc70f2bae77c192cb36c1ccd"
 Fixed #27849 -- Added filtering support to aggregates.
 }}}

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

Re: [Django] #23546: Add kwargs support for cursor.callproc()

[Django]

#23546: Add kwargs support for cursor.callproc()
-+-
 Reporter:  fatal10110   |Owner:  felixxm
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  oracle   | 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 GitHub ):

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


Comment:

 In [changeset:"489421b01562494ab506de5d30ea97d7b6b5df30" 489421b]:
 {{{
 #!CommitTicketReference repository=""
 revision="489421b01562494ab506de5d30ea97d7b6b5df30"
 Fixed #23546 -- Added kwargs support for CursorWrapper.callproc() on
 Oracle.

 Thanks Shai Berger, Tim Graham and Aymeric Augustin for reviews and
 Renbi Yu for the initial patch.
 }}}

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

Re: [Django] #28312: ModelChoiceIterator uses cached length of queryset.

[Django]

#28312: ModelChoiceIterator uses cached length of queryset.
-+-
 Reporter:  Sjoerd Job Postmus   |Owner:  Srinivas
 |  Reddy Thatiparthy
 Type:  Bug  |   Status:  assigned
Component:  Forms|  Version:  1.8
 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
-+-
Changes (by Srinivas Reddy Thatiparthy):

 * owner:  nobody => Srinivas Reddy Thatiparthy
 * status:  new => assigned


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

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

Re: [Django] #28451: Change in Oracle sequence name truncation causes regression when updating existing database

[Django]

#28451: Change in Oracle sequence name truncation causes regression when 
updating
existing database
-+-
 Reporter:  Kevin Grinberg   |Owner:  Kevin
 |  Grinberg
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  oracle   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Kevin Grinberg):

 * status:  new => assigned
 * cc: Kevin Grinberg (added)
 * owner:  nobody => Kevin Grinberg


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

Re: [Django] #28073: RemoveField.state_forwards() crashes with AttributeError: 'NoneType' object has no attribute 'is_relation'

[Django]

#28073: RemoveField.state_forwards() crashes with AttributeError: 'NoneType' 
object
has no attribute 'is_relation'
-+
 Reporter:  Logan Gunthorpe  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  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 Tim Graham):

 Can you please provide a sample project that reproduces the problem?

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

Re: [Django] #28073: RemoveField.state_forwards() crashes with AttributeError: 'NoneType' object has no attribute 'is_relation'

[Django]

#28073: RemoveField.state_forwards() crashes with AttributeError: 'NoneType' 
object
has no attribute 'is_relation'
-+
 Reporter:  Logan Gunthorpe  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  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
-+
Changes (by Python Force):

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


Old description:

> Hi,
>
> I'm trying to upgrade my project (originally created on 1.7) to the
> latest release but there's an issue with my existing migration files not
> working. The backtrace is below.
>
> I'll attache my migration files but it seems to be related to the
> migration removing the 'id' field which was automatically created and
> then removed in a future migration. Commenting out the RemoveField in the
> second migration seems to fix the issue but I'm not sure if it's entirely
> correct to do so.
>
> Thanks,
>
> Logan
>

>

> {{{
> Traceback (most recent call last):
>   File "./manage.py", line 10, in 
> execute_from_command_line(sys.argv)
>   File
> "/home/logang/projects/stove/software/website_dev/env/lib/python3.4/site-
> packages/django/core/management/__init__.py", line 363, in
> execute_from_command_line
> utility.execute()
>   File
> "/home/logang/projects/stove/software/website_dev/env/lib/python3.4/site-
> packages/django/core/management/__init__.py", line 355, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File
> "/home/logang/projects/stove/software/website_dev/env/lib/python3.4/site-
> packages/django/core/management/base.py", line 283, in run_from_argv
> self.execute(*args, **cmd_options)
>   File
> "/home/logang/projects/stove/software/website_dev/env/lib/python3.4/site-
> packages/django/core/management/base.py", line 330, in execute
> output = self.handle(*args, **options)
>   File
> "/home/logang/projects/stove/software/website_dev/env/lib/python3.4/site-
> packages/django/core/management/commands/migrate.py", line 163, in handle
> pre_migrate_state =
> executor._create_project_state(with_applied_migrations=True)
>   File
> "/home/logang/projects/stove/software/website_dev/env/lib/python3.4/site-
> packages/django/db/migrations/executor.py", line 81, in
> _create_project_state
> migration.mutate_state(state, preserve=False)
>   File
> "/home/logang/projects/stove/software/website_dev/env/lib/python3.4/site-
> packages/django/db/migrations/migration.py", line 92, in mutate_state
> operation.state_forwards(self.app_label, new_state)
>   File
> "/home/logang/projects/stove/software/website_dev/env/lib/python3.4/site-
> packages/django/db/migrations/operations/fields.py", line 148, in
> state_forwards
> delay = not old_field.is_relation
> AttributeError: 'NoneType' object has no attribute 'is_relation'
>
> }}}

New description:

 Hi,

 I'm trying to upgrade my project (originally created on 1.7) to the latest
 release but there's an issue with my existing migration files not working.
 The backtrace is below.

 I'll attache my migration files but it seems to be related to the
 migration removing the 'id' field which was automatically created and then
 removed in a future migration. Commenting out the RemoveField in the
 second migration seems to fix the issue but I'm not sure if it's entirely
 correct to do so.

 Thanks,

 Logan




 {{{
 Traceback (most recent call last):
   File "./manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "/home/logang/projects/stove/software/website_dev/env/lib/python3.4
 /site-packages/django/core/management/__init__.py", line 363, in
 execute_from_command_line
 utility.execute()
   File "/home/logang/projects/stove/software/website_dev/env/lib/python3.4
 /site-packages/django/core/management/__init__.py", line 355, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/logang/projects/stove/software/website_dev/env/lib/python3.4
 /site-packages/django/core/management/base.py", line 283, in run_from_argv
 self.execute(*args, **cmd_options)
   File "/home/logang/projects/stove/software/website_dev/env/lib/python3.4
 /site-packages/django/core/management/base.py", line 330, in execute
 output = self.handle(*args, **options)
   File "/home/logang/projects/stove/software/website_dev/env/lib/python3.4
 /site-packages/django/core/management/commands/migrate.py", line 163, in
 handle
 pre_migrate_state =
 executor._create_project_state(with_applied_migrations=True)
   

Re: [Django] #23546: Add kwargs support for cursor.callproc() (was: callproc **kwargs or *args parameter)

[Django]

#23546: Add kwargs support for cursor.callproc()
-+-
 Reporter:  fatal10110   |Owner:  felixxm
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle   | 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 Tim Graham):

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

Re: [Django] #23546: callproc **kwargs or *args parameter

[Django]

#23546: callproc **kwargs or *args parameter
-+-
 Reporter:  fatal10110   |Owner:  felixxm
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * has_patch:  0 => 1


Comment:

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

Re: [Django] #26608: Add a window function expression

[Django]

#26608: Add a window function expression
-+-
 Reporter:  Jamie Cockburn   |Owner:  Mads
 |  Jensen
 Type:  New feature  |   Status:  assigned
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 Mads Jensen):

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

Re: [Django] #28334: contrib.postgresql overwhelms database with "select from pg_type" queries on each request

[Django]

#28334: contrib.postgresql overwhelms database with "select from pg_type" 
queries
on each request
-+-
 Reporter:  Igor Gumenyuk|Owner:  Igor
 Type:   |  Gumenyuk
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.postgres |  Version:  1.11
 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
-+-
Changes (by Tim Graham):

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

Re: [Django] #28487: runserver crashes with UncodeDecodeError as of Django 1.11.4

[Django]

#28487: runserver crashes with UncodeDecodeError as of Django 1.11.4
-+-
 Reporter:  newerBkl |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  1.11
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham):

 You can add `print(key, new_environ[key])` before the line with
 `force_bytes(new_environ[key], encoding=encoding)` to see the problematic
 value.

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

Re: [Django] #28073: RemoveField.state_forwards() crashes with AttributeError: 'NoneType' object has no attribute 'is_relation'

[Django]

#28073: RemoveField.state_forwards() crashes with AttributeError: 'NoneType' 
object
has no attribute 'is_relation'
-+-
 Reporter:  Logan Gunthorpe  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.11
 Severity:  Normal   |   Resolution:  needsinfo
 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 Tim Graham):

 I closed #28489 as a duplicate but it's also missing steps to reproduce.

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

Re: [Django] #28489: AttributeError: 'NoneType' object has no attribute 'is_relation' - None is undefined

[Django]

#28489: AttributeError: 'NoneType' object has no attribute 'is_relation' - None 
is
undefined
--+--
 Reporter:  Python Force  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Migrations|  Version:  1.11
 Severity:  Normal|   Resolution:  duplicate
 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 Tim Graham):

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


Comment:

 Looks like a duplicate of #28073. If you can provide steps to reproduce
 such as a sample project, please reopen that 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/067.fcaa1d104ff5e7f3c8b874aacb7cbf1e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26488: migrate crashes when renaming a multi-table inheritance base model

[Django]

#26488: migrate crashes when renaming a multi-table inheritance base model
-+-
 Reporter:  Christopher  |Owner:  nobody
  Neugebauer |
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Markus Holtermann):

 Looks like using a `AlterModelBases` operation wouldn't cut it in the
 given case as the bases alteration needs to happen as part of the
 `RenameModel` operation.

 
[https://github.com/MarkusH/django/commit/b7bf79ed38bb1a5d730c9b106ef6e5819ebb3a4e
 Here] is a very early patch including debugging output and some other
 cruft that wouldn't be part of a proper patch that does not work on
 SQLite, yet.

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

Re: [Django] #26488: migrate crashes when renaming a multi-table inheritance base model

[Django]

#26488: migrate crashes when renaming a multi-table inheritance base model
-+-
 Reporter:  Christopher  |Owner:  nobody
  Neugebauer |
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Markus Holtermann):

 * version:  1.9 => master
 * needs_tests:  0 => 1


Comment:

 So, this is due to the fact that Django doesn't have a way to alter model
 bases. For whatever reason. I don't have a solution at hand right now. But
 there are a few other tickets (one being #23521) that suffer from the same
 issue.

 Idea for a solution:
 * add `AlterModelBases` migration operation
 * extend autodetector to detect model bases changes

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

Re: [Django] #26488: migrate crashes when renaming a multi-table inheritance base model

[Django]

#26488: migrate crashes when renaming a multi-table inheritance base model
-+-
 Reporter:  Christopher  |Owner:  nobody
  Neugebauer |
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.9
 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 Markus Holtermann):

 When I try to run `makemigrations` after *step 0* with the code you
 provided I get the following system check failure:
 {{{
 $ ./manage.py makemigrations
 SystemCheckError: System check identified some issues:

 ERRORS:
 ticket26488.SubModel.basemodel_ptr: (fields.E007) Primary keys must not
 have null=True.
 HINT: Set null=False on the field, or remove primary_key=True
 argument.
 }}}

 Further, neither steps 0-2 nor steps 1-2 work for me. It comes down to
 `django.core.exceptions.FieldError: Auto-generated field 'basemodel_ptr'
 in class 'SubModel' for parent_link to base class 'BaseModel' clashes with
 declared field of the same name.` both times.

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

Re: [Django] #28468: Template braces within {% include ... with="..." %} are not evaluated

[Django]

#28468: Template braces within {% include ... with="..." %} are not evaluated
-+--
 Reporter:  Liquid Scorpio   |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Template system  |  Version:  1.11
 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 Liquid Scorpio):

 Fair Enough. However, any suggested approach to get the desired output?

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

Re: [Django] #28487: runserver crashes with UncodeDecodeError as of Django 1.11.4

[Django]

#28487: runserver crashes with UncodeDecodeError as of Django 1.11.4
-+-
 Reporter:  newerBkl |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  1.11
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by newerBkl):

 Replying to [comment:1 Tim Graham]:
 > What's the key/value of the environment variable that's causing the
 crash?

 I have no idea, it's just a new project without my own code and the
 traceback doesn't give me any ideas about the cause.

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

Re: [Django] #28219: Ease locating origin of queryset paginator warnings

[Django]

#28219: Ease locating origin of queryset paginator warnings
--+
 Reporter:  Denise Mauldin|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  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 Simon Charette):

 FWIW the re-warning approach could eventually be used if
 [https://www.python.org/dev/peps/pep-0550/ PEP 505] gets adopted as it
 would make `warnings.catch_warnings()` safe to use in multi-threaded
 environments.

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