[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets
Brought to you by:
zzzeek
From: Bitbucket <com...@bi...> - 2014-03-21 02:52:11
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/a22927b80915/ Changeset: a22927b80915 Branch: None User: zzzeek Date: 2014-03-21 03:46:23 Summary: - reword the paragraph which talks about web framework integration for sessions: 1. fix the typo in the paragraph, fixes #2998 2. as zope-sqlalchemy only provides transaction integration and not session scoping, dial back the language here as people are probably using scoped_session with pyramid anyway 3. as I'm going to again start recommending people don't cling to flask-sqlalchemy so hard, take out the word "strongly" from the recommendation. 4. as flask is the only framework I can think of that actually has an explicit SQLAlchemy layer that handles setting up scoped_session, take out the word "most", now it's "some web frameworks" (by which it means "only flask...and flask-sqlalchemy is probably not worth using anyway") Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/cb51fe3ef894/ Changeset: cb51fe3ef894 Branch: rel_0_8 User: zzzeek Date: 2014-03-21 03:51:57 Summary: - reword the paragraph which talks about web framework integration for sessions: 1. fix the typo in the paragraph, fixes #2998 2. as zope-sqlalchemy only provides transaction integration and not session scoping, dial back the language here as people are probably using scoped_session with pyramid anyway 3. as I'm going to again start recommending people don't cling to flask-sqlalchemy so hard, take out the word "strongly" from the recommendation. 4. as flask is the only framework I can think of that actually has an explicit SQLAlchemy layer that handles setting up scoped_session, take out the word "most", now it's "some web frameworks" (by which it means "only flask...and flask-sqlalchemy is probably not worth using anyway") Affected #: 1 file Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. |