[issue21911] "IndexError: tuple index out of range" should include the requested index and tuple length

Mark Lawrence added the comment: If a programmer can't work out from "IndexError: tuple index out of range" what is going on they should give up programming. Personally I'd close this now with resolution "complete waste of core dev time". -- nosy: +BreamoreBoy type: behavior -> enhanc

[issue21911] "IndexError: tuple index out of range" should include the requested index and tuple length

Ram Rachum added the comment: Mark, again I'm finding myself saying things that are obvious to all of us: You can figure out that "tuple index out of range" means you asked for an item bigger than the size of the tuple, but it might be very helpful for debugging to say the number of item that

[issue21911] "IndexError: tuple index out of range" should include the requested index and tuple length

Mark Lawrence added the comment: Ram I won't be making any more comments as it's quite clear to me that you have no empathy at all with the core devs. -- ___ Python tracker ___

[issue21911] "IndexError: tuple index out of range" should include the requested index and tuple length

Josh Rosenberg added the comment: As I said, the main reason is that every feature has to start at minus 100 points. It's not that your idea is bad, it's that it has to be sufficiently good to warrant the risks that come with any code churn, no matter how small. "Simple and obvious" does not m

[issue21911] "IndexError: tuple index out of range" should include the requested index and tuple length

Ram Rachum added the comment: Josh, I agree with most of what you're saying. (Except the tips about debugging are not helpful, the point is to get the information as quickly as possible without having to make code modifications if possible.) I can totally understand a reaction of "Your idea is

[issue21911] "IndexError: tuple index out of range" should include the requested index and tuple length

R. David Murray added the comment: The development team is not monolithic, and we are all people, with differing opinions (and Mark is Mark). As has been pointed out, there is people-load for development and maintenance associated with any change, so a mature project has a natural tendency to

[issue21911] "IndexError: tuple index out of range" should include the requested index and tuple length

Ram Rachum added the comment: David, as a more generalized solution: Do you think it's possible to make some kind of mechanism in Python that would change the way that an exception is constructed based on whether it's used for control flow or not? I know that it's a bit far-fetched, but if we

[issue14345] Document socket.SOL_SOCKET

Mark Lawrence added the comment: I think this would be worth doing. All I could find out about SOL_SOCKET is that it's an int and has a value of 65535, at least on 3.4.1, Windows 7 32 bit. -- nosy: +BreamoreBoy type: -> behavior versions: +Python 3.4, Python 3.5 _

[issue14418] Document differences in SocketServer between Python 2.6 and 2.7

Mark Lawrence added the comment: @Geoffrey sorry about the delay in getting back to you. -- nosy: +BreamoreBoy, pitrou ___ Python tracker ___

[issue14453] profile.Profile.calibrate can produce incorrect numbers in some circumstances

Mark Lawrence added the comment: @Adam sorry about the delay in getting back to you. @Georg can you comment on the patch please. -- nosy: +BreamoreBoy, georg.brandl versions: +Python 3.5 -Python 2.6, Python 3.1, Python 3.2, Python 3.3 ___ Python trac

[issue14483] inspect.getsource fails to read a file of only comments

Mark Lawrence added the comment: @Sean we're sorry for the delay in getting back to you. -- nosy: +BreamoreBoy, yselivanov ___ Python tracker ___

[issue18212] No way to check whether Future is finished?

Josh Rosenberg added the comment: Have an idea for a name? It already has a done method, which happens to cover the case of a Future having completed successfully, completed due to an exception or having been cancelled. Simply calling it "finished()", "completed()" etc. isn't markedly differen

[issue18212] No way to check whether Future is finished?

Josh Rosenberg added the comment: Ugh. Left out a key word: "I see this as making it even easier to do threading *badly*, rather than a legitimate improvement." -- ___ Python tracker _

[issue14189] Documentation for some C APIs is missing clear specification of the type of reference they return

Josh Rosenberg added the comment: If any of these actually return borrowed references, I'd consider it a serious documentation bug to not mention it. New reference semantics are the default, and while it's best to call them out, it can be assumed in most cases. Returning borrowed references wi

[issue14566] run_cgi reverts to using unnormalized path

Mark Lawrence added the comment: Can we have a response to this security issue please. -- nosy: +BreamoreBoy versions: +Python 3.4, Python 3.5 ___ Python tracker ___

[issue21913] Possible deadlock in threading.Condition.wait() in Python 2.7.7

New submission from Sangeeth Saravanaraj: Python version 2.7.7 Mac OS Darwin Kernel Version 13.2.0 I have the following code which when executed waits to be interrupted by SIGINT, SIGTERM or SIGQUIT. When an object is initialized, it creates a threading.Condition() and acquires() it! The progr

[issue14709] http.client fails sending read()able Object

