[issue41753] subprocess.run on windows does not convert path to string

[Kaushik G]

Kaushik G  added the comment:

Thank you for your response.

There are two concerns I have here.

1. Python's promise of being straightforward. In MOST cases pathlib.Path 
objects do the right thing, casting to a string such that pathlib.Path is a 
drop in replacement. This exception is unexpected.

2. Cross platform consistency. Looks like this works on macOS and Linux. Why 
should it fail on Windows?

Thanks!

--

___
Python tracker 
<https://bugs.python.org/issue41753>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue41753] subprocess.run on windows does not convert path to string

[Kaushik G]

New submission from Kaushik G :

a call of the form `subprocess.run([x, y, z])` where one of the elements is a 
`pathlib.Pat`h fails on windows because the path is not converted to a string 
as it should. This works fine (as expected) on macOS and Linux.

A typical error message is:

`TypeError: argument of type 'WindowsPath' is not iterable`

--
components: Windows
messages: 376651
nosy: kaushik.ghose, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: subprocess.run on windows does not convert path to string
type: behavior
versions: Python 3.7

___
Python tracker 
<https://bugs.python.org/issue41753>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com