Re: [Django] #7145: 'NoneType' object has no attribute 'year' in admin change list when using date_hierarchy with a date field with null values

[Django]

#7145: 'NoneType' object has no attribute 'year' in admin change list when using
date_hierarchy with a date field with null values
-+-
 Reporter:  Eric Walstad |Owner:  nobody
     |   Status:  closed
 Type:  Uncategorized|  Version:  master
Component:  contrib.admin|   Resolution:
 Severity:  Normal   |  worksforme
 Keywords:   | Triage Stage:
Has patch:  1|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by dfraser@…):

 I had this problem and the cause turned out to be a date of -00-00 and
 thus an exception at

 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/django/contrib/admin/templatetags/admin_list.py in
 date_hierarchy, line 350

 occurred because of the None value at the head of the list of possible
 years.  The relevant column in the table was defined as NOT NULL, so this
 is a MySQL related issue due to its defaults and the complexity resulting
 from them.  Forcing a crash would be good because it makes one clean up
 the data, but a date of -00-00 might be valid in some sense, so
 perhaps the code in admin_list.py should change?

 I decided having a value of "unknown" was more appropriate given how the
 field was used, so I decided not to use the date_hierarchy feature.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #7145: 'NoneType' object has no attribute 'year' in admin change list when using date_hierarchy with a date field with null values

[Django]

#7145: 'NoneType' object has no attribute 'year' in admin change list when using
date_hierarchy with a date field with null values
-+-
 Reporter:  Eric Walstad |Owner:  nobody
     |   Status:  closed
 Type:  Uncategorized|  Version:  master
Component:  contrib.admin|   Resolution:
 Severity:  Normal   |  worksforme
 Keywords:   | Triage Stage:
Has patch:  1|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by simon29):

 @daniellindsley- perhaps you could share the details of the "data problem"
 that causes the error?

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #7145: 'NoneType' object has no attribute 'year' in admin change list when using date_hierarchy with a date field with null values

[Django]

#7145: 'NoneType' object has no attribute 'year' in admin change list when using
date_hierarchy with a date field with null values
-+-
 Reporter:  Eric Walstad |Owner:  nobody
     |   Status:  closed
 Type:  Uncategorized|  Version:  master
Component:  contrib.admin|   Resolution:
 Severity:  Normal   |  worksforme
 Keywords:   | Triage Stage:
Has patch:  1|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

 * status:  reopened => closed
 * resolution:   => worksforme


Comment:

 Please don't reopen tickets anonymously without providing any details. If
 the problem still exists in 1.4, I recommend to file a new ticket with
 enough information for someone else to reproduce it. Thanks!

 See the [https://docs.djangoproject.com/en/dev/internals/contributing
 /bugs-and-features/#reporting-bugs guidelines on reporting bugs] for
 advice on what a good bug report looks like.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #7145: 'NoneType' object has no attribute 'year' in admin change list when using date_hierarchy with a date field with null values

[Django]

#7145: 'NoneType' object has no attribute 'year' in admin change list when using
date_hierarchy with a date field with null values
-+-
 Reporter:  Eric Walstad |Owner:  nobody
     |   Status:  reopened
 Type:  Uncategorized|  Version:  master
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by anonymous):

 * status:  closed => reopened
 * severity:   => Normal
 * resolution:  worksforme =>
 * easy:   => 0
 * ui_ux:   => 0
 * type:   => Uncategorized


Comment:

 is ind 1.4

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #7145: 'NoneType' object has no attribute 'year' in admin change list when using date_hierarchy with a date field with null values

[Django]

#7145: 'NoneType' object has no attribute 'year' in admin change list when using
date_hierarchy with a date field with null values
--+-
  Reporter:  Eric Walstad   | Owner:  
nobody
Status:  closed   | Milestone:  1.3 
  
 Component:  django.contrib.admin |   Version:  SVN 
  
Resolution:  worksforme   |  Keywords:  
  
 Stage:  Unreviewed   | Has_patch:  1   
  
Needs_docs:  0|   Needs_tests:  0   
  
Needs_better_patch:  0|  
--+-
Comment (by daniellindsley):

 Sorry for reopening. After updating & addressing a data problem,
 worksforme. Wish I could set the status to
 "embarassingwasteofcoredevtime".

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #7145: 'NoneType' object has no attribute 'year' in admin change list when using date_hierarchy with a date field with null values

[Django]

#7145: 'NoneType' object has no attribute 'year' in admin change list when using
date_hierarchy with a date field with null values
--+-
  Reporter:  Eric Walstad   | Owner:  
nobody
Status:  closed   | Milestone:  1.3 
  
 Component:  django.contrib.admin |   Version:  SVN 
  
Resolution:  worksforme   |  Keywords:  
  
 Stage:  Unreviewed   | Has_patch:  1   
  
Needs_docs:  0|   Needs_tests:  0   
  
Needs_better_patch:  0|  
--+-
Changes (by russellm):

  * status:  reopened => closed
  * resolution:  => worksforme

Comment:

 Works for me; Provided test cases pass for me on trunk and 1.2.X.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #7145: 'NoneType' object has no attribute 'year' in admin change list when using date_hierarchy with a date field with null values

[Django]

#7145: 'NoneType' object has no attribute 'year' in admin change list when using
date_hierarchy with a date field with null values
--+-
  Reporter:  Eric Walstad   | Owner:  
nobody
Status:  reopened | Milestone:  1.3 
  
 Component:  django.contrib.admin |   Version:  SVN 
  
Resolution:   |  Keywords:  
  
 Stage:  Unreviewed   | Has_patch:  1   
  
Needs_docs:  0|   Needs_tests:  0   
  
Needs_better_patch:  0|  
--+-
Changes (by daniellindsley):

  * has_patch:  0 => 1
  * needs_tests:  1 => 0

Comment:

 I uploaded both a 1.2 & 1.3 version of the patch. However, the 1.3 is
 tests-only, as the same bug doesn't seem to be present in 1.3.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #7145: 'NoneType' object has no attribute 'year' in admin change list when using date_hierarchy with a date field with null values

[Django]

#7145: 'NoneType' object has no attribute 'year' in admin change list when using
date_hierarchy with a date field with null values
--+-
  Reporter:  Eric Walstad   | Owner:  
nobody
Status:  reopened | Milestone:  1.3 
  
 Component:  django.contrib.admin |   Version:  SVN 
  
Resolution:   |  Keywords:  
  
 Stage:  Unreviewed   | Has_patch:  0   
  
Needs_docs:  0|   Needs_tests:  1   
  
Needs_better_patch:  0|  
--+-
Changes (by daniellindsley):

  * status:  closed => reopened
  * resolution:  duplicate =>
  * needs_tests:  0 => 1
  * milestone:  => 1.3

Comment:

 Sorry, but this was not a duplicate of #7147. It is still a bug as of
 Django 1.2.X.

 Fixing it to omit null dates is easy but creating a test for it is proving
 difficult. I'll try to upload a patch shortly.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.