threading.local causes leaks in multithreaded connection pool

Bug #715490 reported by Volkan Gürel
This bug report is a duplicate of:  Bug #530229: Client - bogus use of threading.local. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Python Memcached
Won't Fix
Undecided
Unassigned

Bug Description

it would be great to be able to specify whether memcache.Client (and other class in memcache) should inherit from threading.local or object, because if one wants to create a connection pool for a multithreaded process, the Client instances that inherit from threading.local cause connection leaks.

Changed in python-memcached:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.