It never fails (bsddb retirement in 2.3)

Nick Vargish nav at adams.patriot.net
Mon May 5 13:35:29 EDT 2003


Andrew MacIntyre <andymac at bullseye.apana.org.au> writes:

> In retrospect, I think a slightly less painful approach would have been to
> import PyBSDDB as bsddb3, and just deprecate the original bsddb (letting
> it wither except on those systems that absolutely insist).  Too late now I
> think.

I know this would have been preferrable in my situation. A
"deprecation" warning would have helped quite a bit, both by allowing
the existing code to continue working, and giving me some time to
understand all the issues involved before freaking out. I'm not
totally sure it would have averted my original post, but it would have
been more of a considered freak-out and less of the sky-is-falling
kind.

Nick

-- 
#include<stdio.h> /* SigMask 0.3 (sig.c) 19990429 PUBLIC DOMAIN "Compile Me" */
int main(c,v)char *v;{return !c?putchar(*v-1)&&main(0,v+ /* Tweaks welcomed. */
1):main(0,"Ojdl!Wbshjti!=obwAqbusjpu/ofu?\v\1");}  /* build: cc -o sig sig.c */




More information about the Python-list mailing list