[issue29928] Add f-strings to Glossary

Martin Panter added the comment: When I wrote the documentation , I think I tried to avoid “f-string”, being jargon, and used more formal terminology from PEP 498 instead. But I agree they more than regular literals. Serhi

[issue29928] Add f-strings to Glossary

Serhiy Storchaka added the comment: I don't have a link. There were a lot of threads about this feature and I didn't follow them. After implementing PEP 498 there was a discussion about terminology. I read discussions about coming and released Python 3.6 on StackOverflow, Reddit and other res

[issue29922] error message when __aexit__ is not async

Changes by Chewy : -- nosy: +Chewy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mail

[issue29921] datetime validation is stricter in 3.6.1 than previous versions

m-parry added the comment: >From my opening comment (with new emphasis): "I think it's the case that **some routes via the C API** now reject out of range values that were previously permitted." The pywin32 repro I gave above eventually calls PyDateTimeAPI->DateTime_FromDateAndTime(): http:/

[issue29929] Idea: Make __main__ an implied package

New submission from Nick Coghlan: In just the last 24 hours, I've run across two cases where the default "the script directory is on sys.path" behaviour confused even experienced programmers: 1. a GitHub engineer thought the Python version in their Git-for-Windows bundle was broken because "f

[issue29930] asyncio.StreamWriter.drain raises an AssertionError under heavy use

New submission from Metathink: While trying to break some code in a project using asyncio, I found that under certain circumstances, asyncio.StreamWriter.drain raises an AssertionError. 1. There must be a lot of concurrent uses of "await writer.drain()" 2. The server on which we send data must

[issue29929] Idea: Make __main__ an implied package

Nick Coghlan added the comment: A key enabler for actually pursuing this idea would be coming up with a feasible way of emitting a deprecation warning for code that relied on the old implicit relative imports. A reasonable fast check for that would be to: 1. Start populating a private sys._mai

[issue29908] Inconsistent crashing with an access violation

Eryk Sun added the comment: I can confirm that the CRT function construct_environment_block() does cause an access violation sometimes when no "=x:" shell variables are defined in the current environment. These "=x:" environment variables are the way that Windows emulates DOS per-drive working

[issue29929] Eliminate implicit __main__ relative imports

Nick Coghlan added the comment: In formulating a post to import-sig about this, I realised it made more sense to describe it in terms of the goal (eliminating implicit __main__ relative imports) rather than one possible technique for achieving that goal. -- title: Idea: Make __main__ a

[issue29677] clarify docs about 'round()' accepting a negative integer for ndigits

Cheryl Sabella added the comment: Mariatta, Yes, thank you, I will work on a pull request to address Victor's comment. Since it's my first time, I hope to read through the contributing docs and get this done today or tomorrow. Thank you! -- ___ P

[issue29931] ipaddress.ip_interface __lt__ check seems to be broken

New submission from Sanjay: The less than check for ip_interface behavior seems weird. I am not sure if this is by design. We are just comparing the network address but when network address is equal we should compare the ip address. The expectation is if a < b is False then b <= a must be True

[issue29928] Add f-strings to Glossary

Jim Fasarakis-Hilliard added the comment: It's odd how 'f-string' just caught on when byte, raw and unicode strings never really did (at least I personally don't see many people using b-string, r-string and u-string respectively). Shouldn't an entry for them be made too if 'f-string' would be

[issue29798] Handle "git worktree" in "make patchcheck"

Nick Coghlan added the comment: No, that's the bug that prompted me to reopen the issue. I just got distracted and never submitted the follow-up PR :( -- ___ Python tracker ___

[issue29921] datetime validation is stricter in 3.6.1 than previous versions

STINNER Victor added the comment: 2017-03-28 10:17 GMT+02:00 m-parry : > "I think it's the case that **some routes via the C API** now reject out of > range values that were previously permitted." > > The pywin32 repro I gave above eventually calls > PyDateTimeAPI->DateTime_FromDateAndTime(): >

[issue29921] datetime validation is stricter in 3.6.1 than previous versions

m-parry added the comment: That's just a Python C API call. It looks like it eventually resolves to new_datetime_ex(30828, 9, 13, 3, 48, 5, 48, Py_None, PyDateTime_DateTimeType). We also have some internal code that sees a similar problem from calling PyTime_FromTime(), that was similarly

[issue29931] ipaddress.ip_interface __lt__ check seems to be broken

