A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2001-January/011412.html below:

[Python-Dev] Add __exports__ to modules

[Python-Dev] Add __exports__ to modules [Python-Dev] Add __exports__ to modulesTim Peters tim.one@home.com
Mon, 8 Jan 2001 03:17:59 -0500
[Greg Stein]
> Simple question: so what?
>
> "Oh, no! My module exposes mod.sys! Oh, woe is me!"  *snort*

Couldn't care less about the module author.  It's the module user who has to
sort this stuff out.  "Don't use 'import *'" is good advice but not followed
either, and after I do

from MyPackage import sys  # intentionally exports its own sys
from GregSnort import *    # accidentally exports some other sys

madness ensues.  Like I said, it's inelegant, and at best.

Simple question for you:  what would __exports__ hurt?  "Oh, no!  Tim's
module explicitly lists what it intended to export!  Oh, woe is me!".  Gimme
a break.




RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4