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/2010-March/098046.html below:

[Python-Dev] Draft PEP on RSON configuration file format

[Python-Dev] Draft PEP on RSON configuration file formatPatrick Maupin pmaupin at gmail.com
Mon Mar 1 01:59:16 CET 2010
On Sun, Feb 28, 2010 at 6:29 PM, Benjamin Peterson <benjamin at python.org> wrote:
> In that case, it should live in the user space for several years. If
> the community decides that it is an excellent format, then it should
> be considered for inclusion in the stand library.

Agreed.

However, there are too many things which became de facto standards
without community input this way.  PEP 1 itself says:

Reference Implementation -- The reference implementation must be
completed before any PEP is given status "Final", but it need not be
completed before the PEP is accepted. It is better to finish the
specification and rationale first and reach consensus on it before
writing code.

So, I do not mind the code sitting outside the standard library, and
the PEP not reaching "Final" for several years, but I do believe that
the PEP process is itself a really good way to build a better
mousetrap by consensus.

If you do not care to participate in the building of this particular
mousetrap, that is OK, too.

Regards,
Pat
More information about the Python-Dev mailing list

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