Serhiy Storchaka added the comment: Indeed, this looks as a bug. >>> a < b False >>> b > a True -- nosy: +serhiy.storchaka stage: -> needs patch ___ Python tracker ___

[issue29932] Missing word ("be") in error message ("first argument must a type object")

New submission from SylvainDe: Very uninteresting issue but error message should probably be "first argument must BE a type object" in `array__array_reconstructor_impl` in Modules/arraymodule.c . This has been introduced with ad077154d0f305ee0ba5bf41d3cb47d1d9c43e7b . I'll handle this issue i

[issue29930] asyncio.StreamWriter.drain raises an AssertionError under heavy use

Changes by STINNER Victor : Added file: http://bugs.python.org/file46761/server.py ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue29930] asyncio.StreamWriter.drain raises an AssertionError under heavy use

STINNER Victor added the comment: Modified client and server to be able to reproduce the issue on a LAN. -- nosy: +haypo Added file: http://bugs.python.org/file46762/client.py ___ Python tracker ___

[issue29930] asyncio.StreamWriter.drain raises an AssertionError under heavy use

STINNER Victor added the comment: The bug occurs when the transport pauses writing and the client code calls drain() multiple times in parallel. -- ___ Python tracker ___ __

[issue29930] asyncio.StreamWriter.drain raises an AssertionError under heavy use

STINNER Victor added the comment: I understood that: * code fills the write buffer of the transport until writing is paused because of the high water mark * a function calls drain() which waits until the server reads until packets to reduce the size of the write buffer * a second function call

[issue29643] --enable-optimizations compiler flag has no effect

INADA Naoki added the comment: New changeset 8cea5929f52801b0ce5928b46ef836e99a24321a by INADA Naoki (Alex Wang) in branch 'master': bpo-29643: Fix check for --enable-optimizations (GH-129) https://github.com/python/cpython/commit/8cea5929f52801b0ce5928b46ef836e99a24321a -- nosy: +ina

[issue29930] asyncio.StreamWriter.drain raises an AssertionError under heavy use

STINNER Victor added the comment: Proof-of-concept of patched drain() to support multiple waiters. I don't see any strong reason to not allow two coroutines to wait on drain() in parallel? I'm too lazy to write a full patch with unit tests, doc changed, etc. I started with a PoC to discuss th

[issue29643] --enable-optimizations compiler flag has no effect

Changes by INADA Naoki : -- pull_requests: +768 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue29643] --enable-optimizations compiler flag has no effect

Changes by STINNER Victor : -- pull_requests: +769 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue29643] --enable-optimizations compiler flag has no effect

Changes by INADA Naoki : -- pull_requests: +770 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue29921] datetime validation is stricter in 3.6.1 than previous versions

STINNER Victor added the comment: > Again, under <3.6.1, that was accepted. (And again, I am making no argument > about the validity of this code, just with regards to backwards > compatibility.) You are right that I modified the C API of datetime in Python 3.6.1 to make it stricter and rejec

[issue29100] datetime.fromtimestamp() doesn't check min/max year anymore: regression of Python 3.6

STINNER Victor added the comment: m-parry reported the issue #29921 "datetime validation is stricter in 3.6.1 than previous versions". He is right, the C API of Python 3.6.1 is now stricter than Python 2.7 and 3.5. The C API doesn't allow anymore to create datetime objects outside the [datetim

[issue29930] Waiting for asyncio.StreamWriter.drain() twice in parallel raises an AssertionError when the transport stopped writing

Changes by STINNER Victor : -- title: asyncio.StreamWriter.drain raises an AssertionError under heavy use -> Waiting for asyncio.StreamWriter.drain() twice in parallel raises an AssertionError when the transport stopped writing ___ Python tracker <

[issue29921] datetime validation is stricter in 3.6.1 than previous versions

m-parry added the comment: pywin32 is not my code. It is a ubiquitous Python library on Windows that cannot be used under Python 3.6.1. -- ___ Python tracker ___ ___

[issue29932] Missing word ("be") in error message ("first argument must a type object")

Jim Fasarakis-Hilliard added the comment: Indeed, quickly glancing over the error messages there's another small typo in https://github.com/python/cpython/blob/master/Modules/arraymodule.c#L2371: "array indices must be integer" -> "array indices must be integers" might as well fix that in

[issue29643] --enable-optimizations compiler flag has no effect

