follow-up issues in zarr-python

[MSanKeys963]

Linking this from zarr-developers/zarr-python#54. Conversations on some issues have gone stale. Here are issues in zarr-python that need follow-up from the author, and then we can decide the best action to take:

• bug in save for variable length arrays? zarr-python#1035
• Proposal: Add Array.blocks using new BlockIndexer (Prototype Code Included) zarr-python#991
• indexing with list not supported zarr-python#1029
• resize(): Improve docs & control of what is modified zarr-python#1017
• async zarr zarr-python#1104
• Passing dask array to zarr leads to a TypeError zarr-python#962
• bsddb3 is deprecated zarr-python#904
• Surprising N5FSStore test failure n5py#11
• Increase the usage of augmented assignment statements zarr-python#864
• Fail to synchronize zarr-python#784
• Dependabot sends PRs to forks zarr-python#777
• Provide a more informative error when using open_consolidated zarr-python#776
• Read only array default upon opening zarr-python#809

If you think this is in the right category, feel free to follow up on the issue. Thanks!

[joshmoore]

• to-be-reproduced / needs-unit-test (new label)

  • bug in save for variable length arrays? zarr-python#1035
  • 809

• yes, just check in

  • 991
  • 1029
  • 868 (possibly reproduce)
  • 864
  • 777

• maybe close (these are trickier)

  • 1017 (docs, help?)
  • 962 (after asking for comments?) possibly a documentation issue
  • 784 (synchronization is often a tricky one)

• help wanted / good first

  • 904

• needs a review or first comment

  • 776 (suggest a PR?)

[joshmoore]

Updated my comment for all the issues listed here, @MSanKeys963.