Marc Brinkmann

In closing, I've checked on `#postgres` on IRC, here's my final assessment: - It's an issue because transaction isolation is not enough, actual SQL `MERGE`/upserts are needed in simplekv. -...

@macrojames, @eMerzh: Can you supply some debugging output? Possibly even a small test case?

I am grateful for any reproducible test case. Unfortunately, I have not run into the issue myself yet, which makes it hard to pin down and fix.

I haven't followed up on this, as I am still without a reproducible problem =). @etscrivner Details would be appreciated. @mmautner Do you run into this issue as well? If...

> @mbr Anything new about this? I'm using flask's default client side session, but I'm also faceing a similar issue that some user logs into another's account with no reason...

@jeffcwang I'm afraid that will, at best, mask the problem by silencing the error. If User A uses Session X and it gets replaced by User B's session, also with...

> If you have any new suggestions on better fix, please let me know. The issue is I am fairly stumped at this point. Noone seems to be able to...

Currently, the serialization code is supposed to be protocol-agnostic (you can swap it out with JSON or anything else), adding this configuration option would change that slightly and it is...

> The KVSessionInterface class has the serialization_method hard coded with pickle, so I think it would be OK to have an optional way to pass in the pickling protocol you...

Python2.6 is somewhat of an issue - it's very annoying to support, 2.7 has been out for two years now and I rarely run into it myself. Officially, it is...