[issue41669] Case mismatch between "include" and "Include"

[Éric Araujo]

Éric Araujo  added the comment:

Is this the same as #24908 ?

--
nosy: +eric.araujo

___
Python tracker 

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

[issue41669] Case mismatch between "include" and "Include"

[Steve Dower]

Steve Dower  added the comment:

Unfortunately, it's easier to change what we distribute, except that has 
_always_ been "include" (based on a 2.4 installer I had laying around). And of 
course we can't change the repo.

Still, case sensitivity is becoming more acceptable on Windows and there are 
more ways to enable it, so we're probably best to deal with this. For 3.10, we 
can update PC/layout/main.py and tools/msi/common.wxs#L80 to create "Include", 
and we probably want to go over the few places where we may reference it to 
make sure the case is consistent. (Noting that distutils is fully deprecated in 
3.10, so it doesn't matter.)

I'm not sure that it qualifies as enough of a bugfix for 3.8 or 3.9.1, so I 
think we'll leave them alone. A case-sensitive file system can easily support a 
symlink/junction from "Include" to "include" anyway, which is a pretty 
straightforward workaround ;)

--
versions: +Python 3.10 -Python 3.8

___
Python tracker 

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

[issue41669] Case mismatch between "include" and "Include"

[Gregory Szorc]

New submission from Gregory Szorc :

On Windows, `sysconfig.get_path('include')` returns `Include` (capital I).

However, the actual installation path is `include` (lowercase i).

I believe the reason for the case mismatch is in this code in PC/layout/main.py:

```
if ns.include_dev:

for dest, src in rglob(ns.source / "Include", "**/*.h"):
yield "include/{}".format(dest), src
src = ns.source / "PC" / "pyconfig.h"
yield "include/pyconfig.h", src
```

The case mismatch is relevant for case sensitive filesystems. In my case, I was 
extracting a Windows Python install on Linux and then using the `sysconfig` 
value to locate directories within that install. Due to the case mismatch, 
Linux says `Include` doesn't exist since `sysconfig` points to "include."

Case only renames can be a bit wonky to perform. I would suggest preserving 
what is shipped today and changing `sysconfig` to advertise lowercase 
"include." However, this would create a mismatch between the cpython source 
repo and built distributions. So maybe attempting the case-only rename is 
doable.

Note that Windows will not allow you to have a file/directory varying only in 
case. i.e. you can have both an "include" and "Include." I can't recall if you 
can perform a case-only rename with a single system call (meaning it is atomic) 
or whether you need to go through a temporary directory.

--
components: Windows
messages: 376131
nosy: indygreg, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: Case mismatch between "include" and "Include"
type: behavior
versions: Python 3.8

___
Python tracker 

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