> But, on the other hand, I think a parse_dsn function could easily be > supplied by the user.
Sure, of course. But the question is, "should django support this standard method of expressing DSNs as URIs?" more than "is it possible to use URI-style DSNs in django at all?" The downside to leaving #1810 dead and not including parse_dsn() is that django won't support standard URI-style DSNs out of the box, unlike just about every other package that provides or uses a high-level python database interface. I'd argue that this raises the learning curve for adopters and, unfortunately, contributes a bit to the impression that django has NIH tendencies. Since the work of providing a parse_dsn() that parses out the stuff that django needs, and writing some docs for its use, has already been done (or mostly done if only part of the patch is accepted), my opinion is that there's a lot more weight on the "support" side. JP --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
