[issue32259] Misleading "not iterable" Error Message when generator return a "simple" type, and a tuple is expected

Camion added the comment: By the way, I guess if the problem arises like that, it's because it might be hard to distinguish both situations at the interpreter level, but if it was possible, it would be the best solution to have a different error message (even if

[issue30806] netrc.__repr__() is broken for writing to file

INADA Naoki added the comment: New changeset 3b9173d33adc2903e1af461214333b0052d7b1e9 by INADA Naoki (Steven Loria) in branch '2.7': bpo-30806: Fix netrc.__repr__() format (GH-2491) https://github.com/python/cpython/commit/3b9173d33adc2903e1af461214333b0052d7b1e9

[issue32259] Misleading "not iterable" Error Message when generator return a "simple" type, and a tuple is expected

Camion added the comment: I wrote it like that on purpose, Steven : My goal was not to show the message itself which (I believe) was sufficiently described in the explanation, but to show how hard it might be to understand the mistake in regard with the error

[issue32255] csv.writer converts None to '""\n' when it is first line, otherwise '\n'

Licht Takeuchi added the comment: The current implementation does not quote in most case. IOW, the patch which makes all '' is quoted is the breaking change (Note that there are some applications does not use quoting). -- ___

[issue32255] csv.writer converts None to '""\n' when it is first line, otherwise '\n'

Licht Takeuchi added the comment: I think the first one is buggy and there are two reasons. 1. The both are valid CSV. The double quoting is unnecessary. Some other applications, eg. Excel, does not use the double quoting. Also, the current implementation make to quote

[issue32245] OSError: raw write() returned invalid length on latest Win 10 Consoles

Change by Larry Hastings : -- nosy: -larry ___ Python tracker ___ ___ Python-bugs-list

[issue32255] csv.writer converts None to '""\n' when it is first line, otherwise '\n'

Nitish added the comment: Which scenario you think is the wrong behaviour in this case? First one or second one? I don't know much about csv module, but I thought it was a deliberate choice made to quote all empty lines and hence considered the second scenario as

[issue17972] inspect module docs omits many functions

Change by Martin Panter : -- dependencies: +Online doc does not include inspect.classify_class_attrs ___ Python tracker ___

[issue32262] Fix linting errors in asyncio code; use f-strings consistently

Yury Selivanov added the comment: I think it's OK. I want asyncio code to stay modern and up to date. git blame is not a problem here, as only one-two lines are changed per function. Code consistency is more important. --

[issue32259] Misleading "not iterable" Error Message when generator return a "simple" type, and a tuple is expected

Steven D'Aprano added the comment: I agree with Camion that the error message is misleading, and not just for beginners. It threw me for a loop too, when I first read it. Serhiy is right, the exception type cannot and should not be changed, but we can change the

[issue27505] Missing documentation for setting module __class__ attribute

Nick Coghlan added the comment: This is still a valid docs issue, although PEP 562's module __getattr__ and __dir__ will provide a simpler alternative for most of the cases that previously required setting the __class__ attribute: https://www.python.org/dev/peps/pep-0562/

[issue32225] Implement PEP 562: module __getattr__ and __dir__

New submission from Nick Coghlan : For documentation of this feature, I'd suggest adding a new subsection after https://docs.python.org/3/reference/datamodel.html#customizing-attribute-access (but at the same level), called "Customizing module attribute access". That can

[issue32225] Implement PEP 562: module __getattr__ and __dir__

Change by Nick Coghlan : -- nosy: +ncoghlan ___ Python tracker ___ ___ Python-bugs-list

[issue24991] Define instance mutability explicitly on type objects?

Nick Coghlan added the comment: I updated some of the issue metadata and added a question mark to the issue title to help make it clearer that this would require a PEP level conceptual enhancement to the language, rather than being about documenting an existing concept.

[issue31506] Improve the error message logic for object_new & object_init

