In article <[email protected]>, Stefan Schwarzer <[email protected]> wrote: > >Which approach would you prefer and why? Or some other approach? Would >you use a different approach if the library-internal class was named >`_FTPFile` instead of `FTPFile`?
If it's not a public class, it should have been named `_FTPFile`. When your class isn't public, it doesn't matter much exactly how you expose it internally. (I essentially never use __all__ myself, but I don't write libraries for public consumption.) -- Aahz ([email protected]) <*> http://www.pythoncraft.com/ "If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." --Red Adair -- http://mail.python.org/mailman/listinfo/python-list
