FWIW, I think __version__, __author__ etc. were bad ideas. Almost nobody manages these correctly. Note that the PEP 8 section starts with less than an endorsement: "If you *have* to have Subversion, CVS, or RCS crud in your source file, do it as follows."
That said, if an official answer is required, common sense would suggest that __version__ should go before the imports. (I would put it before the docstring too, except then the docstring wouldn't be a docstring any more. Go figure.) On Fri, Mar 20, 2015 at 6:38 PM, Ben Finney <ben+pyt...@benfinney.id.au> wrote: > Lewis Coates <lew...@pdx.edu> writes: > > > In pep8 there are two conflicting statements, both > > > > https://www.python.org/dev/peps/pep-0008/#version-bookkeeping > > https://www.python.org/dev/peps/pep-0008/#imports > > > > Stipulate that they should be "at the top of the file after any module > > comments and docstrings." Which of these takes precedence? > > I don't know an official answer. The convention I've observed is > overwhelmingly in one direction: import statements come before any > assignment statements. > > > Secondly, we also have an "__author__", and "__project__" variables, I > > assume these would be put with the version information as well? > > Yes. > > -- > \ “Welchen Teil von ‘Gestalt’ verstehen Sie nicht? [What part of | > `\ ‘gestalt’ don't you understand?]” —Karsten M. Self | > _o__) | > Ben Finney > > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/guido%40python.org > -- --Guido van Rossum (python.org/~guido)
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
