"Benjamin Kaplan" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] | On Sat, May 24, 2008 at 10:14 AM, Fuzzyman <[EMAIL PROTECTED]> wrote: || > For example, at Resolver Systems we expose the spreadsheet object | > model to our users. It hasa public, documented, API - plus a host of | > undocumented internally used methods. | > | > We would really *much* rather hide these, because anything our | > customers start using (whether documented or not) we will probably | > have to continue supporting and maintaining. | > | > The 'we told you not to use that' approach, when applied to paying | > customers doesn't really work... all they see is that you broke their | > spreadsheet code by changing your API.
Python was not really written with 'difficult' customers in mind ;-) One could largely hide private vars with a program that substituted random names for single _ names, and removed the doc strings for functions, classes, and methods with such names. Such a program could even put such names in a separate module imported as '_private_do_not_use_'. -- http://mail.python.org/mailman/listinfo/python-list
