Charles-François Natali <neolo...@free.fr> added the comment: > But at the heart of the matter, I see no benefit to exposing Python > developers to the idiosyncrasies of poor C API design. I feel strongly that > one way Python becomes "pythonic" is that it aims for the convenience of the > programmer--not the language designer and not the implementer. The Python > calling convention is far more flexible than the C calling convention. We > should put it to good use here.
I agree. However, I think Martin is a proponent of the "thin wrapper" approach, so it'd be nice to have his input on this. I personally like the change, except for `flags` argument collapsing. Imagine what mmap's prototype would look like if we used list of optional arguments instead of a flag... ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue15078> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