Changes by INADA Naoki : -- pull_requests: +771 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue29933] asyncio: set_write_buffer_limits() doc doesn't specify unit of the parameters

New submission from STINNER Victor: The asyncio set_write_buffer_limits() documentation doesn't specify unit of high and low parameters. Moreover, it would to explain better the effect of high and low: * pause_writing() is called when the buffer size becomes larger or equal to high * (if writi

[issue29928] Add f-strings to Glossary

R. David Murray added the comment: "raw" and "byte" are one syllable names, and thus as easy and more meaningful to say than "r-string" or "b-string". "unicode string" is more descriptive and not much longer, but "u-string" does occasionally get used, though mostly in a python3 context where

[issue29933] asyncio: set_write_buffer_limits() doc doesn't specify unit of the parameters

STINNER Victor added the comment: See also https://github.com/asyncio-doc/asyncio-doc/issues/17 for a more general documentation request on asyncio parameters (on the external asyncio doc). -- ___ Python tracker

[issue29932] Missing word ("be") in error message ("first argument must a type object")

Jim Fasarakis-Hilliard added the comment: ..and another one here https://github.com/python/cpython/blob/master/Modules/arraymodule.c#L2145: "__reduce_ex__ argument should an integer" -> ".. should be .." -- ___ Python tracker

[issue29929] Eliminate implicit __main__ relative imports

Changes by Barry A. Warsaw : -- nosy: +barry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue29926] time.sleep ignores _thread.interrupt_main()

Terry J. Reedy added the comment: Eryk, would the addition go before or after "trip_signal(SIGINT);" I posted "Issue with _thread.interrupt_main (29926)" on pydev list. Steven D'Aprano verified delayed response on *nix. Martin Panter said "Looking at the implementation, _thread.interrupt_main

[issue29933] asyncio: set_write_buffer_limits() doc doesn't specify unit of the parameters

