Re: [Sqlalchemy-tickets] [sqlalchemy] #1437: rip off collections.namedtuple for Query so that it ca
Brought to you by:
zzzeek
From: sqlalchemy <mi...@zz...> - 2009-11-03 04:49:41
|
#1437: rip off collections.namedtuple for Query so that it can be pickled ---------------------------------+------------------------------------------ Reporter: zzzeek | Owner: zzzeek Type: defect | Status: closed Priority: high | Milestone: 0.6.0 Component: orm | Severity: major - 1-3 hours Resolution: fixed | Keywords: namedtuple Status_field: not decided upon | ---------------------------------+------------------------------------------ Changes (by zzzeek): * status: new => closed * resolution: => fixed * milestone: 0.5.xx => 0.6.0 Comment: collections.namedtuple is not even pickleable. in 0.6 we are using a new tuple that just has a module-level class. -- Ticket URL: <http://www.sqlalchemy.org/trac/ticket/1437#comment:1> sqlalchemy <http://www.sqlalchemy.org/> The Database Toolkit for Python |