This looks like a bug to me - can you file it on the issue tracker.
Evidently I did not consider python 2 behavior when backporting `os.fspath`
from python 3.
Eric
On Mon, 14 Jan 2019 at 16:28 Stuart Reynolds
wrote:
> After a recent upgrade of numpy (1.13.1 -> 1.6.0), my code is failing
> wher
After a recent upgrade of numpy (1.13.1 -> 1.6.0), my code is failing where
I provide unicode objects as filenames.
Previously they were allowed. Now that are not, and I *must* provide a
(py2) str or bytearray only.
# str is OK
$ python2.7 -c "from numpy.compat import py3k; print py3k.os_fspath('1
