From: Andrew S. <str...@as...> - 2004-11-30 20:13:23
|
Given that I'm an "interested and intermittent" user, not a "hardcore, must have" user, please don't rank my responses as highly as others'. Also, I've only answered the questions that I feel even remotely qualified or interested to answer. (You may take my other answers as "0".) >- Image support (in the sense stated in > http://hdf.ncsa.uiuc.edu/HDF5/doc/ADGuide/ImageSpec.html). > > Sounds great +1 In conjunction with releasing Python GIL on file write operations: +5 This might make me a hardcore user if I convert my primitive home-brew "movie" code. But this would require releasing the Python GIL on writing the data to HDF5 files. This would allow a multi-threaded Python program to continue working while the (non-Python API using) C code completes. Refer to our previous conversation: http://sourceforge.net/mailarchive/forum.php?thread_id=4963045&forum_id=13760 My email (at sourceforge time 2004-06-22 00:04) describes the (seemingly fairly simple) necessary changes. (Sorry, if you've done this already -- I haven't kept up with the changes in the last few months.) >- Full index-based searches in Tables (right now, you can only set one > condition in index-accelerated searches). > > Sounds good, but not informed enough to judge (+1?) >- Which present limitations do you find more annoying? > > (Sorry to keep kicking a dead horse.) Keeping the GIL in long file write operations where the Python API is not touched and therefore it could be released. >- In which field of engineering, science or business are you using > PyTables? > > Neuroscience. |