Re: Renaming the postgresql_psycopg2 backend

[Baptiste Mispelon]

I finally got around to creating a ticket for this: 
https://code.djangoproject.com/ticket/25175


On 07/15/2015 03:30 PM, Collin Anderson wrote:
We definitely should make sure postgresql_psycopg2 still works as 
expected. As a data point, Heroku uses "postgres" instead of 
"postgresql" in their DATABASE_URL scheme. Maybe we could support all 
three? :)


On Wednesday, July 15, 2015 at 9:17:30 AM UTC-4, Baptiste Mispelon wrote:

Hi everyone,

After starting a new project recently and failing three times to type
the name of the postgres backend correctly, I was wondering if
there's
really any value in keeping around this strange name.

 From what I understand, it's a historical artifact from a time when
there was more than one postgres backend.


Could we at least make it an alias of a more simply named
"postgresql"
backend?


Thanks,
Baptiste

--
You received this message because you are subscribed to the Google 
Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to django-developers+unsubscr...@googlegroups.com 
.
To post to this group, send email to 
django-developers@googlegroups.com 
.

Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/3ab4f912-fc25-4859-bd8d-5651e2c68e93%40googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups "Django 
developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/55B49865.9050408%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Should migrations have their imports sorted?

[Raphael Michel]

Am Sat, 25 Jul 2015 16:32:21 -0700 (PDT)
schrieb Tim Graham :
> I think it's been addressed in 1.9 to at least some extent. See 
> https://github.com/django/django/commit/7f20041bca43ca33f0a9617793f2af7ab07c3fab

Oh, I didn't find that. Wonderful, sorry for the noise :)

Raphael

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/20150726110721.557235cc%40kvothe.
For more options, visit https://groups.google.com/d/optout.


pgpA742XfliXB.pgp
Description: Digitale Signatur von OpenPGP

Dynamic inlines for Django ModelAdmin

[Gert Steyn]

Hi All

I've been using Django since before newforms-admin and have seen ModelAdmin 
gradually becoming more customization. I often use dynamic inlines (based 
on the state of the object) and would like to clean up the implementation a 
bit.

I would like to open a ticket to add:

def get_inlines(self, request, obj=None):
return self.inlines

to ModelAdmin and then change

def get_inline_instances(self, request, obj=None):
inline_instances = []
for inline_class in *self.inlines*:

to

def get_inline_instances(self, request, obj=None):
inline_instances = []
for inline_class in *self.get_inlines(request, obj=obj)*:

Any reasons not to do this?

Regards
Gert

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/3934ce43-4004-446e-a0fc-616803112ac1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.