Pyramid 1.10.1 has been released. This is a very minor bugfix release
fixing a regression in 1.10.
Expect Pyramid 2.x to support only Python 3+ (minor version to be
determined). Pyramid's releases contain python_requires metadata which will
cause pip and other compliant tools to install only the
Thanks Michael,
I’d be glad to have this appear in a cookiecutter – let me know how I can help.
For the record, what I missed to mention (but is actually the bigger selling
point for me):
Apart from the automatic rollback functionality, that approach allows putting
anything to
Andi, I think this is a fantastic approach. The key here is to override
request.dbsession to a mocked out version which is not connected to
pyramid_tm at all, giving you full control of commit/rollback from the
outside. One extra step would be to disable pyramid_tm entirely by setting
Cheers Andi will have a look at PyCharm :)
On Tuesday, 6 November 2018 09:27:50 UTC, Andi Blake wrote:
>
>
>
> Welcome dcs3spp!
>
>
>
> One thing I noted in your snippet was you where using pdb (or ipdb). That
> looks like you’re not using an IDE that is able to debug ;)
>
>
>
> I would
Welcome dcs3spp!
One thing I noted in your snippet was you where using pdb (or ipdb). That looks
like you’re not using an IDE that is able to debug ;)
I would really recommend using PyCharm for such tinkering, cause even the
community version has a well integrated debugger and
Hi Andi,
Thankyou for sharing the fixtures and approach, much appreciated. So the
SQLAlchemy test session is shared in the registry which triggers a bypass
of the pyramid_tm session for the request when testing.
That would solve the problem I have been encountering since, with this
approach
