Some python libraries do not support extended-length path(UNC path).

[dhmemi]

Description of the bug:

Bazel modified the python packages path into extended-length path to support paths bigger than 256 characters in this PR: #2496 . But there are many python libraries that don't support extended-length path，include some python built-in packages like os.path .

See related issues for more details:

• extended-length path with forward slash on windows rules_python#680
• support srearch template with extended-length path sphinx-doc/sphinx#10374

What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

According to the Microsoft's documentation, Maybe we can support paths bigger than 256 characters without prefix \\?\ which is not compatible with forward slash on windows 10.1607 or later version.

But it need to be test, and I'm not sure if there is any other codes in bazel related to this bug.

Which operating system are you running Bazel on?

Windows 10

What is the output of bazel info release?

release 4.1.0

If bazel info release returns development version or (@non-git), tell us how you built Bazel.

No response

What's the output of git remote get-url origin; git rev-parse master; git rev-parse HEAD ?

No response

Have you found anything relevant by searching the web?

#2504

Any other information, logs, or outputs that you want to share?

No response

[UlrichEckhardt]

Interesting, I just stumbled across this issue in the context of Gcovr or, rather the Jinja2 template renderer it uses. I'm seeing this using 5.1.1 though.

[comius]

#15745