On Monday, December 20, 2010, Yo-Yo Ma wrote:
> UPDATE:
>
> The BuiltWith team has removed Django because there aren't enough
> clues to accurately detect Django in some circumstances, and they
> didn't want to give bad data. Instead, they've added
> http://trends.builtwith.com/cms/Django-CSRF (wh
On Sun, Dec 19, 2010 at 2:55 PM, Yo-Yo Ma wrote:
>
> From the core team, are there any reliable clues to detect Django that
> are more consistent than naming conventions? CSRF doesn't
> always apply. This tool can also be helpful for those contributors who
> run Django showcase sites, etc.
Many
I developed https://bitbucket.org/mhall119/django-extauth/wiki/Home to
accomplish this same kind of scenario, it can either be used as a Django
1.2 backend with support for object/row level permissions, or using it's
own API on earlier versions of Django.
--
Michael
On Sat, 2010-12-18 at 08:57
UPDATE:
The BuiltWith team has removed Django because there aren't enough
clues to accurately detect Django in some circumstances, and they
didn't want to give bad data. Instead, they've added
http://trends.builtwith.com/cms/Django-CSRF (which basically is
telling you a site uses Django). They're
On Thu, Dec 16, 2010 at 5:23 AM, KentH wrote:
> Any chance this one (#16455) can be reviewed before feature freeze?
Hi Kent,
I've just committed this in r14986.
Thanks for your work on this ticket. For future reference, I've left a
couple of notes on the ticket explaining the relatively minor
d
Hi all,
To be a bit more specific:
I've filed
http://code.djangoproject.com/ticket/14910
Added a test that proves the bug. Provided code that makes that test
green. Fixed the documentation. All including patches.
Could someone with sufficient authority move this forward?
Much obliged,
Klaas