STINNER Victor added the comment: It would also be nice to: * link to set_write_buffer_limits() from drain() * link to set_write_buffer_limits() from pause_writing() / resume_writing() * mention asyncio default values for set_write_buffer_limits(): low=16 kB, high=64 kB (kb? kib? i never know :

[issue19824] string.Template: Rewrite docs to emphasize i18n use case

Barry A. Warsaw added the comment: New changeset 9f74deba784fc8781d13ed564f69c02ed7c331bb by Barry Warsaw in branch 'master': Improve the documentation for template strings (#856) https://github.com/python/cpython/commit/9f74deba784fc8781d13ed564f69c02ed7c331bb -- ___

[issue20314] Potentially confusing formulation in 6.1.4. Template strings

Barry A. Warsaw added the comment: New changeset 9f74deba784fc8781d13ed564f69c02ed7c331bb by Barry Warsaw in branch 'master': Improve the documentation for template strings (#856) https://github.com/python/cpython/commit/9f74deba784fc8781d13ed564f69c02ed7c331bb -- ___

[issue12518] In string.Template it's impossible to transform delimiter in the derived class

Barry A. Warsaw added the comment: New changeset 9f74deba784fc8781d13ed564f69c02ed7c331bb by Barry Warsaw in branch 'master': Improve the documentation for template strings (#856) https://github.com/python/cpython/commit/9f74deba784fc8781d13ed564f69c02ed7c331bb -- ___

[issue12518] In string.Template it's impossible to transform delimiter in the derived class

Changes by Barry A. Warsaw : -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bug

[issue19824] string.Template: Rewrite docs to emphasize i18n use case

Changes by Barry A. Warsaw : -- resolution: -> fixed stage: needs patch -> resolved status: open -> closed ___ Python tracker ___ ___

[issue20314] Potentially confusing formulation in 6.1.4. Template strings

Changes by Barry A. Warsaw : -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bug

[issue20314] Potentially confusing formulation in 6.1.4. Template strings

Changes by Barry A. Warsaw : -- versions: +Python 3.7 -Python 2.7, Python 3.3, Python 3.4 ___ Python tracker ___ ___ Python-bugs-list

[issue16011] "in" should be consistent with return value of __contains__

R. David Murray added the comment: New changeset 0ae7c8bd614d3aa1fcaf2d71a10ff1148c80d9b5 by R. David Murray (Amit Kumar) in branch 'master': bpo-16011 clarify that 'in' always returns a boolean value https://github.com/python/cpython/commit/0ae7c8bd614d3aa1fcaf2d71a10ff1148c80d9b5 --

[issue29921] datetime validation is stricter in 3.6.1 than previous versions

Ned Deily added the comment: FTR, there is now a pywin32 issue (opened by the OP) on this: https://sourceforge.net/p/pywin32/bugs/748/ -- nosy: +ned.deily ___ Python tracker __

[issue29928] Add f-strings to Glossary

Mariatta Wijaya added the comment: The abstract of PEP 498 states: ``` In this PEP, such strings will be referred to as "f-strings", taken from the leading character used to denote such strings, and standing for "formatted strings". ``` -- ___ Pytho

[issue29694] race condition in pathlib mkdir with flags parents=True

Armin Rigo added the comment: Changes including a test. The test should check all combinations of "concurrent" creation of the directory. It hacks around at pathlib._normal_accessor.mkdir (patching "os.mkdir" has no effect, as the built-in function was already extracted and stored inside pa

[issue16011] "in" should be consistent with return value of __contains__

Changes by Mariatta Wijaya : -- pull_requests: +773 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue16011] "in" should be consistent with return value of __contains__

Changes by Mariatta Wijaya : -- pull_requests: +772 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue10379] locale.format() input regression

Changes by R. David Murray : -- stage: needs patch -> backport needed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue29934] % formatting fails to find formatting code in bytes type after a null byte

New submission from Mert Bora Alper: Hello, In Python 3.6.0, % formatting fails to find formatting code after a null byte in bytes type. Example: >>> "%s_\x00%s" % ("hello", "world") 'hello_\x00world' >>> b"%s_\x00%s" % (b"hello", b"world") Traceback (most recent call last):

[issue29934] % formatting fails to find formatting code in bytes type after a null byte

Changes by Mert Bora Alper : -- components: +Interpreter Core ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: h

[issue10379] locale.format() input regression

Changes by R. David Murray : -- stage: backport needed -> needs patch ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue16011] "in" should be consistent with return value of __contains__

R. David Murray added the comment: Thanks, -- stage: patch review -> backport needed ___ Python tracker ___ ___ Python-bugs-list maili

[issue29934] % formatting fails to find formatting code in bytes type after a null byte

Xiang Zhang added the comment: Yes, this is a regression in 3.6.0 and it has been fixed in #29714 for 3.6.1. Try the new version. :-) -- nosy: +xiang.zhang resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> can't interpolate byte string with \x00 before

[issue29934] % formatting fails to find formatting code in bytes type after a null byte

Xiang Zhang added the comment: Sorry, the fix is for 3.6.2 so 3.6.1 would still suffer from it. :-( -- ___ Python tracker ___ ___ Pyth

[issue29926] time.sleep ignores _thread.interrupt_main()

Eryk Sun added the comment: For Windows the event should be set after trip_signal(SIGINT). That way the flag is guaranteed to be tripped when PyErr_CheckSignals is called from the time module's pysleep() function. This in turn calls the default SIGINT handler that raises a KeyboardInterrupt.

[issue29904] Fix a number of error message typos

Changes by Jim Fasarakis-Hilliard : -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Pyt

[issue11913] sdist refuses README.rst

Ryan Gonzalez added the comment: FWIW, I opened a PR for this: https://github.com/python/cpython/pull/563 -- nosy: +refi64 ___ Python tracker ___

[issue29643] --enable-optimizations compiler flag has no effect

INADA Naoki added the comment: New changeset f01de61a8efea8319c65365898982f929d59a895 by INADA Naoki in branch '3.6': bpo-29643: Fix check for --enable-optimizations (GH-869) https://github.com/python/cpython/commit/f01de61a8efea8319c65365898982f929d59a895 --

[issue29643] --enable-optimizations compiler flag has no effect

INADA Naoki added the comment: New changeset e6a49531568561fe5aaf662259ecb7b4bc2426be by INADA Naoki in branch '3.5': bpo-29643: Fix check for --enable-optimizations (GH-871) https://github.com/python/cpython/commit/e6a49531568561fe5aaf662259ecb7b4bc2426be --

[issue29930] Waiting for asyncio.StreamWriter.drain() twice in parallel raises an AssertionError when the transport stopped writing

Aymeric Augustin added the comment: For context, websockets calls `yield from self.writer.drain()` after each write in order to provide backpressure. If the output buffer fills up, calling API coroutines that write to the websocket connection becomes slow and hopefully the backpressure will pr

[issue29104] Left bracket remains in format string result when '\' preceeds it

Serhiy Storchaka added the comment: Ping again. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue10379] locale.format() input regression

R. David Murray added the comment: New changeset 1cf93a76c2cf307f2e1e514a8944864f746337ea by R. David Murray (Garvit Khatri) in branch 'master': bpo-10379: add 'monetary' to format_string, deprecate format https://github.com/python/cpython/commit/1cf93a76c2cf307f2e1e514a8944864f746337ea -

[issue10379] locale.format() input regression

R. David Murray added the comment: Oops. I merged the patch without coming back here first :(. Still getting used to the new workflow. It turns out that format has a parameter, monetary, that isn't supported by format_string. So what we did was add that parameter to format_string and depre

[issue29908] Inconsistent crashing with an access violation

Steve Dower added the comment: Thanks for the link! I've reported it to the C Runtime team and they'll get it fixed. (Because this is an operating system component, the fix will come through normal Windows Updates and apply to any version of Python 3.5+, so I'd rather not build a workaround in

[issue13349] Non-informative error message in index() and remove() functions

Changes by Jim Fasarakis-Hilliard : -- pull_requests: +775 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue29935] list and tuple index methods should accept None parameters

New submission from George King: As of python3.6, passing None to the start/end parameters of `list.index` and `tuple.index` raises the following exception: "slice indices must be integers or None or have an __index__ method" This suggests that the intent is to support None as a valid input. Th

[issue29677] clarify docs about 'round()' accepting a negative integer for ndigits

Changes by Cheryl Sabella : -- pull_requests: +776 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue29936] Typo in __GNU*C*_MINOR__ guard affecting gcc 3.x

New submission from Niklas Fiekas: The patch in http://bugs.python.org/issue16881 disables the nicer macro for gcc 3.x due to a small typo. The build is not failing. The guard just unnescessarily evaluates to false. -- components: Interpreter Core messages: 290738 nosy: niklasf priorit

[issue29936] Typo in __GNU*C*_MINOR__ guard affecting gcc 3.x

Changes by Niklas Fiekas : -- pull_requests: +777 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue16011] "in" should be consistent with return value of __contains__

