I was just talking to Michael (mhall119) on IRC about threading, and he expressed some concerns regarding the potential for added complexity in putting threading in libkeryx. During the conversation, I came up with an idea for a compromise: write a class in a separate file, threading.py, which would handle threading. Any library/UI that wants to use threading could call it, but it's use would remain optional. What does everyone think of this? - Douglass Clem Chief Technology Officer, Crashsystems LLC (crashsystems.net) Public Key: 37F9 E685 576A CFD3 B08C
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Mailing list: https://launchpad.net/~keryx Post to : [email protected] Unsubscribe : https://launchpad.net/~keryx More help : https://help.launchpad.net/ListHelp
