Override the __all__ when importing

@pf_moore Ya, it is hard to offer anything convincing if others haven’t done these sorts of things in the first place. To answer your question though, in a package there would normally be a specification of the versions of other packages that are to be installed when creating a new environment. In an official release to my customer I would never leave it in the blind. In general, an update to a core package could break anyone’s project, regardless if I customized functions or not. Yes, in an online setting (with real-time updating abilities), I can see the mindset of working with an author or participating in a project to provide it the capabilities desired. In my experience I have found myself in too many offline or closed environments. So I am starting to see some bias in my reasoning here.