Mariatta Wijaya added the comment: New changeset 0957f262c5e47167efd520624557aebdc61bfda8 by Mariatta in branch '3.5': bpo-16011: clarify that 'in' always returns a boolean value (GH-152) (GH-875) https://github.com/python/cpython/commit/0957f262c5e47167efd520624557aebdc61bfda8 -- nos

[issue29936] Typo in __GNU*C*_MINOR__ guard affecting gcc 3.x

Changes by Niklas Fiekas : -- components: +Build -Interpreter Core nosy: +Jeffrey.Armstrong, christian.heimes type: -> compile error ___ Python tracker ___ _

[issue29935] list and tuple index methods should accept None parameters

Changes by Jim Fasarakis-Hilliard : -- components: +Interpreter Core versions: +Python 3.7 ___ Python tracker ___ ___ Python-bugs-list

[issue16011] "in" should be consistent with return value of __contains__

Mariatta Wijaya added the comment: New changeset c4021af50526f488c0c280e7c7eaa83ef80ae1df by Mariatta in branch '3.6': bpo-16011: clarify that 'in' always returns a boolean value (GH-874) https://github.com/python/cpython/commit/c4021af50526f488c0c280e7c7eaa83ef80ae1df -- ___

[issue29935] list and tuple index methods should accept None parameters

Changes by George King : -- type: -> enhancement ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue22049] argparse: type= doesn't honor nargs > 1

Changes by paul j3 : -- resolution: -> not a bug stage: needs patch -> resolved status: open -> closed ___ Python tracker ___ ___ Pyt

[issue29643] --enable-optimizations compiler flag has no effect

INADA Naoki added the comment: New changeset 6a04ef7ceddae0930eba6cc57ba2ebfcef00abab by INADA Naoki in branch '2.7': bpo-29643: Fix check for --enable-optimizations (GH-873) https://github.com/python/cpython/commit/6a04ef7ceddae0930eba6cc57ba2ebfcef00abab --

[issue29643] --enable-optimizations compiler flag has no effect

Changes by INADA Naoki : -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-li

[issue13349] Non-informative error message in index() and remove() functions

