Vinícius Dantas added the comment: If it is tagged for future releases, whoever choose to update their Python version should expect code breaking and API changes, shouldn't them? I don't see code breaking as an issue against this request.
On 1 March 2017 at 14:33, Raymond Hettinger <rep...@bugs.python.org> wrote: > > Raymond Hettinger added the comment: > > It's too late to change this API. As Serhiy says, it risks breaking code > that is currently running and correct. > > Note the the __doc__ on functions is set to None when there is no > docstring. For better or worse, returning None is common in the Python > world. > > ---------- > nosy: +rhettinger > resolution: -> rejected > stage: -> resolved > status: open -> closed > > _______________________________________ > Python tracker <rep...@bugs.python.org> > <http://bugs.python.org/issue29686> > _______________________________________ > -- Vinícius Dantas de Lima Melo Graduando em Ciências e Tecnologia Universidade Federal do Rio Grande do Norte (UFRN) Escola de Ciências e Tecnologia (ECT) Natal, Rio Grande do Norte vinicius.gpp...@gmail.com viniciusdan...@bct.ect.ufrn.br vinicius.dantasdelimam...@mail.utoronto.ca | Celular/Mobile Phone: +1 647 447 5737 Skype: viniciusdantas01 ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29686> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
