[issue29330] __slots__ needs documentation

Martin Panter added the comment: Have you seen ? There is also . -- assignee: -> docs@python components: +Documentation nosy: +docs@python, martin.panter _

[issue29327] SystemError or crash in sorted(iterable=[])

STINNER Victor added the comment: Raymond: "Please be careful with all of these AC changes. They need to have tests. They need to not change APIs. They need to not introduce bugs." The bug was not introduced by an Argument Clinic change. I agree that switching to AC must not change the API.

[issue29330] __slots__ needs documentation

saumitra paul added the comment: Python 2.7.10 (default, Oct 23 2015, 19:19:21) [GCC 4.2.1 Compatible Apple LLVM 7.0.0 (clang-700.0.59.5)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> help(__slots__) Traceback (most recent call last): File "", line 1

[issue9625] argparse: Problem with defaults for variable nargs when using choices

Changes by paul j3 : -- priority: normal -> high ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue9338] argparse optionals with nargs='?', '*' or '+' can't be followed by positionals

Changes by paul j3 : -- priority: normal -> high ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue29057] Compiler failure on Mac OS X - sys/random.h

Changes by Ned Deily : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___ Pyth

[issue27596] Build failure with Xcode 8 beta on OSX 10.11

Ned Deily added the comment: Maxime, there have been a couple of attempts to address this problem. We believe it now finally fixed for all versions of macOS from 10.6 through 10.12 by the changes in Issue29057. Unfortunately, for 2.7,x the last set of fixes were after the release of 2.7.13 i

[issue29328] struct module should support variable-length strings

Yury Selivanov added the comment: Ethan, thanks for moving my reply on the list to here. Also +1 to what Mark said. -- nosy: +yselivanov ___ Python tracker ___

[issue27596] Build failure with Xcode 8 beta on OSX 10.11

Maxime Belanger added the comment: Glad to hear it! Thanks for the quick followup :). -- ___ Python tracker ___ ___ Python-bugs-list m

[issue29330] __slots__ needs documentation

Eryk Sun added the comment: Are you suggesting that the Helper class in Lib/pydoc.py should index [sub-]topics by special names such as "__slots__"? Currently you can see the __slots__ documentation via the topics "ATTRIBUTEMETHODS" and "SPECIALMETHODS". The list of topics can be printed via h

[issue29330] __slots__ needs documentation

Changes by Raymond Hettinger : -- assignee: docs@python -> rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue29316] Can we keep typing.py provisional for the duration of the Python 3.6 release cycle?