Serhiy Storchaka added the comment: >>> [1, 2, 3].index("'") Traceback (most recent call last): File "", line 1, in ValueError: ""'"" not in list Aren't too much quotes? -- ___ Python tracker __

[issue29926] time.sleep ignores _thread.interrupt_main()

Nathaniel Smith added the comment: If you want to trigger the standard signal handling logic, then raise(SIGINT) is also an option. On unix it probably won't help because of issue 21895, but using raise() here + fixing 21895 by using pthread_kill in the c level signal handler would together gi

[issue24251] Different behavior for argparse between 2.7.8 and 2.7.9 when adding the same arguments to the root and the sub commands

Changes by paul j3 : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-li

[issue13349] Non-informative error message in index() and remove() functions

Jim Fasarakis-Hilliard added the comment: Yes, that does look like too much. My rationale for adding quotes around the value was in order to make it more clear in cases where the repr exceeds 100 characters. Instead of: Traceback (most recent call last): File "", line 1, in Value

[issue29926] time.sleep ignores _thread.interrupt_main()

Nathaniel Smith added the comment: (oh, in case it wasn't obvious: the advantage of raise() over kill() and pthread_kill() is that raise() works everywhere, including Windows, so it would avoid platform specific logic. Or if you don't like raise() for some reason then you can get the same effe

[issue23487] argparse: add_subparsers 'action' broken

paul j3 added the comment: I'm going to close this. At most it calls for a documentation change. But saying something like It must be compatible with argparse._SubParsersAction. will just confuse the average user. Any customization of this action class is an advanced topic, that require

[issue13349] Non-informative error message in index() and remove() functions

Jim Fasarakis-Hilliard added the comment: Could use `%.100S` instead of `%.100R` but I'm not sure of the downsides that might entail. -- ___ Python tracker ___ _

[issue13349] Non-informative error message in index() and remove() functions

Serhiy Storchaka added the comment: Error messages should use repr(). For example str() of bytes object emits a warning or error. See issue26090 for the issue with truncated reprs. -- ___ Python tracker _

[issue29936] Typo in __GNU*C*_MINOR__ guard affecting gcc 3.x

Changes by Jeffrey Armstrong : -- nosy: -Jeffrey.Armstrong ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: htt

[issue29926] time.sleep ignores _thread.interrupt_main()

Eryk Sun added the comment: Nathaniel's suggestion to update the implementation to work with raise(SIGINT) sounds like a good idea. Fpr Windows, GenerateConsoleCtrlEvent is definitely a non-starter. PyErr_SetInterrupt shouldn't depend on having an attached console. IDLE generally runs without

[issue29935] list and tuple index methods should accept None parameters

Changes by Serhiy Storchaka : -- assignee: -> serhiy.storchaka nosy: +serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list ma

[issue29937] argparse mutex group should allow mandatory parameters

New submission from Mark Nolan: I see elsewhere, and from use, that a mutex group will not support mandatory positional parameters. TBH, I don't understand why this should be any different from any other option, but if it must, then I think it should follow the 'required' parameter of the mut

[issue29926] time.sleep ignores _thread.interrupt_main()

Terry J. Reedy added the comment: Even is IDLE is started from a console, the user execution process is not attached to one. What I want, from an IDLE perspective, is for ^C in IDLE's shell to work as well as it does in a terminal. That means either fixing _thread.interrupt_main to always do

[issue29931] ipaddress.ip_interface __lt__ check seems to be broken

Changes by Roundup Robot : -- pull_requests: +778 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue19791] test_pathlib should use can_symlink or skip_unless_symlink from test.support

Brett Cannon added the comment: New changeset ec1f5df46ed37aa3e839d20298c4b361a9a74bc4 by Brett Cannon (Vajrasky Kok) in branch 'master': bpo-19791: Use functions from test support to check the symlink support. (GH-822) https://github.com/python/cpython/commit/ec1f5df46ed37aa3e839d20298c4b361a

[issue19791] test_pathlib should use can_symlink or skip_unless_symlink from test.support

Changes by Brett Cannon : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___ P

[issue11566] hypot define in pyconfig.h clashes with g++'s cmath

Changes by Matthew McCormick : -- pull_requests: +780 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://m

[issue29928] Add f-strings to Glossary

Brett Cannon added the comment: I think we're getting bogged down in a larger scope than this issue is about. All we should be discussing in this issue is whether adding an entry in the glossary for "f-string" as it's already being used in the community is bad (which I don't think it is since

  1   2   >