[Python-Dev] quick PEP 387 comments
Brett Cannon
brett at python.org
Fri Aug 28 01:57:51 CEST 2009
More information about the Python-Dev mailing list
Fri Aug 28 01:57:51 CEST 2009
- Previous message: [Python-Dev] deprecated methods on array objects
- Next message: [Python-Dev] quick PEP 387 comments
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Is the PEP considering all non-private APIs public even if they are not documented? If so we might want to be up front about that and say so to make sure we are all very careful about making all non-essential APIs private (assuming this PEP gets accepted). And we might want to say that all code in 'test' sub-packages are not subject to backwards compatibility unless documented. I have a ton of support code in importlib.test that I do not want to have to maintain for public consumption as they are meant solely for testing purposes by me. If you read the PEP it would suggest that all modules in test are subject to the PEP's compatibility policy which is obviously absurd. -Brett
- Previous message: [Python-Dev] deprecated methods on array objects
- Next message: [Python-Dev] quick PEP 387 comments
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list