Just as an example to how the absent of communication has led to porrer-and-unnecessary implementation(s):
In we2py_utils, I've seen Thadeus used 'sqlight:memory' in the connection-string. This completely circumvent the entire issue that many implementations I had seen have been hammering on - the issue of having to clear-out the fixtures on each test-session-setup, and the issue of having an sqlight-file locked by another process. When you use an in-memory instance of sqlight in your setup-implementation, you are completely avoiding such issues, AND it's faster AND simpler. A centralized-location for consolidation of such conclusions would have prevented this duplicated-and-redundant-effort from occuring in the first place. The web2py_utils project is from 2011, so this means that solutions to issues have been missed by some people, even though (or perhaps "because") they had been done a long time ago. -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
