anatoly techtonik writes:

 > I am afraid that dunders will become a standard thing in many Python
 > packages, because of everybody's natural desire to use latest features that
 > work right.

__preview__ is for the latest features that have not been confirmed to
work right (yet).  Where's the problem?  Newbies certainly should not
be using such in production applications, although it's an excellent
way to learn everything you always wanted to know about Python
internals but were afraid to ask (and more!) 

What's the point in developing code you won't use? __preview__ features don't have a Roadmap, so you may wait forever to release you package into production. With indefinite release cycle __preview__ will become useless for the most people, who will quickly lose enthusiasm to use __preview__ and continuously update their code for API breaks. 
">

(original) (raw)

On Wed, Jan 4, 2012 at 2:29 PM, Stephen J. Turnbull <stephen@xemacs.org> wrote:
anatoly techtonik writes:

\> I am afraid that dunders will become a standard thing in many Python
\> packages, because of everybody's natural desire to use latest features that
\> work right.

\_\_preview\_\_ is for the latest features that have not been confirmed to
work right (yet). Where's the problem? Newbies certainly should not
be using such in production applications, although it's an excellent
way to learn everything you always wanted to know about Python
internals but were afraid to ask (and more!)

What's the point in developing code you won't use? \_\_preview\_\_ features don't have a Roadmap, so you may wait forever to release you package into production. With indefinite release cycle \_\_preview\_\_ will become useless for the most people, who will quickly lose enthusiasm to use \_\_preview\_\_ and continuously update their code for API breaks.

--
anatoly t.