[Python-3000] Py3k release schedule worries

[Brett Cannon]

On 12/19/06, Guido van Rossum <guido at python.org> wrote:
>
> On 12/19/06, Brett Cannon <brett at python.org> wrote:
> >
> >
> > On 12/19/06, Guido van Rossum <guido at python.org> wrote:
> > > On 12/19/06, Georg Brandl <g.brandl at gmx.net> wrote:
> > > > Okay, I updated the patch at SF. While you're at it, in PEP 3100
> there's
> > > > "compile(): put in sys (or perhaps in a module of its own)". I guess
> > that
> > > > isn't really necessary either...
> > >
> > > Hm, I think it would be fine to move, it's pretty specialized. What do
> > > others here think?
> >
> > Move it, I just wonder if there is a better place for it than
> sys.  Putting
> > intern() in sys makes sense since it is a specific thing to the
> interpreter.
> >  id could go there or maybe inspect.
> >
> > But compile (along wth exec, but I don't think you wanted to move that)
> are
> > just plain different.  Dynamic code execution is its own thing that I do
> not
> > directly associate with the specifics of the interpreter.  Maybe a
> module
> > named 'dynamic' or 'execution'?
>
> Well, sys is pretty much a grab-bag.


That is very true.  =)  I talked about breaking it up.  Still want to see a
PEP on that someday?

And you can't tell me that
> compile() isn't a hook into system internals. :-) (The compiler in
> this case.)


No, but I view sys as place to put stuff that influences the running of the
interpreter and I don't put compile() in that category.

-Brett
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/python-3000/attachments/20061219/2019b70c/attachment.html