[Python-ideas] working on a PEP for the __preview__ package
anacrolix at gmail.com
Tue Jan 3 15:57:26 CET 2012
Just a suggestion:
Golang uses an "exp" namespace, this would translate to a exp package
for grouping like modules in a similar way that xml, http and
concurrent are currently used.
The name is unoffensive, and somewhat more palatable than __preview__,
which really isn't a protocol, or a bag for special interpreter
switches like __future__.
Under this scheme, the currently proposed modules would be:
Either way I really look forward to something for PEP 3153 being trialed.
On Tue, Jan 3, 2012 at 3:32 PM, Nick Coghlan <ncoghlan at gmail.com> wrote:
> On Tue, Jan 3, 2012 at 1:08 PM, Eli Bendersky <eliben at gmail.com> wrote:
>> I plan to take the ideas discussed in the thread on the
>> __experimental__/__preview__ package (1), and further elaborated by
>> Nick Coghlan in (2), and turn it into a PEP. Further, I'm willing to
>> invest the time resources to make the package release-worthy before
>> Alpha 1 of 3.3, with at least one module in it. This work will be done
>> under the mentorship of Nick Coghlan.
>> Any ideas, suggestions or objections are welcome.
> I think one thing that needs to be made crystal clear (both in the PEP
> and in the documentation for the namespace) is that anyone attempting
> to combine the preview namespace with persistence mechanisms that rely
> on module names are setting themselves up for migration problems in
> the future.
> It isn't just the case that the __preview__ namespace APIs *might*
> change: they're actually *guaranteed* to change, when they move to
> their final location (probably, but not necessarily, in the next
> Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
> Python-ideas mailing list
> Python-ideas at python.org
More information about the Python-ideas