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

Kacper Kowalik xarthisius.kk at gmail.com
Fri Aug 9 22:43:44 PDT 2013


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 --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 901 bytes
Desc: OpenPGP digital signature
URL: <http://lists.spacepope.org/pipermail/yt-dev-spacepope.org/attachments/20130810/315f4fb9/attachment.pgp>


More information about the yt-dev mailing list