On Apr 14, 2016, at 3:29 AM, Victor Stinner <victor.stinner@gmail.com> wrote:
IMHO it's more a side effect of the implementation than a deliberate choice. For new code which really want to support bytes paths, I suggest to only accept bytes and bytes subclasses.

">

(original) (raw)

Yes, in the 3.2 time frame there was a consensus that only bytes and their subclasses should be accepted. buffer support crept back into the posix module with the major changes in 3.3, likely by mistake. A couple new issues are proposed to remove these inconsistencies/regressions:

http://bugs.python.org/issue26800

--
Philip Jenvey

On Apr 14, 2016, at 3:29 AM, Victor Stinner <victor.stinner@gmail.com> wrote:

IMHO it's more a side effect of the implementation than a deliberate choice. For new code which really want to support bytes paths, I suggest to only accept bytes and bytes subclasses.