On Fri, 2009-05-01 at 08:47 -0700, codysacoder wrote: > Why not allow both to work (parse the DSN string if encountered)?
That should be an option of last resort. One way to do things, preferably obvious, even if you're not Dutch, and all that jazz. I'd prefer dictionaries to strings, because strings are tough to modify dynamically -- as has already been demonstrated a few times in Django's history. Right now, you have to pass in specific (non-DSN) information to set up a database (in the settings file) and the lower-level API is dictionary based. Introducing DSNs is an option that isn't required. Consistency counts there when trying to choose between two roughly equivalent options. After Simon, Alex, et al have had a discussion at the conference, there'll be a summary and a chance for discussion on this list so we can see if any strong arguments for one option come up there. As you'll see from the thread earlier this week, Simon's reasoning was just that there should be a way to construct things dynamically and he wasn't particularly attached to strings as a concept (so having to arrange for some of the larger conference attendees to help him swim the Vltava at the end of the conference might not be necessary after all). Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
