[issue16395] Documentation claims that PySequence_Fast returns a tuple, when it actually returns a list.

Larry Hastings added the comment: I have no objections to someone backporting this. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16395 ___ ___

[issue16395] Documentation claims that PySequence_Fast returns a tuple, when it actually returns a list.

Roundup Robot added the comment: New changeset b2187b82a658 by Benjamin Peterson in branch '3.4': PySequence_Fast generally returns a list not a tuple (closes #16395) http://hg.python.org/cpython/rev/b2187b82a658 New changeset b235db467cd5 by Benjamin Peterson in branch '2.7': PySequence_Fast

[issue16395] Documentation claims that PySequence_Fast returns a tuple, when it actually returns a list.

Josh Rosenberg added the comment: Any news on this? I was about to open a bug of my own for this, since the docs and code are still out of sync. -- nosy: +josh.rosenberg ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16395

[issue16395] Documentation claims that PySequence_Fast returns a tuple, when it actually returns a list.

Josh Rosenberg added the comment: As far as performance goes, presumably the length hinting API reduces the number of cases in which we're working with completely unsized iterables, right? -- ___ Python tracker rep...@bugs.python.org

[issue16395] Documentation claims that PySequence_Fast returns a tuple, when it actually returns a list.

New submission from Simon Law: The documentation in Python 2.7, 3.2, and 3.3 claim that: PyObject* PySequence_Fast(PyObject *o, const char *m) Return value: New reference. Returns the sequence o as a tuple, unless it is already a tuple or list, in which case o is returned... Unfortunately,

[issue16395] Documentation claims that PySequence_Fast returns a tuple, when it actually returns a list.

Changes by Éric Araujo mer...@netwok.org: -- nosy: +rhettinger ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16395 ___ ___ Python-bugs-list

[issue16395] Documentation claims that PySequence_Fast returns a tuple, when it actually returns a list.

Simon Law added the comment: It looks like this was caught in the 3.3 branch, but only fixed it in the comment: changeset: 75448:d8f68195210e user:Larry Hastings la...@hastings.org date:Mon Mar 05 22:59:13 2012 -0800 summary: Fix a comment: PySequence_Fast() creates a

[issue16395] Documentation claims that PySequence_Fast returns a tuple, when it actually returns a list.

Éric Araujo added the comment: Larry, any objection to backporting this? -- assignee: - docs@python components: +Documentation -Interpreter Core nosy: +docs@python, eric.araujo, larry stage: - patch review versions: -Python 3.3 ___ Python tracker

[issue16395] Documentation claims that PySequence_Fast returns a tuple, when it actually returns a list.

Serhiy Storchaka added the comment: PySequence_Tuple() was changed to PySequence_List() in the changeset 4714aff4bf75 in 2004. Are there any measurements which show PySequence_List() faster than PySequence_Tuple() on modern Python? I don't see any references in 4714aff4bf75 description.