On Thu, Apr 15, 2021 at 9:38 AM Barry Warsaw <ba...@python.org> wrote:
> From a library maintainers point of view, I personally want to get away > from using __version__ strings at all. They’re kind of a pain to remember > to bump on every new release. That’s a tooling issue, and I don’t think that Python itself should take any official stance on the tooling. But yes, anything that Python takes an official stance on should be able to be easily supported with not-too-complex tools.and I think a __version__ string fits this need. Personally, I use the __version__ string in my packages as the canonical source when I bold my packages. And there are fancier tools for more complex needs. > PEP 396 has been dormant for a long time and I have no interest in pushing it forward any more. If someone else wants to take up the cause, I recommend creating a new PEP and referring back to 396. Fair enough -- I'm still gathering data to see if I should do just that. I am leaning toward at least SOME PEP about this -- having __version__ around as a semi-convention with no official recommendation as to if or how it should be used is kind of a mess. -CHB
_______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/FXIM52YHGECNJMKPA4E6UXJNRMZ2CUO2/ Code of Conduct: http://python.org/psf/codeofconduct/
