simon mackenzie added the comment:
I note os.path.realpath("v1") does produce the right path in windows. Maybe
that is what you meant. Will that work cross-platform?
On Tue, 19 Jan 2021 at 18:48, simon mackenzie wrote:
> For most people the expectation would be that it returns
simon mackenzie added the comment:
For most people the expectation would be that it returns a path in the same
format as any other path. Furthermore it seems odd to change the default
behaviour after years when it worked as expected. I never heard of this
substitute path before and it does not
New submission from simon mackenzie :
os.readlink gives wrong result on python 3.8 onwards for windows
os.readlink("c:/users/simon/v1")
'?\\d:\\v1'
Should read d:\\v1
--
components: Windows
messages: 385218
nosy: paul.moore, simon mackenzie, steve.dower, t
simon mackenzie added the comment:
Would be clearer if the arguments were listed before the return object.
On Thu, 15 Aug 2019 at 15:05, SilentGhost wrote:
>
> SilentGhost added the comment:
>
> But docs don't say that at all. You're looking at description of an
&
simon mackenzie added the comment:
Technically true but I am not the first person to have incorrectly
interpreted this that it can be a string which suggests it is not clear to
the reader. Maybe should be explicitly stated in the description of run as
it is not obvious or intuitive.
On Thu
New submission from simon mackenzie :
The docs for subprocess.run say "The arguments used to launch the process. This
may be a list or a string."
This works in windows but in linux it has to be a list. Either needs fixing or
the docs need to be changed.
--
messages: 3
