drop does not delete a bcolz directory

[ltransom]

Calling drop on an existing bcolz data directory results in an RuntimeError:

bcolz/carray_ext.pyx in bcolz.carray_ext.carray.flush (bcolz/carray_ext.c:31412)()
bcolz/carray_ext.pyx in bcolz.carray_ext.chunk.cinit (bcolz/carray_ext.c:4279)()
bcolz/carray_ext.pyx in bcolz.carray_ext.chunk.compress_data (bcolz/carray_ext.c:5222)()

RuntimeError: fatal error during Blosc compression: -1

[cpcloud]

drop is kind of a weird function because it works on strings which then dispatches to resource which then tries to create it or return the existing thing so it will try to create an empty bcolz array without any type information

[mrocklin]

Arguably resource is the odd duck here. It currently serves double duty as "get me the thing corresponding to this string" and "create the thing according to this string. Arguably this could be split?

[cpcloud]

yes

[cpcloud]

we are discussing on gitter

[cpcloud]

well actually i don't think that resource is odd

[cpcloud]

i think drop calling resource without knowing anything about whether the thing exists or not is odd

[cpcloud]

hm, let me think about this