Ned Deily added the comment: As far as I can tell, the only places that typing was declared as provisional were in PEP 484 and twice in the 3.5 What's New document (https://docs.python.org/3.5/whatsnew/3.5.html); it doesn't appear to have been mentioned in the library reference (https://docs.

[issue29323] Wrong documentation (Library) for unicode and str comparison

R. David Murray added the comment: That's a good point, I think that is exactly the issue with that paragraph. -- ___ Python tracker ___ _

[issue29259] Add tp_fastcall to PyTypeObject: support FASTCALL calling convention for all callable objects

STINNER Victor added the comment: tp_fastcall-5.patch: Rebased patch. I already tried to push changes not directly related to tp_fastcall, so the new patch should be a *little bit* shorter. -- Added file: http://bugs.python.org/file46347/tp_fastcall-5.patch ___

[issue29316] Keep typing.py provisional for the duration of the Python 3.6 release cycle

Guido van Rossum added the comment: Thanks everybody! We'll make typing.py provisional again for 3.6. @levkivskyi do you have the stomach to upload a patch here? -- title: Can we keep typing.py provisional for the duration of the Python 3.6 release cycle? -> Keep typing.py provisional

[issue9625] argparse: Problem with defaults for variable nargs when using choices

paul j3 added the comment: Recent StackOverFlow question related to this issue http://stackoverflow.com/questions/41750896/python-argparse-type-inconsistencies-when-combining-choices-nargs-and-def/41751730#41751730 -- ___ Python tracker

[issue9338] argparse optionals with nargs='?', '*' or '+' can't be followed by positionals

paul j3 added the comment: Recent StackOverFlow question related to this issue - where the following positional is a subparsers. http://stackoverflow.com/questions/41742205/how-to-argparse-with-nargs-and-subcommands -- ___ Python tracker

[issue29292] Missing a parameter in PyEval_EvalCodeEx doc

Ammar Askar added the comment: Updated patch for review comments -- Added file: http://bugs.python.org/file46348/kwdefs_docs.diff3 ___ Python tracker ___

[issue29292] Missing a parameter in PyEval_EvalCodeEx doc

Ammar Askar added the comment: Updated patch to include a cross reference to keyword-only arguments since I think not everyone will know about this rather new feature. -- Added file: http://bugs.python.org/file46349/kwdefs_docs.diff4 ___ Python track

[issue29281] json.loads documentation missing "versionchanged" statement

Ammar Askar added the comment: Attached patch adds a versionchanged block to specify that bytes and bytesarray can now be used and the types of encodings it supports (as taken from the whatsnew changes here https://hg.python.org/cpython/rev/e9e1bf9ec2ac#l2.7) -- keywords: +patch Added

[issue29292] Missing a parameter in PyEval_EvalCodeEx doc

Roundup Robot added the comment: New changeset bb76ea32a32f by Xiang Zhang in branch '3.5': Issue #29292: Update outdated doc of PyEval_EvalCodeEx. https://hg.python.org/cpython/rev/bb76ea32a32f New changeset bd121b7517ee by Xiang Zhang in branch '3.6': Issue #29292: Merge 3.5. https://hg.python

[issue29292] Missing a parameter in PyEval_EvalCodeEx doc

Xiang Zhang added the comment: Thanks Ammar. :-) -- resolution: -> fixed stage: needs patch -> resolved status: open -> closed ___ Python tracker ___ ___

[issue29325] pysqlite: Evaluate removal of sqlite3_stmt_readonly

Xiang Zhang added the comment: pysqlite is not part of Python stdlib so here is not the right place. :-( Maybe you could go to https://github.com/ghaering/pysqlite for help. -- nosy: +xiang.zhang resolution: -> third party stage: -> resolved status: open -> closed

[issue29327] SystemError or crash in sorted(iterable=[])

Raymond Hettinger added the comment: A few random thoughts that may or may not be helpful: * We now have two seasoned developers and one new core developer that collectively are creating many non-trivial patches to core parts of Python at an unprecedented rate of change. The patches are comin

[issue29325] pysqlite: Evaluate removal of sqlite3_stmt_readonly

Ma Lin added the comment: sqlite3 module in CPython 3.6.0 also uses sqlite3_stmt_readonly(). see 284676cf2ac8. sqlite3_stmt_readonly() was used twice [1][2], but it seems that we can avoid using this function in both of them. [1] https://hg.python.org/cpython/file/3.6/Modules/_sqlite/cursor.c#

[issue29325] pysqlite: Evaluate removal of sqlite3_stmt_readonly

Xiang Zhang added the comment: Hi Ma Lin. If you find this is also a problem in sqlite3 module, feel free to open another issue against sqlite3. :-) -- ___ Python tracker ___ __

[issue29325] pysqlite: Evaluate removal of sqlite3_stmt_readonly

Ma Lin added the comment: RHEL6's life-cycle is around 10 years [1], it will be alive until 2020. https://access.redhat.com/support/policy/updates/errata/ Let's wait issue28518, IMO, that issue will decide whether we can get around sqlite3_stmt_readonly(). -- _

[issue29281] json.loads documentation missing "versionchanged" statement

Changes by Raymond Hettinger : -- assignee: docs@python -> rhettinger nosy: +rhettinger ___ Python tracker ___ ___ Python-bugs-list ma

[issue29298] argparse fails with required subparsers, un-named dest, and empty argv

paul j3 added the comment: http://bugs.python.org/issue9253 argparse: optional subparsers Initially this bug/issue was a request to allow subparsers to be optional. But with the change in how required actions are handled, subparsers are now optional by default. As you learned from the SO qu

[issue29281] json.loads documentation missing "versionchanged" statement

Roundup Robot added the comment: New changeset 3452ff9e8f0a by Raymond Hettinger in branch '3.6': Issue #29281: Fill-in a missing versionchanged entry https://hg.python.org/cpython/rev/3452ff9e8f0a -- nosy: +python-dev ___ Python tracker

[issue29281] json.loads documentation missing "versionchanged" statement

Raymond Hettinger added the comment: Thanks for the patch. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___

[issue29327] SystemError or crash in sorted(iterable=

Serhiy Storchaka added the comment: > While Python 3.5 doesn't crash, I consider that it has also the bug. So I > added Python 3.5 in Versions. The patch uses new feature of 3.6 -- supporting positional-only parameters in PyArg_ParseTupleAndKeywords() (see issue26282). Since passing an iterabl

[issue29327] SystemError or crash in sorted(iterable=[])

Changes by Serhiy Storchaka : -- title: SystemError or crash in sorted(iterable= -> SystemError or crash in sorted(iterable=[]) ___ Python tracker ___ __

[issue29327] SystemError or crash in sorted(iterable=[])

Raymond Hettinger added the comment: Serhiy, this patch passes tests and looks fine. I think you can go ahead with this patch. -- assignee: -> serhiy.storchaka ___ Python tracker

[issue29328] struct module should support variable-length strings

Raymond Hettinger added the comment: FWIW, I concur with Mark and Yuri that the feature request isn't compatible with the design and purpose of the struct module -- nosy: +rhettinger ___ Python tracker ___

[issue29327] SystemError or crash in sorted(iterable=

Serhiy Storchaka added the comment: > Serhiy, this patch passes tests and looks fine. I think you can go ahead > with this patch. Right now I'm building 3.6 with applied patch before final testing and committing. My netbook is very slow. :( -- title: SystemError or crash in sorted(ite

[issue29327] SystemError or crash in sorted(iterable=[])

Serhiy Storchaka added the comment: The title is spoiled when reply by email. I suppose [] has special meaning in email subject. -- title: SystemError or crash in sorted(iterable= -> SystemError or crash in sorted(iterable=[]) ___ Python tracker

[issue29327] SystemError or crash in sorted(iterable=[])

Roundup Robot added the comment: New changeset 1827b64cfce8 by Serhiy Storchaka in branch '3.6': Issue #29327: Fixed a crash when pass the iterable keyword argument to sorted(). https://hg.python.org/cpython/rev/1827b64cfce8 New changeset f44f44b14dfc by Serhiy Storchaka in branch 'default': Iss

[issue29296] convert print() to METH_FASTCALL

INADA Naoki added the comment: > Can we close the issue, or do you prefer to keep it open? I don't care. -- ___ Python tracker ___ __

[issue29331] Simplify argument parsing in sorted() and list.sort()

New submission from Serhiy Storchaka: Proposed patch simplifies argument parsing in sorted() and list.sort(). list.sort() now uses the support of keyword-only parameters in PyArg_ParseTupleAndKeywords(). Keyword arguments now are passed as is to list.sorted() in sorted(). -- component

[issue29241] sys._enablelegacywindowsfsencoding() don't apply to os.fsencode and os.fsdecode

JGoutin added the comment: A little encoding cache benchmark. Current Code: = import sys def _fscodec(): encoding = sys.getfilesystemencoding() errors = sys.getfilesystemencodeerrors() def fsencode(filename): filename = fspath(filename) # Does type-checking o

[issue29327] SystemError or crash in sorted(iterable=

STINNER Victor added the comment: "The patch uses new feature of 3.6 -- supporting positional-only parameters in PyArg_ParseTupleAndKeywords() (see issue26282)." Oh, I didn't recall that it's a new feature. It's a nice feature by the way, thanks for implementing it :-) In that case, yeah it's

[issue29296] convert print() to METH_FASTCALL

STINNER Victor added the comment: Since the title of the issue is "convert print() to METH_FASTCALL", I consider that the issue is now done. As I wrote, as soon as AC will support **kwargs, we will be able to print() to use AC. Thanks Naoki for the change. -- dependencies: -Argument

<    1   2