I just released SAContext 0.2.1. There are two backward-incompatible changes due to popular demand:
- sac._session_context is now sac.session_context. - "dburi" in a Pylons config file is now "uri"; e.g., "sqlalchemy.default.uri". Waldemar Osuch contributed a patch to fix a couple bugs and make the imports forward compatible with SQLAlchemy 0.4. Get it all at http://sluggo.scrapping.cc/python/sacontext/ Several people have asked whether SAContext is suitable for this or that complicated scenario. I've added the following to the docstring: SAContext is basically a container for your engines, metadatas, and sessions. It helps build applications quickly and avoids common mistakes. It supports multiple databases within one application but may not be suitable for highly complex applications that switch between entire sets of engines at various times. We're doing further research to determine the limits of SAContext's scalability. -- Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
