Michael Foord writes:
> >> Assuming the module is then promoted to the the standard library proper in
> >> release ``3.X+1``, it will be moved to a permanent location in the library::
> >>
> >> import example
> >>
> >> And importing it from ``__preview__`` will no longer work.
> > Why not leave it accessible through __preview__ too?
>
> +1
Er, doesn't this contradict your point about using
try:
from __preview__ import spam
except ImportError:
import spam
?
I think it's a bad idea to introduce a feature that's *supposed* to
break (in the sense of "make a break", ie, change the normal pattern)
with every release and then try to avoid breaking (in the sense of
"causing an unexpected failure") code written by people who don't want
to follow the discipline of keeping up with changing APIs. If they
want that stability, they should wait for the stable release.
Modules should become unavailable from __preview__ as soon as they
have a stable home.
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