Nick Coghlan added the comment: Thanks for the feedback and updates folks! If we decide to make any further changes, I think they will be best handled as a new issue :) -- resolution: -> fixed stage: patch review -> resolved status: open -> closed

[issue31506] Improve the error message logic for object_new & object_init

Nick Coghlan added the comment: New changeset 780acc89bccf332d334a27887684cc942eb6 by Nick Coghlan (Sanyam Khurana) in branch 'master': bpo-31506: Improve the error message logic for class instantiation (GH-4740)

[issue30928] Copy modified blurbs to idlelib/NEWS.txt

Change by Terry J. Reedy : -- pull_requests: +4678 ___ Python tracker ___ ___

[issue32257] Support Disabling Renegotiation for SSLContext

Nathaniel Smith added the comment: Another reason to consider making it possible to disable renegotiation is HTTP/2. RFC 7540 says: A deployment of HTTP/2 over TLS 1.2 MUST disable renegotiation. An endpoint MUST treat a TLS renegotiation as a connection error

[issue27505] Missing documentation for setting module __class__ attribute

Cheryl Sabella added the comment: Hi Nick, I started looking at this issue for documenting #22986 and then found #24912 and #24991. Has anything changed in the code since 2015 that would make these issues (this one and 24991) obsolete? It seems there were a lot of ideas

[issue32262] Fix linting errors in asyncio code; use f-strings consistently

New submission from Serhiy Storchaka : Usually we don't do such kind of changes. This spoils the output of `git annotate` and `git blame` and makes harder researching the history. -- nosy: +pitrou, rhettinger, serhiy.storchaka

[issue32265] Correctly classify builtin static and class methods

Change by Serhiy Storchaka : -- keywords: +patch pull_requests: +4677 stage: -> patch review ___ Python tracker ___

[issue32265] Correctly classify builtin static and class methods

New submission from Serhiy Storchaka : Currently class and some static methods of builtin types are classified as plain methods. The proposed patch adds types.ClassMethodDescriptorType for unbound class methods of builtin types and makes

[issue20285] Improve object.__doc__ and help(object) output

Terry J. Reedy added the comment: How about "The starting base class of all types and classes other than itself." (Object.__bases__ = ().) -- ___ Python tracker

[issue32245] OSError: raw write() returned invalid length on latest Win 10 Consoles

Eryk Sun added the comment: We need a test that reproduces this problem on a vanilla installation of Python 3.5. Include the system locale context as well, i.e. the ANSI codepage, OEM codepage, and active console output codepage. A reliable test will help determine whether

[issue32264] move pygetopt.h into internal/

New submission from Benjamin Peterson : This header has no public functions. It shouldn't be distributed. -- components: Interpreter Core messages: 307925 nosy: benjamin.peterson priority: normal severity: normal status: open title: move pygetopt.h into internal/

[issue32260] siphash shouldn't byte swap the keys

Change by Benjamin Peterson : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue30140] Binary arithmetic does not always call subclasses first

Change by Cheryl Sabella : -- components: +Interpreter Core keywords: +needs review, patch stage: -> patch review versions: +Python 3.7 ___ Python tracker

[issue32257] Support Disabling Renegotiation for SSLContext

Qichao Chu added the comment: I don't think it is a bug in OpenSSL. For various reasons, certain applications must allow renegotiation while this leaves security problem for others. That's why if python can control this flag, applications will be more confident in dealing

[issue32263] Template string docs refer to "normal %-based substitutions"

Change by Barry A. Warsaw : -- nosy: +barry ___ Python tracker ___ ___ Python-bugs-list

[issue30737] Update devguide link to the new URL

Julien Palard added the comment: Just created http://psf.upfronthosting.co.za/roundup/meta/issue646 to track the "CORE DEVELOPMENT" link of b.p.o. -- ___ Python tracker

[issue32262] Fix linting errors in asyncio code; use f-strings consistently

Change by Yury Selivanov : -- keywords: +patch pull_requests: +4676 stage: -> patch review ___ Python tracker ___

[issue32263] Template string docs refer to "normal %-based substitutions"

New submission from Glenn Linderman : At least as far back as Python 3.1, the description for Template strings (section 6.1.5 in version 3.6.4rc1 docs) starts by differentiating what Template strings do, as: Instead of the normal %-based substitutions, Templates support

[issue32262] Fix linting errors in asyncio code; use f-strings consistently

Change by Yury Selivanov : -- components: asyncio nosy: yselivanov priority: normal severity: normal status: open title: Fix linting errors in asyncio code; use f-strings consistently versions: Python 3.7 ___ Python tracker

[issue32262] Fix linting errors in asyncio code; use f-strings consistently

Change by Yury Selivanov : -- nosy: +asvetlov ___ Python tracker ___ ___

[issue30737] Update devguide link to the new URL

Julien Palard added the comment: I opened a PR on psf-salt to fix HTTP redirections https://github.com/python/psf-salt/pull/123 -- ___ Python tracker

[issue32245] OSError: raw write() returned invalid length on latest Win 10 Consoles

Larry Hastings added the comment: To confirm what Steve said: we no longer accept bug fixes for Python 3.5 (or 3.4). We only accept security fixes for 3.5 (and 3.4). -- ___ Python tracker

[issue30737] Update devguide link to the new URL

Julien Palard added the comment: Just spotted the "CORE DEVELOPMENT" link in the bugs.python.org points to the old one too. Redirections should be placed on https://docs.python.org/devguide/ to the new one too. -- nosy: +mdk

[issue32245] OSError: raw write() returned invalid length on latest Win 10 Consoles

Steve Dower added the comment: Does this only affect Python 3.5? We're highly unlikely to take a fix for that version. This code was rewritten for 3.6, so it wouldn't surprise me if there is no longer an issue. -- nosy: +larry

[issue31392] Upgrade installers to OpenSSL 1.1.0g and 1.0.2n

Ned Deily added the comment: And now 1.0.2n is out. I'm not sure how vulnerable Python is to the main problem fixed (see https://www.openssl.org/news/secadv/20171207.txt) which only impacts 1.0.2.x but I'd be willing to pull it into 3.6.4 final for the Windows and macOS

[issue20285] Improve object.__doc__ and help(object) output

Serhiy Storchaka added the comment: "Python class" can be read as a user type defined in Python (usually with the "class" statement). The term "class" in the glossary is used with this meaning in contrary to the term "type" which means also builtin and extension

[issue32260] siphash shouldn't byte swap the keys

