You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(The current behavior is to ignore the attrs kwarg)
Looking back in time, I see this discussion: #121. It seems attrs as a kwarg was not pursued because of concerns about matching the behavior of hdf5? How relevant is that concern today>
The text was updated successfully, but these errors were encountered:
Hi @d-v-b, sorry you didn't get a reply to this at the time.
#121 got closed because the original complaint was that '.zattrs' got written twice when you create an array then set attributes. We resolved that by modifying the library so that '.zattrs' was created lazily the first time the user tried to write some attributes.
However I can see that it would be convenient to also support attrs in the array creation functions, so no objection from me to adding support for that.
Is there any reason why it's not possible to set the attrs of an array / group by passing a kwarg to the relevant creation function? e.g.:
(The current behavior is to ignore the
attrskwarg)Looking back in time, I see this discussion: #121. It seems attrs as a kwarg was not pursued because of concerns about matching the behavior of hdf5? How relevant is that concern today>
The text was updated successfully, but these errors were encountered: