[issue18162] Add index attribute to IndexError

2015-04-15 Thread Ofer Schwarz
Changes by Ofer Schwarz : Added file: http://bugs.python.org/file39060/indexerror_all.patch ___ Python tracker <http://bugs.python.org/issue18162> ___ ___ Python-bug

[issue18162] Add index attribute to IndexError

2015-04-15 Thread Ofer Schwarz
Changes by Ofer Schwarz : -- keywords: +patch Added file: http://bugs.python.org/file39055/indexerror.patch ___ Python tracker <http://bugs.python.org/issue18

[issue18162] Add index attribute to IndexError

2015-04-15 Thread Ofer Schwarz
Changes by Ofer Schwarz : Added file: http://bugs.python.org/file39056/indexerror.tests ___ Python tracker <http://bugs.python.org/issue18162> ___ ___ Python-bugs-list m

[issue18162] Add index attribute to IndexError

2015-04-15 Thread Ofer Schwarz
Ofer Schwarz added the comment: I'm working on this now (patch hopefully coming soon), and I've hit an interesting issue: PySequence methods take care of negative indexes by adding +len before calling the subclass method (s.t. -1 becomes len-1 etc.). This means that if the subclass

[issue23960] PyErr_SetImportError doesn't clean up on some errors

2015-04-14 Thread Ofer Schwarz
New submission from Ofer Schwarz: When creating kwargs to construct the ImportError, if PyDict_SetItemString fails the function returns without decref'ing the already-created locals. -- components: Interpreter Core files: importerrorcleanup.patch keywords: patch messages: 241052

[issue18166] 'value' attribute for ValueError

2015-04-14 Thread Ofer Schwarz
Ofer Schwarz added the comment: So, this is actually impossible to do. Since exceptions are c-level classes, adding members to ValueError means anything that multiple-inherits from ValueError and any other complex exception gets a multiple bases layout conflict. There's already one such

[issue18166] 'value' attribute for ValueError

2015-04-14 Thread Ofer Schwarz
Ofer Schwarz added the comment: There's actually no advantage for a weakref here, since the exception object already holds an indirect reference to all the raising frame's locals through __traceback__. -- nosy: +blackfawn ___ Python trac

[issue21345] multiprocessing.Pool._handle_workers sleeps too long

2015-04-13 Thread Ofer Schwarz
Ofer Schwarz added the comment: I couldn't reproduce this on my machine, but I have no idea if I'm using the wrong sequence of operations, or type of pool, or if my machine is just faster or something else entirely. Johannes, can you upload a repro code for this? -- nosy: