<br><br><div><span class="gmail_quote">On 12/19/06, <b class="gmail_sendername">Guido van Rossum</b> <<a href="mailto:guido@python.org">guido@python.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 12/19/06, Brett Cannon <<a href="mailto:brett@python.org">brett@python.org</a>> wrote:<br>><br>><br>> On 12/19/06, Guido van Rossum <<a href="mailto:guido@python.org">guido@python.org</a>> wrote:<br>
> > On 12/19/06, Georg Brandl <<a href="mailto:g.brandl@gmx.net">g.brandl@gmx.net</a>> wrote:<br>> > > Okay, I updated the patch at SF. While you're at it, in PEP 3100 there's<br>> > > "compile(): put in sys (or perhaps in a module of its own)". I guess
<br>> that<br>> > > isn't really necessary either...<br>> ><br>> > Hm, I think it would be fine to move, it's pretty specialized. What do<br>> > others here think?<br>><br>> Move it, I just wonder if there is a better place for it than sys. Putting
<br>> intern() in sys makes sense since it is a specific thing to the interpreter.<br>> id could go there or maybe inspect.<br>><br>> But compile (along wth exec, but I don't think you wanted to move that) are
<br>> just plain different. Dynamic code execution is its own thing that I do not<br>> directly associate with the specifics of the interpreter. Maybe a module<br>> named 'dynamic' or 'execution'?
<br><br>Well, sys is pretty much a grab-bag.</blockquote><div><br>That is very true. =) I talked about breaking it up. Still want to see a PEP on that someday?<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
And you can't tell me that<br>compile() isn't a hook into system internals. :-) (The compiler in<br>this case.)</blockquote><div><br>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.
<br><br>-Brett<br></div><br></div>