On Fri, Dec 14, 2012 at 1:11 PM, Michael Bayer wrote:
> Hi list -
>
> SQLAlchemy 0.8.0b2 is released. This is hopefully the last beta for 0.8,
> as things have been mostly quiet surrounding 0.8.0b1, we had a few
> regressions fixed, and a bunch of other new bugs whose fixes are only in
> 0.8.
>
On Thu, Jun 28, 2012 at 11:45 PM, tonthon wrote:
> Hi,
>
> I was wondering what values to setup for pool_size and pool_recycyle
> parameters.
>
> I think you have to set them up regarding your sql server configuration
> (mysql in my case), but how ?
I can only comment on pool_recycle because I've
With some help from Ned Batchelder I was able to confirm that this is
a Python bug: http://bugs.python.org/issue1569356 that has been fixed
since the 2.5.2 release. Ned confirmed that the fix is included in
Python 2.6a3.
Doug
On Sep 16, 5:22 pm, Doug Latornell <[EMAIL PROTECTED]>
Thanks for the quick replies, Jason and Michael, and for the very
succinct test case. I will try to raise this with Ned Bachelor over
at http://nedbatchelder.com/code/modules/coverage.html
Doug
On Sep 16, 4:55 pm, Michael Bayer <[EMAIL PROTECTED]> wrote:
> On Sep 16, 2008, at 7:25
Over on the TurboGears list a TG2 user pointed out a problem that
arises when nosetests --with-coverage is run on a project with a
sqlalchemy identity model:
http://groups.google.com/group/turbogears/t/7fd3639a5a4d4b8c
I dug into it and have reproduced the problem outside of TurboGears 2
and wit
