Fix circular import on map.read

[Astro-Kirsty]

Resolves #5600

[registerrier]

Thanks @Astro-Kirsty ! Looks good. Can you add a test for this. I am really surprised that an error of something as simple as Map.read was not seen on the CI.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.60%. Comparing base (ccb8bc8) to head (d5dc78b).
Report is 3 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5603   +/-   ##
=======================================
  Coverage   94.60%   94.60%           
=======================================
  Files         232      232           
  Lines       36394    36394           
=======================================
  Hits        34432    34432           
  Misses       1962     1962           

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

---

🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests

[Astro-Kirsty]

Thanks @Astro-Kirsty ! Looks good. Can you add a test for this. I am really surprised that an error of something as simple as Map.read was not seen on the CI.

As we discussed I think it is due to the imports we have, i.e. we import many things in the tests but it was failing specifically when only importing Map. Not sure how we can add a test to catch this?

[registerrier]

Thanks @Astro-Kirsty ! Looks good. Can you add a test for this. I am really surprised that an error of something as simple as Map.read was not seen on the CI.

As we discussed I think it is due to the imports we have, i.e. we import many things in the tests but it was failing specifically when only importing Map. Not sure how we can add a test to catch this?

well technically the existing test on make_map_rgb should be failing already. And the docstring of the function too. The docstring test runs while executing it in an ipython session fails...