replace usages of copy_arrays with memmap

[zacharyburnett]

follow-on to asdf-format/asdf#1797

Checklist

• added entry in CHANGES.rst (either in Bug Fixes or Changes to API)
• updated relevant tests
• updated relevant documentation
• updated relevant milestone(s)
• added relevant label(s)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 66.21%. Comparing base (4d7c3a6) to head (f5c46d7).
Report is 31 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #306      +/-   ##
==========================================
+ Coverage   64.84%   66.21%   +1.37%     
==========================================
  Files         103      101       -2     
  Lines        5694     5402     -292     
==========================================
- Hits         3692     3577     -115     
+ Misses       2002     1825     -177     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[braingram]

Thanks!

Based on https://github.com/spacetelescope/jwst/pull/8660/files the "copy_arrays" usage is very limited in jwst and I see no uses that pass it to DataModel.__init__. It's possible a user might be doing this and it also makes sense to me to remove "copy_arrays" as an allowed keyword argument (eventually).

Would you add a deprecation for passing "copy_arrays" to DataModel.__init__ and a test for the deprecation? I think another UserWarning is called for here since it seems likely to happen in an interactive session. We can then remove "copy_arrays" for stdatamodels 3.0.0

[zacharyburnett]

Thanks!

Based on https://github.com/spacetelescope/jwst/pull/8660/files the "copy_arrays" usage is very limited in jwst and I see no uses that pass it to DataModel.__init__. It's possible a user might be doing this and it also makes sense to me to remove "copy_arrays" as an allowed keyword argument (eventually).

Would you add a deprecation for passing "copy_arrays" to DataModel.__init__ and a test for the deprecation? I think another UserWarning is called for here since it seems likely to happen in an interactive session. We can then remove "copy_arrays" for stdatamodels 3.0.0

Alternatively, we can remove handling copy_arrays entirely and outsource that warning to the AsdfWarning that'll come up when it is passed to asdf.open(); see f5c46d7

[braingram]

Much simpler :) Good idea!