If curses is a core facility now, the default build should tread it as one.
...
IMO ssl isn't an issue because it's not documented as being in the standard module set.
...
- Documented as being in the core but not built in by default.
My more general claim is that the existence of class 3 is a problem
In the case of curses, I believe there is a documentation error in the 2.0 documentation. The curses packages is listed under "Generic Operating System Services". I believe this is wrong, it should be listed as "Unix Specific Services".
Unless I'm mistaken, the curses module is not available on the Mac and on Windows. With that change, the curses module would then fall into Eric's category 2 (Not documented as being in the core and not built in by default).
That documentation change should be carried out even if curses is autoconfigured; autoconf is used on Unix only, either.
Regards, Martin
P.S. The "Python Library Reference" content page does not mention the word "core" at all, except as part of asyncore...
Martin v. Loewis martin@loewis.home.cs.tu-berlin.de:
In the case of curses, I believe there is a documentation error in the 2.0 documentation. The curses packages is listed under "Generic Operating System Services". I believe this is wrong, it should be listed as "Unix Specific Services".
I agree that this is an error and should be fixed.
Unless I'm mistaken, the curses module is not available on the Mac and on Windows. With that change, the curses module would then fall into Eric's category 2 (Not documented as being in the core and not built in by default).
Well...that's a definitional question that is part of the larger issue here.
What does being in the Python core mean? There are two potential definitions:
1. Documentation says it's available on all platforms.
2. Documentation restricts it to one of the three platform groups (Unix/Windows/Mac) but implies that it will be available on any OS in that group.
I think the second one is closer to what application programmers thinking about which batteries are included expect. But I could be persuaded otherwise by a good argument.
What does being in the Python core mean? There are two potential definitions:
Documentation says it's available on all platforms.
Documentation restricts it to one of the three platform groups (Unix/Windows/Mac) but implies that it will be available on any OS in that group.
I think the second one is closer to what application programmers thinking about which batteries are included expect. But I could be persuaded otherwise by a good argument.
Actually, when *I* have used the term "core" I've typically thought of this as referring to anything that's in the standard source distribution, whether or not it is built on all platforms.
--Guido van Rossum (home page: http://www.python.org/~guido/)
participants (3)
-
Eric S. Raymond -
Guido van Rossum -
Martin v. Loewis