<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Jun 11, 2014, at 10:21 AM, Jonathan Vanasco <<a href="mailto:twisted-python@2xlp.com">twisted-python@2xlp.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jun 11, 2014, at 1:23 AM, Glyph wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=us-ascii"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">You might want to just try using SQLAlchemy via <<a href="https://pypi.python.org/pypi/alchimia">https://pypi.python.org/pypi/alchimia</a>> if you don't want to do your own thread-pool management as buildbot appears to be.</div></blockquote><div><br></div><div>thanks.</div><div><br></div><div>i think we might need to go the buildbot route.</div><div><br></div><div>we mainly use SqlAlchemy ; our twisted apps are under 5% of our code.</div><div><br></div><div>alchimia looks to be headed in the direction of what we always wanted ( to get sqlalchemy in twisted ), but not quite there yet. i think it would be too confusing right now to have 2 separate sqlalchemy packages in-house.</div></div></div></blockquote><br></div><div>alchimia is not a re-implementation or a separate sqlalchemy package. It *is* sqlalchemy; it's just a slight extension for integration sqlalchemy operations with the Twisted main loop.</div><div><br></div><div>-glyph</div></body></html>