[Discuss] SQLAlchemy Has Annoyances

[richard.pieri at gmail.com (Richard Pieri)]

On 2/4/2015 7:02 PM, Kent Borg wrote:
> I was once at a Apple Developers' Conference--a *way* long time ago--and
> Iw ent to a session on debugging. At the beginning they put a slide
> saying that a well written program should be able to run for hours--even
> days!--without crashing. Seemed both radical and obvious.

Seems neither? I mean, I've seen old database systems with uptimes 
measured in years, and one that was approaching a decade at the time 
(and if it's still running then it's a few years away from a second 
decade). A well-written program won't crash. Period.

But regarding SQLAlchemy, that sounds like a Python-ism. You can't 
delete classes in Python. The closest you can get is that a class will 
be reaped by the interpreter when nothing references it (the reference 
count is reduced to 0). Exhaustively walking the chains of references is 
the only way to be certain that all references to the class are eliminated.

-- 
Rich P.