-
-
Notifications
You must be signed in to change notification settings - Fork 900
-
-
Notifications
You must be signed in to change notification settings - Fork 900
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
configure() explodes #403
Comments
I've found this bug too. Fix for this bug contains in master branch but package from pypi has 2015-10-23 date. |
Please, update PYPI and close this issue. |
I am looking into making a new release. The project is currently set to 3.0-dev, but this would be a 2.2 release, as the only changes I see are fixes and clarifications. @mitsuhiko +1? |
I haven't had time to review the current state of the repo in a while, but as long as all the tests are passing and the changelog is updated then we should be fine. |
All tests are passing. The plan is to review the CHANGES file, update references from 3.0 to 2.2, then cut a 2.2 release against what is currently in master. |
Release 2.3 is out. I'm assuming, since the fix was in master, that this issue has therefore been resolved. If not, feel free to correct me and I'll re-open this issue. |
Calling
db.session.configure(expire_on_commit=True)
in the latest version in git blows up:The text was updated successfully, but these errors were encountered: