I thought I would end this standoff by simply going where James pointed, and turning it into the minimal "spec" Alex describes. I know next to nothing about db backends, but it sounded like this was a job for a scribe, not a developer.
Unfortunately, django.db.backends.dummy falls below the bar for minimal API documentation. While it may have the names of the entry points, they are all defined as complain(*args, **kwargs), and they have no docstrings or comments, so there is no guidance about what they expect, do, or produce. Perhaps James mis-spoke: django.db.backends contains base classes, and has much more useful information. --Ned. http://nedbatchelder.com/blog James Bennett wrote: > On Mon, Mar 24, 2008 at 11:15 PM, Alex P <[EMAIL PROTECTED]> wrote: > >> 1. The original message was in brief: there is a growing interest in >> the Python community for DB2 support, and we (developers behind IBM_DB >> driver, DB-API wrapper and SQLAlchemy adapter) are interested to help >> in the Django context if some _minimal_ documentation is provided in >> an unrestricted form, even under a Open Source license like BSD (even >> with sample/example API usage code, for that matter). >> > > The thing is, though, that there *is* a minimal API documented: > django.db.backends.dummy. If this were Java, you could take that as > laying out the interface to be implemented. The confusion came from > the apparent refusal to deal with this because it's in the form of > open-source code. > > > -- Ned Batchelder, http://nedbatchelder.com --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
