On Fri, Aug 13, 2010 at 7:38 PM, Thomas Guettler wrote:
> burc...@gmail.com wrote:
>> Hi,
>>
>> On Thu, Aug 12, 2010 at 9:54 PM, Thomas Guettler wrote:
>>> Hi,
>>>
>>> a colorized debug page helps a lot. More than 99% of errors
>>> are in my code, and not in
On Aug 13, 7:39 pm, Russell Keith-Magee
wrote:
> Looks good -- I've marked RFC; I'll commit when I get a chance.
Thanks a lot!
Best,
Aaron
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group,
On Sat, Aug 14, 2010 at 6:44 AM, Aaron T. Myers wrote:
> Hello all,
> I was very impressed with the responsiveness to my initial patch for ticket
> #14002. However, no one's taken a look at my updated patch addressing the
> review comments. Would some one mind taking a look?
Hello all,
I was very impressed with the responsiveness to my initial patch for ticket
#14002. However, no one's taken a look at my updated patch addressing the
review comments. Would some one mind taking a look? Thanks a lot.
http://code.djangoproject.com/ticket/14002
Best,
Aaron
--
You
Came across this issue that was introduced with model validation:
http://code.djangoproject.com/ticket/14102
Would love a review.
Travis
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to
burc...@gmail.com wrote:
> Hi,
>
> On Thu, Aug 12, 2010 at 9:54 PM, Thomas Guettler wrote:
>> Hi,
>>
>> a colorized debug page helps a lot. More than 99% of errors
>> are in my code, and not in django's. This patch gives "own" code
>> a different color.
>>
>> It is assigned to
On 08/11/2010 09:51 PM, Paul McMillan wrote:
I think this is somewhat ameliorated by being able to link to the
current trunk documents these days. Many incoming links will be going
there. Additionally, for old documents, there is the "these docs are
old" message at the top.
When I google, I