2017-04-10 5:54 GMT+03:00 Yggdroot <[email protected]>: > For example, py3 print( repr(vim.current.buffer.options["filetype"]) ) will > print b'cpp' but not 'cpp', > while neovim will return a string. > I think it's not reasonable to return a bytes.
Most Vim strings are not guaranteed to contain valid &encoding-encoded values, unlike another option (using surrogateescape for invalid characters) this forces you to think about handling possible conversion errors right away, before you run into related bugs. Also Python 2 has used bytes() always. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > > -- > -- > 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/d/optout. -- -- 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/d/optout.
