kylewyg / pydelicious

Automatically exported from code.google.com/p/pydelicious
Other
0 stars 0 forks source link

pydelicious should throw exceptions for errors #6

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Currently pydelicious handles errors like a C library; the functions return
values and the app is supposed to check them for error. Ie, "addPost"
returns True on success and something else on failure. This is unPythonic;
the code should be reworked to throw exceptions indicating failures. This
change will break some existing programs.

Original issue reported on code.google.com by nelson.m...@gmail.com on 17 Feb 2007 at 6:39

GoogleCodeExporter commented 9 years ago
I agree this is the way to go.

Original comment by gregpin...@gmail.com on 17 Feb 2007 at 6:51

GoogleCodeExporter commented 9 years ago
As of revision 17 (0.5.1) should raise DeliciousError on generic False/not-Ok
messages from server, atm with one subclass 'DeliciousItemExistsError'. More 
may be
added whensomeone stumbles over it :)
Okay messages are received 'silently'.

closing this too..

Original comment by berend.v...@gmail.com on 28 Nov 2008 at 4:02