[issue14133] improved PEP 409 implementation

Benjamin Peterson added the comment: I don't think it's a good idea for setting one attribute to implicitly set another. -- ___ Python tracker ___ _

[issue8706] accept keyword arguments on all base type methods and builtins

Ramchandra Apte added the comment: See also issue14081 which got fixed. -- nosy: +ramchandra.apte ___ Python tracker ___ ___ Python-bu

[issue14139] test_ftplib: segfault

Ramchandra Apte added the comment: On my Linux machine it does not crash. -- nosy: +ramchandra.apte ___ Python tracker ___ ___ Python

[issue14133] improved PEP 409 implementation

Nick Coghlan added the comment: The alternatives are a backwards compatibility break (i.e. raise exc from other_exc would suppress the context, but exc.__cause__ = other_exc would not) or else that we don't succeed in eliminating the dual use of __cause__ in the display routines. Given that

[issue14133] improved PEP 409 implementation

Nick Coghlan added the comment: Also, ensuring class invariants by setting derived attributes correctly is one of the primary use cases for properties, so objecting to my proposed approach is objecting to a fairly fundamental programming technique. --

[issue8706] accept keyword arguments on all base type methods and builtins

Ramchandra Apte added the comment: Can we have keyword arguments to range([start],stop,[step])? -- ___ Python tracker ___ ___ Python-b

[issue14145] string.rfind() returns AttributeError: 'list' object has no attribute 'rfind'

New submission from Griffin Smith : This occurs even when calling methods in modules (such as os.path.splitext), so I know it's not happening due to an error on my part Win7 SP1 -- components: Windows messages: 154529 nosy: glittershark priority: normal severity: normal status: open ti

[issue14145] string.rfind() returns AttributeError: 'list' object has no attribute 'rfind'

R. David Murray added the comment: You'll have to give more details about what you are doing, but I suspect you are in fact calling it incorrectly. In addition, there are pretty much no circumstances in which you want to use string.rfind in 2.7. Just use ''.rfind. -- nosy: +r.david.

[issue14145] string.rfind() returns AttributeError: 'list' object has no attribute 'rfind'

R. David Murray added the comment: Ah, perhaps you *meant* you are calling rfind on a string, rather than calling rfind on the 'string' module as I imagined. So, we definitely need more details about how you are producing this failure and what the traceback looks like. 'abc'.rfind('a') works

[issue14145] string.rfind() returns AttributeError: 'list' object has no attribute 'rfind'

Griffin Smith added the comment: Sorry about the lack of clarity there. I'm calling os.path.splitext("C:\blah.ext") and trackback is returning an AttributeError: 'list' object has no attribute 'rfind' from within the definition for splitext in the NTPath module. That's only the specific usag

[issue14146] IDLE: source line in editor doesn't highlight when debugging

New submission from Rich Rauenzahn : Using 64bit python for windows downloaded from python.org on 64bit windows 7. Python Version 3.2.2 Tk version 8.5 IDLE version 3.2.2 When stepping through code the corresponding line in the editor does not highlight with the code steps. The windows does up

[issue8706] accept keyword arguments on all base type methods and builtins

Raymond Hettinger added the comment: range() has been around 20+ years and there has been zero need for keyword arguments for it. FWIW, the maxsplit keyword argument was a case where a keyword argument added clarity, and there may be a handful of other cases that are also warranted. Greg Sm

[issue12905] multiple errors in test_socket on OpenBSD

Remi Pointel added the comment: I think we could close this bug because it's du to the pthread library on OpenBSD and not Python. We are switching to rthreads and I can't reproduce this bug. Thanks for your help and sorry for the delay. -- ___ Pyth

[issue12903] test_io.test_interrupte[r]d* blocks on OpenBSD

Remi Pointel added the comment: I think we could close this bug because it's du to the pthread library on OpenBSD and not Python. We are switching to rthreads and I can't reproduce this bug. Thanks for your help and sorry for the delay. -- ___ Pyth

[issue12905] multiple errors in test_socket on OpenBSD

Charles-François Natali added the comment: > I think we could close this bug because it's du to the pthread library > on OpenBSD and not Python. Indeed. -- resolution: -> invalid stage: -> committed/rejected type: -> behavior ___ Python tracker

[issue12903] test_io.test_interrupte[r]d* blocks on OpenBSD

Changes by Charles-François Natali : -- resolution: -> invalid stage: patch review -> committed/rejected status: open -> closed ___ Python tracker ___ __

<    1   2