<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">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:<div class=""><div class=""><br class=""></div><div class=""><a href="http://bugs.python.org/issue26754" class="">http://bugs.python.org/issue26754</a></div><div class=""><a href="http://bugs.python.org/issue26800" class="">http://bugs.python.org/issue26800</a><br class=""><div class=""><br class=""><div class="">
<div class=""><div class="">--</div><div class="">Philip Jenvey</div></div>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On Apr 14, 2016, at 3:29 AM, Victor Stinner <<a href="mailto:victor.stinner@gmail.com" class="">victor.stinner@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><p dir="ltr" class="">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.</p></div></blockquote></div><br class=""></div></div></div></body></html>