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
Currently the same block manager is used for all writes of the same AsdfFile object, and it retains state between calls to write_to. This is not good because it leads to confusing and sometimes erroneous behavior with respect to the storage type of certain arrays (see #599 and #618 for one particular example).
When creating an AsdfFile object with the intent to write a new file, there is no need to create a block manager until actually calling write_to. This should help resolve ambiguities without introducing any other user-visible effects.
The text was updated successfully, but these errors were encountered:
#1537 largely rewrote block management. Read and written blocks are now separated. Write blocks are not created until writing and are not shared across writes.
Currently the same block manager is used for all writes of the same
AsdfFile
object, and it retains state between calls towrite_to
. This is not good because it leads to confusing and sometimes erroneous behavior with respect to the storage type of certain arrays (see #599 and #618 for one particular example).When creating an
AsdfFile
object with the intent to write a new file, there is no need to create a block manager until actually callingwrite_to
. This should help resolve ambiguities without introducing any other user-visible effects.The text was updated successfully, but these errors were encountered: