Django: Reasonable to store session data in Class Variable?
I see a lot of reasons not to do it.
I'm sure caching solutions offer robust solutions to memory management.  This includes running as a daemon.  Having cache invalidation, setting lifetimes on the data. 
By setting a classvariable, you are forgoing the above things.  
Additionally, caching solutions provide a clean documented, api for interfacing with them.
I have a class which parses multiple urls/feeds
and stores hashes of entries. Formerly I had put the hashes into a session variable,
but instead of hitting the db I now switched to a class variable in the form of {request.user.id : [hashes]}. Is this bad practice? Any reasons against it?