[issue40732] New realpath breaks setuptools_scm

Jason R. Coombs added the comment: Good news is it looks like the issue with setuptools_scm can be address in a relatively straightforward manner (https://github.com/pypa/setuptools_scm/issues/436#issuecomment-632899446). I think that means the answers to the above questions are: - Downstre

[issue40732] New realpath breaks setuptools_scm

Jason R. Coombs added the comment: To make matters more complicated, `git rev-parse --show-toplevel` also returns the realpath: ``` # git rev-parse --show-toplevel //vmware-host/Shared Folders/home/code/main/path ``` -- ___ Python tracker

[issue40732] New realpath breaks setuptools_scm

Jason R. Coombs added the comment: It's because on Unix: ``` >>> os.path.relpath('/Users/jaraco/code/main/path/.flake8', '') '.flake8' ``` But on Windows, relpath raises an error for the comparable call: ``` >>> os.path.relpath('vmware-host\\shared >>> folders\\home\\code\\main\\path\\.

[issue40732] New realpath breaks setuptools_scm

Jason R. Coombs added the comment: It seems the underlying reason the behavior fails is the (intended) difference resolving the empty path to a realpath when a symlink points to another volume. The failing routine invokes realpath early (https://github.com/pypa/setuptools_scm/blob/d7c122e14c

[issue40732] New realpath breaks setuptools_scm

Change by Jason R. Coombs : -- nosy: +eryksun ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue40732] New realpath breaks setuptools_scm

New submission from Jason R. Coombs : I've encountered an apparent regression on Python 3.8 on Windows when the current working directory is in a symlink to another volume and one runs `setup.py develop` on a project using setuptools_scm (https://github.com/pypa/setuptools_scm/issues/436). I