Benjamin Peterson added the comment: New changeset 60ed1308304964e5648d8bfc9b74bd549570fa83 by Benjamin Peterson in branch 'master': byte swap the raw hash secrets (more bpo-32260) (#4773) https://github.com/python/cpython/commit/60ed1308304964e5648d8bfc9b74bd549570fa83

[issue32260] siphash shouldn't byte swap the keys

Change by Benjamin Peterson : -- pull_requests: +4675 ___ Python tracker ___ ___

[issue32245] OSError: raw write() returned invalid length on latest Win 10 Consoles

Change by Eryk Sun : -- components: +Windows nosy: +paul.moore, tim.golden, zach.ware stage: -> test needed ___ Python tracker ___

[issue20285] Improve object.__doc__ and help(object) output

Terry J. Reedy added the comment: After looking at https://en.wiktionary.org/wiki/base I can explain better why 'most base class' is wrong, and felt wrong to participants in the python-list thread. 'Base' is actually two words. As a noun (or verb), it comes from Ancient

[issue32260] siphash shouldn't byte swap the keys

Benjamin Peterson added the comment: New changeset 4e3e156391e70cd23cae18f2629ec323b3b1e7de by Benjamin Peterson in branch 'master': bpo-32260: don't byte swap siphash keys (#4771) https://github.com/python/cpython/commit/4e3e156391e70cd23cae18f2629ec323b3b1e7de

[issue32261] Online doc does not include inspect.classify_class_attrs

New submission from Cheryl Sabella : Documentation for inspect.classify_class_attrs exists in the docstring and, therefore, pydoc, but is not included in the online docs for inspect. -- assignee: docs@python components: Documentation keywords: easy messages: 307912

[issue32257] Support Disabling Renegotiation for SSLContext

Christian Heimes added the comment: If it's a bug in OpenSSL, please report the bug with OpenSSL and request a fix. Bugs should be patched where they occur. Can you contact OpenSSL development team, please? The flag is not documented and I don't know how it influences

[issue32260] siphash shouldn't byte swap the keys

Change by Benjamin Peterson : -- keywords: +patch pull_requests: +4674 stage: -> patch review ___ Python tracker ___

[issue32260] siphash shouldn't byte swap the keys

New submission from Benjamin Peterson : Reference siphash takes the keys as a bytes, so it makes sense to byte swap when reifying the keys as 64-bit integers. However, Python's modified siphash takes host integers in to start with. -- components: Interpreter Core

[issue31650] implement PEP 552

Benjamin Peterson added the comment: New changeset 42aa93b8ff2f7879282b06efc73a31ec7785e602 by Benjamin Peterson in branch 'master': closes bpo-31650: PEP 552 (Deterministic pycs) implementation (#4575)

[issue31650] implement PEP 552

Benjamin Peterson added the comment: On Sat, Dec 9, 2017, at 01:06, Serhiy Storchaka wrote: > > Serhiy Storchaka added the comment: > > While we are here, can other changes be made? All these suggestions seem fine, but they're not in the PEP

[issue8722] Documentation for __getattr__

Terry J. Reedy added the comment: Thanks. I normally look at source in my local clone with an editor. I found 'view blame' and 'view blame prior' on github. -- keywords: -patch ___ Python tracker

[issue32257] Support Disabling Renegotiation for SSLContext

Qichao Chu added the comment: Hi Christian, Thank you for review! I have changed the code to directly setting this flag by using s3->flag. Code is copied from nginx repo:

[issue32253] Deprecate old-style locking in asyncio/locks.py

Change by Andrew Svetlov : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue32253] Deprecate old-style locking in asyncio/locks.py

Andrew Svetlov added the comment: New changeset 28d8d14013ade0657fed4673f5fa3c08eb2b1944 by Andrew Svetlov in branch 'master': bpo-32253: Deprecate with statement and bare await for asyncio locks (GH-4764)

[issue32259] Misleading "not iterable" Error Message when generator return a "simple" type, and a tuple is expected

Camion added the comment: I'm not talking about changing the type of the exception, Serhiy. but only to make the text message more explicit by adding a lead to a secondary possible cause. I do not understand how this addition would be misleading - more than the

[issue32234] Add context management to mailbox.Mailbox

Change by Yury Selivanov : -- nosy: -yselivanov ___ Python tracker ___ ___

[issue32234] Add context management to mailbox.Mailbox

Change by sblondon : -- keywords: +patch pull_requests: +4673 stage: -> patch review ___ Python tracker ___

[issue32253] Deprecate old-style locking in asyncio/locks.py

Yury Selivanov added the comment: > This can make harder writing portable code that works in 2.7, 3.4 and 3.7. asyncio for Python 3.4 is fairly outdated. Most of the async packages today require 3.5+, as they usually use async/await syntax. I say this sort of

[issue26865] Meta-issue: support of the android platform

Xavier de Gaye added the comment: issue 22724 is fixed for Android. -- dependencies: -byte-compile fails for cross-builds ___ Python tracker

[issue26865] Meta-issue: support of the android platform

Change by Xavier de Gaye : -- dependencies: +Add platform.android_ver() to test.pythoninfo for Android platforms, Do not use the canonical path in pydoc test_mixed_case_module_names_are_lower_cased, [asyncio] test failure when the platform lacks a functional

[issue26865] Meta-issue: support of the android platform

Xavier de Gaye added the comment: issue #32031: Do not use the canonical path in pydoc test_mixed_case_module_names_are_lower_cased issue #32059: detect_modules() in setup.py must also search the sysroot paths issue #32126: [asyncio] test failure when the platform lacks a

[issue32255] csv.writer converts None to '""\n' when it is first line, otherwise '\n'

Change by Licht Takeuchi : -- keywords: +patch pull_requests: +4672 stage: -> patch review ___ Python tracker ___

[issue32259] Misleading "not iterable" Error Message when generator return a "simple" type, and a tuple is expected

Serhiy Storchaka added the comment: I concur with Eric. The current exception is correct and allows to identify your mistake. Changing the type of the exception will break an existing code, and the message proposed by you is misleading. -- nosy:

[issue32259] Misleading "not iterable" Error Message when generator return a "simple" type, and a tuple is expected

Camion added the comment: Ok, but the other explanation is valid as well. That's why I suggest to modify the error message like this : TypeError: '[TYPE]' object is not iterable - OR - ValueError: not enough values to unpack (expected [N], got 1) --

[issue2636] Adding a new regex module (compatible with re)

Change by petros : -- nosy: +petros ___ Python tracker ___ ___ Python-bugs-list mailing

[issue20285] Improve object.__doc__ and help(object) output

Cheryl Sabella added the comment: Hi Terry, I've submitted a PR for this. Thanks! -- nosy: +csabella ___ Python tracker ___

[issue32212] few discrepancy between source and docs in logging

Change by Vinay Sajip : -- resolution: not a bug -> fixed stage: patch review -> resolved status: open -> closed type: -> enhancement ___ Python tracker

[issue32212] few discrepancy between source and docs in logging

Vinay Sajip added the comment: New changeset 292fce9934280867ca9a65870495f83fca37751e by Vinay Sajip in branch '2.7': bpo-32212: Updated logging documentation to make parameter names more consistent with source. (GH-4765) (GH-4768)

[issue32259] Misleading "not iterable" Error Message when generator return a "simple" type, and a tuple is expected

Eric V. Smith added the comment: The error message is correct, but I'm sorry it's confusing. Here's an equivalent error: a, b = 3 You'll get the error "TypeError: 'int' object is not iterable". That's because Python sees 2 items to the left of the assignment, so it needs

[issue32212] few discrepancy between source and docs in logging

Vinay Sajip added the comment: New changeset 63868181a904c844d8d01e3badfdd5b134acc5fa by Vinay Sajip in branch '3.6': bpo-32212: Updated logging documentation to make parameter names more consistent with source. (GH-4765) (GH-4767)

[issue32212] few discrepancy between source and docs in logging

Change by Vinay Sajip : -- pull_requests: +4671 ___ Python tracker ___ ___

[issue8722] Documentation for __getattr__

Cheryl Sabella added the comment: >> Is there a way to get an annotated listing from git (given which patch, and >> therefore which person, is responsible for each line)? Which source did you want to look at? In github, if you go into any source, you can click on a line

[issue32257] Support Disabling Renegotiation for SSLContext

Christian Heimes added the comment: I don't think your PR is required. The issue has been addressed in OpenSSL 0.9.8m over 7 years ago, https://access.redhat.com/security/cve/cve-2009-3555. >From https://www.openssl.org/docs/manmaster/man3/SSL_CTX_set_options.html >

[issue32259] Misleading "not iterable" Error Message when generator return a "simple" type, and a tuple is expected

New submission from Camion : I'm new with Python and I've been blocked for day on a "TypeError: 'Fraction' object is not iterable" error message, while the problem turned out to be completely different. I don't even know to what programming case this message

[issue32212] few discrepancy between source and docs in logging

Change by Vinay Sajip : -- pull_requests: +4670 ___ Python tracker ___ ___

[issue32257] Support Disabling Renegotiation for SSLContext

Christian Heimes added the comment: Thanks for your patch, a few comments We generally don't have special functions to set flags. SSL3_FLAGS_NO_RENEGOTIATE_CIPHERS is an OpenSSL < 1.1.0 option. OpenSSL 1.1.0 still defines the flag but no longer uses it. With your patch, the

[issue32212] few discrepancy between source and docs in logging

Vinay Sajip added the comment: New changeset a9f8df646aac7fc94ced0aefd1ed2c8566d14d10 by Vinay Sajip in branch 'master': bpo-32212: Updated logging documentation to make parameter names more consistent with source. (GH-4765)

[issue32250] Add loop.current_task() and loop.all_tasks() methods

Change by Andrew Svetlov : -- keywords: +patch pull_requests: +4669 stage: -> patch review ___ Python tracker ___

[issue32212] few discrepancy between source and docs in logging

Change by Vinay Sajip : -- keywords: +patch pull_requests: +4668 stage: needs patch -> patch review ___ Python tracker ___

[issue32258] Rewrite asyncio docs to use async/await syntax

Change by Serhiy Storchaka : -- title: Rewrite ayncio docs to use async/await syntax -> Rewrite asyncio docs to use async/await syntax ___ Python tracker

[issue32258] Rewrite ayncio docs to use async/await syntax

New submission from Andrew Svetlov : https://bugs.python.org/issue32193 switched asyncio implementation to async/await syntax. We need to update documentation as well. -- assignee: docs@python components: Documentation, asyncio messages: 307889 nosy:

[issue32253] Deprecate old-style locking in asyncio/locks.py

Andrew Svetlov added the comment: 1. asyncio is not supported by 2.7 anyway 2. with (yield from lock) is based on very non-obvious tricks: a) lock.__enter__ is forbidden and raises RuntimeError b) actually lock.__iter__ is called for lock acquiring *before* calling

