On Fri, Dec 23, 2005 at 08:10:43PM +0100, Daniel Baumann wrote:

> No surprise if you use parts of libextractor-python 0.5.4 on 0.5.2. Wait
> until we upgraded to the newever version.

Where did you get that idea from ?

I searched for example code or minimal docs on 0.5.2. I
found none locally. So I went to the web and googled but
found none. So I downloaded the source package from the web
site (which was 0.5.4). It contained a three-liner Python
example on how to use libextractor-python. I happened to
think to myself that 0.5.2 was close enough to 0.5.4 to
warrant assuming that the *most basic* API of the package
would be the same.

I then filed two bug reports:

1) there are no docs on usage to be found in the official 0.5.2 deb

2) going by docs that are two minor-minor versions ahead
   0.5.2 cannot be made to work

The latter may of course possibly be due to an API change
between 0.5.2 and 0.5.4. However, using standard Python
introspection (such as __dict__, __doc__ and friends) did
not show any obvious API either. So I reported the package
to not work.

Now, I'd be interested in how you suggest people go about
finding out how 0.5.2 works ?

Don't assume users are stupid. Not everything is pilot error.

Frohe Weihnachten,

Karsten Hilbert, MD, PhD
Leipzig, Germany
GNUmed lead developer
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to