Mark Lawrence added the comment: Can we have a response to this please. -- nosy: +BreamoreBoy versions: +Python 3.4, Python 3.5 -Python 3.2 ___ Python tracker ___ ___

[issue14709] http.client fails sending read()able Object

Changes by Ned Deily : -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Missing "return" in HTTPConnection.send() ___ Python tracker ___ __

[issue21910] File protocol should document if writelines must handle generators sensibly

Josh Rosenberg added the comment: +1. I've been assuming writelines handled arbitrary generators without an issue; guess I've gotten lucky and only used the ones that do. I've fed stuff populated by enormous (though not infinite) generators created from stuff like itertools.product and the lik

[issue13946] readline completer could return an iterable

Josh Rosenberg added the comment: I agree the design requiring it to pass the same information over and over is a bit odd (I've occasionally had cause to "borrow" some of ipython's niftyness for a plain Python terminal, and making custom completers work is one of the more awkward parts of the

[issue12067] Doc: remove errors about mixed-type comparisons.

Andy Maier added the comment: Uploaded issue12067-expressions_v4.diff to improve the unicode footnote 3, and to revert to using the term "lexicographical" for sequences (after learning that it applies there as well). Also, this version was produced using "hg diff" to make it properly reviewabl

[issue2057] difflib: add patch capability

Terry J. Reedy added the comment: I am going to agree with starting on PyPI if indeed there is not something there now. -- resolution: -> rejected stage: needs patch -> resolved status: open -> closed ___ Python tracker

[issue21913] Possible deadlock in threading.Condition.wait() in Python 2.7.7

Josh Rosenberg added the comment: So you want it to raise the same exception that is raised in Python 3.4? Either way, I don't think this is a deadlock (to get a deadlock, you'd have to have contested locks; this lock is being acquired only once). You're explicitly violating the rules of using

[issue12067] Doc: remove errors about mixed-type comparisons.

Andy Maier added the comment: PS: The v4 patch does not address comments f) and h) from msg04, and it seems to me they do not need to be addressed. -- ___ Python tracker ___

[issue1425127] os.remove OSError: [Errno 13] Permission denied

Josh Rosenberg added the comment: Similar reference regarding the same basic behavior: http://blogs.msdn.com/b/oldnewthing/archive/2012/09/07/10347136.aspx Short version: Indexing and anti-virus tools prevent deletion from occurring. Longer version: DeleteFile (and all the stuff that ultimate

[issue21914] Create unit tests for Turtle guionly

New submission from Lita Cho: Create unit tests for the Turtle library, specifically on their gui commands. -- components: Library (Lib), Tkinter messages: 59 nosy: Lita.Cho, jesstess priority: normal severity: normal status: open title: Create unit tests for Turtle guionly versions:

[issue21914] Create unit tests for Turtle guionly

Lita Cho added the comment: I created tests for the gui portion of Turtle. This file combines both me and Ingrid's work that is specifically the gui tests. -- Added file: http://bugs.python.org/file35846/test_turtle_guionly.py ___ Python tracker

[issue21914] Create unit tests for Turtle guionly

Lita Cho added the comment: I forgot to make it a patch. Created it as a patch for convenience. -- keywords: +patch Added file: http://bugs.python.org/file35847/test_turtle_guionly.patch ___ Python tracker

[issue1425127] os.remove OSError: [Errno 13] Permission denied

Josh Rosenberg added the comment: Please pretend I didn't leave off the actual os.remove call at the end of my second example that bypasses the issue. -- ___ Python tracker __

[issue21915] telnetlib.Telnet constructor does not match telnetlib.Telnet.__init__ docstring

New submission from Garrett Cooper: telnetlib.Telnet.__init__ supports keyword arguments, but the documentation for 2.7.8 ( https://docs.python.org/2/library/telnetlib.html ) claims they're non-keyword arguments. The py3k docs are much better ( https://docs.python.org/3/library/telnetlib.html

[issue21915] telnetlib.Telnet constructor does not match telnetlib.Telnet.__init__ docstring

Changes by Garrett Cooper : -- versions: +Python 2.7, Python 3.4 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue16296] Patch to fix building on Win32/64 under VS 2010

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

[issue21913] Possible deadlock in threading.Condition.wait() in Python 2.7.7

Sangeeth Saravanaraj added the comment: I am convinced that the code is wrong. It was written with wrong assumptions. But Python 2.7 behaves differently compare to Python 3.4. I am not expecting the same behavior in Python 2.7 as in Python 3.4 but I am expecting that some form of exception is

[issue21720] "TypeError: Item in ``from list'' not a string" message

Changes by Berker Peksag : -- nosy: +berker.peksag ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue21720] "TypeError: Item in ``from list'' not a string" message

Changes by Raymond Hettinger : -- assignee: -> rhettinger nosy: +rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list

<    1   2