[Python-3000] Py3k release schedule worries
Guido van Rossum
guido at python.org
Wed Dec 20 03:59:41 CET 2006
More information about the Python-3000 mailing list
Wed Dec 20 03:59:41 CET 2006
- Previous message: [Python-3000] Py3k release schedule worries
- Next message: [Python-3000] Py3k release schedule worries
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 12/19/06, Brett Cannon <brett at python.org> wrote: > > 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. Nor stdin/out/err, not argv, not getframe, nor copyright. Yes, copyright!? I'm not concerned, really. There are bigger fish to fry. -- --Guido van Rossum (home page: http://www.python.org/~guido/)
- Previous message: [Python-3000] Py3k release schedule worries
- Next message: [Python-3000] Py3k release schedule worries
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-3000 mailing list