> Isn't this breaking backwards compatibility? We would need to check > what Python plugins this breaks.
It is. I assume that nobody used `vim.buffers[i]` due to inability to determine `i`. Case `for buffer in vim.buffers` which was likely used to find buffer with given number is covered by one of the subsequent patches with iterator. I have not used either in scripts, only `vim.current.buffer` and `vim.windows[i].buffer`. Note that previous assumption is not true for me: without documentation telling what exactly is `i` I used to think `vim.buffers[i]` is “get vim.buffer object for buffer `i+1`”. I have not ever used this in scripts though; scripts that follow this assumption are broken from the very beginning in any case. By the way, can I remove `_()` around all exception messages? Translating exceptions in python world is not a common practice: you can easily get Unicode* error. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
