[yt-dev] RFC: using only explicit imports in core yt

Nathan Goldbaum nathan12343 at gmail.com
Fri Aug 9 23:07:16 PDT 2013


+1

It makes the code hard to approach for newcomers as well.  It definitely
confused me at first.

On Friday, August 9, 2013, Kacper Kowalik wrote:

> Hi,
> I'd like to discuss deprecating glob imports in yt-3.0. Initial work has
> been done in PR68 [1].
>
> Main rationale is that '*' confuses all python static checkers and
> obscures bugs that otherwise would be trivial to find.
>
> I understand that it's onerous and the very reason yt.funcs exists is to
> make devs' live more convenient and allow to easily grab everything
> that's defined there. However, using said yt.funcs as an example, it's
> worth noticing that there are not many modules that grab more than 2-3
> methods from it. That allows me to hope that in the end it won't be such
> a great PITA...
>
> Cheers,
> Kacper
>
>
> [1] https://bitbucket.org/yt_analysis/yt-3.0/pull-request/68/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.spacepope.org/pipermail/yt-dev-spacepope.org/attachments/20130809/50cd555f/attachment.html>


More information about the yt-dev mailing list