[issue23226] Add float linspace recipe to docs

Changes by Raymond Hettinger : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue23226] Add float linspace recipe to docs

Roundup Robot added the comment: New changeset bb8fe61d78a4 by Raymond Hettinger in branch 'default': Issue #23226: Add linspace() recipe to the docs https://hg.python.org/cpython/rev/bb8fe61d78a4 -- nosy: +python-dev ___ Python tracker

[issue23226] Add float linspace recipe to docs

Changes by Mark Dickinson : -- nosy: +mark.dickinson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue23226] Add float linspace recipe to docs

Andrew Barnert added the comment: So something like the first version below? Or should even the example be inline, as in the second version below? (Apologies if the formatting gets screwed up pasting from docs to bugs.) --- Range objects are inappropriate for non-integral types, especially in

[issue23226] Add float linspace recipe to docs

Raymond Hettinger added the comment: This is too much. Try for a brief reference. This section of the docs is primarily about how range() works. Linspace() is at best a tangential discussion and shouldn't interfere with the usability of range() docs (a tool we actually have and that is in c

[issue23226] Add float linspace recipe to docs

Andrew Barnert added the comment: As suggested by the review: removing unnecessary parenthetical, changing "ulp" to "digit", and fixing the recipe link. -- Added file: http://bugs.python.org/file37685/stdtypes.rst.diff ___ Python tracker

[issue23226] Add float linspace recipe to docs

New submission from Andrew Barnert: In a recent thread on python-ideas (https://mail.python.org/pipermail/python-ideas/2015-January/030817.html), it was concluded that Python should not have a range-like type for floats in the stdlib, but there should be some simple discussion of the alternati