GitHub migration done!

On Fri, Apr 27, 2012 at 11:50 AM, Adrian Holovaty wrote: > We're going to do the migration to GitHub today. This means we'll no > longer be committing code to our Subversion repository. Committers, > please hold off on making commits until the migration is done. OK, it's

Re: More on Customizable Serialization

Hi Tom, On Friday, 27 April 2012 at 12:44 PM, Tom Christie wrote: > Seeing another proposal for Customizable Serialization for the GSoC this year > prompted me to dust off the bits of work I've done along similar lines. > I'd really like to see this get properly addressed in core and I thought

Re: GitHub migration

Wow this is awesome! Congrats on the change! Very excited to be able to contribute a Pull Request or two! On Friday, April 27, 2012 9:50:01 AM UTC-7, Adrian Holovaty wrote: > > Hey guys, here's an important heads-up! > > We're going to do the migration to GitHub today. This means we'll no >

Re: Implementation of Object Permissions

> > Are there any hopes of speeding up or caching GenericForgeinKey queries ? > I found - > http://zerokspot.com/weblog/2008/08/13/genericforeignkeys-with-less-queries/ > > Adding 'db_index=True' to the GenericForeignKey's object_id field should be a significant performance enhancement. It

Re: GitHub migration

On Fri, Apr 27, 2012 at 11:50 AM, Adrian Holovaty wrote: > We're going to do the migration to GitHub today. This means we'll no > longer be committing code to our Subversion repository. Committers, > please hold off on making commits until the migration is done. > > I expect

Will django escaping ever consider context of javascript and CSS?

Hello provides great protection from XSS by escaping output to webpages, but it only does it in HTML context. XSS can be executed when user input is inserted into javascript or CSS, which have different context and rules than HTML, so HTML context escaping doesn't help/protect. Are there any

Django use of stdlib HTMLParser "internals"

Although the Django tests all pass when run for the Python 3 port under Python 3.2, I hit some problems when testing against recent changes in the Python trunk (default branch, which will become 3.3). Looking into these problems, I found that Django subclasses HTMLParser and overrides

Re: Django Admin Revamp - Any updates?

On that note, why can't the fruits of Grappelli be used as a starting point? -Original Message- From: h3 Sent: Friday, April 27, 2012 4:01 PM To: Django developers Subject: Re: Django Admin Revamp - Any updates? I don't know the status of this project, but my guess is that you

Re: Django Admin Revamp - Any updates?

Hey all, Yeah, you aren't missing anything — originally I wanted to wait for the formrendering stuff, but that never panned out, and then I got busy. Grappelli is lovely. Without knocking it at all, I think that the next version of the admin should be as forward-looking as the last version,

Re: Django Admin Revamp - Any updates?

I don't know the status of this project, but my guess is that you shouldn't hold your breath for it. Fortunately, there is Grappelli: https://github.com/sehmaschine/django-grappelli We are currently working on making it compatible with django 1.4 (see the "grappelli_2_4" branch) Alternatively

Re: Problems with date-based generic views when USE_TZ=True

Hi Mike, On 27 avr. 2012, at 14:51, Mike Yumatov wrote: > I wrote a ticket about time zone warnings in date-based generic views: > https://code.djangoproject.com/ticket/18217 It isn't necessary to notify django-developers when you create a ticket; that's the job of django-updates. > After

Re: GitHub migration

woohoo! this is great, good luck Adrian Brendan Smith, IT Specialist National Priorities Project http://www.nationalpriorities.org http://www.facebook.com/nationalpriorities 413 584 9556 On Apr 27, 2012, at 12:50 PM, Adrian Holovaty wrote: > Hey guys, here's an important heads-up! > >

GitHub migration

Hey guys, here's an important heads-up! We're going to do the migration to GitHub today. This means we'll no longer be committing code to our Subversion repository. Committers, please hold off on making commits until the migration is done. I expect it'll be done by late afternoon Chicago time.

Re: Implementation of Object Permissions

Fantastic job on the performance benchmarks, the number 4-5 seconds per check is scary. I’ve posted a comment on django-guradian in hopes the author can chime in onto this conversation by posting https://groups.google.com/forum/#!topic/django-developers/6UNjPu1mcgc/discussion. Are there any

GSoC Check-in: Security Enhancements

Hi, I am Rohan Jain, a student from Indian Institute of Technology, Kharagpur. I'll be doing a Google Summer of Code project with django this year under the title "Security Enhancements". As the title suggests, it has something to do with Security Enhancements: like improvements in CSRF

Problems with date-based generic views when USE_TZ=True

Hi! I wrote a ticket about time zone warnings in date-based generic views: https://code.djangoproject.com/ticket/18217 After some research, I understand that there are more problems with this views, than I thought at first. django.views.generic.dates module uses aware and naive datetime

Re: Customizable Serialization check-in

W dniu 27.04.2012 12:39, Tom Christie pisze: Hey Piotr, > I quickly skimmed the proposal and I noticed speed/performance wasn't mentioned. I believe performance is important in serialization and especially in deserialization. Right. Also worth considering is making sure the API can deal with

Re: Customizable Serialization check-in

Hey Piotr, Thanks for the quick response. > However sharing ideas and discuss how the API should look and work it will be very desirable. That'd be great, yup. I've got a couple of comments and questions about bits of the API, but I'll wait until you've had a chance to post your proposal

Re: Customizable Serialization check-in

W dniu 27.04.2012 10:36, Anssi Kääriäinen pisze: On Apr 27, 11:14 am, Piotr Grabowski wrote: Hi! I'm Piotr Grabowski, student from University of Wroclaw, Poland In this Google Summer of Code I will deal with problem of customizable serialization in Django. You can

Re: Customizable Serialization check-in

On Apr 27, 11:14 am, Piotr Grabowski wrote: > Hi! > > I'm Piotr Grabowski, student from University of Wroclaw, Poland > In this Google Summer of Code I will  deal with problem of customizable > serialization in Django. > > You can find my proposal here

Re: Django UnicodeEncodeError in errorlist

Hi Thomas, You seem read my email too quickly. I do use u'å'. In force_unicode() and lazy() Django runs str(u'å') which results in the exception(s). If it would use smart_str instead, the exception would not happen. Am I missing something? Andrei On Friday, April 27, 2012 9:11:19 AM UTC+2,

[GSoC] Customizable Serialization check-in

Hi! I'm Piotr Grabowski, student from University of Wroclaw, Poland In this Google Summer of Code I will deal with problem of customizable serialization in Django. You can find my proposal here https://gist.github.com/2319638 It's obviously not a finished idea, it's need to be simplified

Re: Django UnicodeEncodeError in errorlist

this question belongs to django-user. You need to use u'å' not 'å' in your python code. > Is there a good reason > why |force_unicode| and |lazy| do not use |smart_str|? smart_str() creates a bytestring, but in Django everything is unicode until the end. Only one of the last steps is to