Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Django developers
Home
+ new post
About this group
Join this group
Message from discussion Low-Hanging Fruit
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Karen Tracey  
View profile   Translate to Translated (View Original)
 More options Apr 19 2010, 10:49 am
From: Karen Tracey <kmtra...@gmail.com>
Date: Mon, 19 Apr 2010 10:49:45 -0400
Local: Mon, Apr 19 2010 10:49 am
Subject: Re: Low-Hanging Fruit
Print | View thread | Show original | Report this message | Find messages by this author

On Mon, Apr 19, 2010 at 10:26 AM, Shawn Milochik <sh...@milochik.com> wrote:
> So, I'm asking for anyone in the core (or close to it) to specifically
> point out any low-hanging fruit.

Off the top of my head, a ticket I saw some activity on recently but have
not had time to look into making a test/fix for:

http://code.djangoproject.com/ticket/10523

Admin raises an exception if the repr of an object that is modified/deleted
is greater than 200 characters. Fix is probably to truncate the object's
repr to the max length of the field it's being put in. (Note this error will
only happen for DBs that actually enforce max_length -- sqlite, for example,
will happily let you store >200 chars in a field declared to only hold a max
of 200. So the test for this will only fail on current code for certain
DBs.) First place I'd likely look to put a test for this would be
regressiontests/admin_views.

Karen

--
You received this message because you are subscribed to the Google Groups "Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to django-developers+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google