[TIP] including (or not) tests within your package

Barry Warsaw barry at python.org
Tue Aug 10 10:23:16 PDT 2010

On Aug 10, 2010, at 12:04 PM, Ben Finney wrote:

>Andrew Bennetts <andrew at bemusement.org> writes:
>> Ben Finney wrote:
>> > [One downside of installing the tests along with the rest of the
>> > package is that] They would thereby become part of the *public*
>> > interface for the package. I don't want that implied promise; the
>> > test suite is subject to arbitrary unannounced change or removal.
>> Surely you don't consider every importable name to be part of the
>> public interface for a package?
>Every importable name that isn't marked with a leading-underscore name,
>yes. That's what that distinction is for, after all.

I think you meant "after __all__".

__all__ directly controls what names get imported via from-import-* but it's a
very strong indicator about what names are intended as part of the public

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.idyll.org/pipermail/testing-in-python/attachments/20100810/188c42e0/attachment.pgp>

More information about the testing-in-python mailing list