Open pbranson opened 2 months ago
cc @alsonathif
@pbranson yes I think you are right - It is possible to import ... as
but I agree we could avoid this namespace issue altogether by renaming them as you suggest. I can look into it
Thanks @rafa-guedes, we added the as to work around it also, also narrowing the scope of imports is also option.
When working with Alson on a SWAN model setup we started getting validation errors on our previously working CGRID because we had combined imports to the top of the module/notebook so had inadvertently ended up with:
Propose that we should maybe rename them to INPREGULAR and CGRIDREGULAR given that their definition string has different parameters in SWAN also. Thoughts @rafa-guedes?