[issue32253] Deprecate old-style locking in asyncio/locks.py

Serhiy Storchaka added the comment: This can make harder writing portable code that works in 2.7, 3.4 and 3.7. What is the benefit of the deprecation? Are there inevitable design or implementation errors in these constructions? Or getting rid of them can

[issue8722] Documentation for __getattr__

Change by Berker Peksag : -- keywords: +patch ___ Python tracker ___ ___

[issue32252] test_regrtest leaves a test_python_* directory in TEMPDIR

Xavier de Gaye added the comment: Oh it seems your Fedora 27 also uses systemd and uses the same configuration as archlinux, see https://wiki.archlinux.org/index.php/Core_dump. In that case according to this wiki your core dumps go to /var/lib/systemd/coredump and this may

[issue32253] Deprecate old-style locking in asyncio/locks.py

Change by Andrew Svetlov : -- keywords: +patch pull_requests: +4667 stage: -> patch review ___ Python tracker ___

[issue32252] test_regrtest leaves a test_python_* directory in TEMPDIR

Xavier de Gaye added the comment: > Can you please explain how to reproduce the bug? (Which commands should I > type?) ./python -m test test_regrtest > What is your /proc/sys/kernel/core_pattern? $ cat /proc/sys/kernel/core_pattern core-%e.%s $ ulimit -c unlimited FWIW

[issue31650] implement PEP 552

Serhiy Storchaka added the comment: While we are here, can other changes be made? 1. Increase the size of the constant part of the signature. Currently it is only 2 bytes (3rd and 4th bytes are b'\r\n') and it is hard to use them in tools like `file`. 2. Split

[issue32186] io.FileIO hang all threads if fstat blocks on inaccessible NFS server

STINNER Victor added the comment: (Oops, closing was my intent of my previous comment, but I forgot it, thanks Berker.) -- ___ Python tracker