On May 24, 10:37 am, Russell Keith-Magee
wrote:
>
> We will be sprinting at the conference on Thursday and Friday. If you
> have a detailed proposal that would benefit from some round-table
> discussion while several core developers are in the same room, please
> post your
I've uploaded some screenshots [1] of the new patch for #13163 [2] and
#13165 [3] in action, to allow people to see the affect without
necessarily applying the changes.
These enhancements have *vastly* improved the navigability of the
admin interface between related objects.
Please have a look
Awesome! Congrats guys!
Dhruv Vinodrai Adhia
http://www.thirdimension.com
On Mon, May 24, 2010 at 12:33 PM, James Bennett wrote:
> Following up on last week's Django 1.2 release, today we'd like to
> announce Django 1.2.1, the first bugfix release in the 1.2 series:
>
>
Following up on last week's Django 1.2 release, today we'd like to
announce Django 1.2.1, the first bugfix release in the 1.2 series:
* Announcement blog post: http://www.djangoproject.com/weblog/2010/may/24/121/
* Download: http://www.djangoproject.com/download/
* Checksums:
You could always use a proxy model instead of monkey patching.
class MyUser(User):
class Meta:
proxy = True
ordering = ('first_name', 'last_name')
def __unicode__(self):
return self.get_full_name()
Then in any models you define a FK to User, just FK to MyUser instead.
On Fri,
Hi all,
This is a reminder to everyone that DjangoCon.eu is on during this
week. Jacob, Jannis, myself, and several other prominent django-dev
contributors are in Berlin, and as a result, we may not be able to pay
as much attention to django-dev as would would normally.
So - if you post a Grand
Hi,
Several people have expressed interest in ticket #12831, which has
also been marked as DDN. So I thought the next step would be to bring
it up on this list - let me know if that's not the right thing to do.
Basically, I think that it would make sense and that it would be very
useful if a new