Nick Coghlan <[EMAIL PROTECTED]> added the comment: I found further PEP 8 non-compliances in the multiprocessing API while working on a patch for issue 3589, mainly in the area of function names that start with a capital letter, making them look like classes when they definitely are not.
After noticing a few of these, I went through checked more thoroughly, and found all of the following to be functions that claimed to be classes by way of their naming convention (a far worse sin than using camelCase instead of underscores): multiprocessing.Pipe (aka multiprocessing.connection.Pipe) multiprocessing.RawValue (aka multiprocessing.sharedctypes.RawValue) multiprocessing.RawArray (aka multiprocessing.sharedctypes.RawArray) multiprocessing.Value (aka multiprocessing.sharedctypes.Value) multiprocessing.Array (aka multiprocessing.sharedctypes.Array) multiprocessing.connection.Client multiprocessing.connection.SocketClient multiprocessing.connection.PipeClient multiprocessing.connection.XmlClient multiprocessing.managers.RebuildProxy multiprocessing.managers.MakeProxyType multiprocessing.managers.AutoProxy multiprocessing.managers.Array These should all be converted to start with a lowercase letter and use underscores, otherwise people are going to assume they can be treated like classes. _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue3352> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
