This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author mbussonn
Recipients Nate Soares, ezio.melotti, mbussonn, mrabarnett, steven.daprano, vstinner
Date 2017-07-05.13:36:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1499261795.93.0.0479768561352.issue30772@psf.upfronthosting.co.za>
In-reply-to
Content
> I think that the names in __all__ should have the same NFKC normalisation applied as the identifiers.
 
Does it make sens to add to this issue : Ensure that all elements of __all__ are str ? (At least emit a warning ?)

I have encounter a small number of libraries where some member of all are the actual objects. Easy mistake to make if you make a public decorator:

    __all__ = []

    def public(o):
        __all__.append(o)
        return o

    @public
    def bar():
        pass

Happy to open a different issue if deemed necessary. Thanks !
History
Date User Action Args
2017-07-05 13:36:36mbussonnsetrecipients: + mbussonn, vstinner, ezio.melotti, mrabarnett, steven.daprano, Nate Soares
2017-07-05 13:36:35mbussonnsetmessageid: <1499261795.93.0.0479768561352.issue30772@psf.upfronthosting.co.za>
2017-07-05 13:36:35mbussonnlinkissue30772 messages
2017-07-05 13:36:35mbussonncreate