How to install Python package from source on Windows

[Jussi Piitulainen]

Chris Angelico writes:

> On Sun, May 21, 2017 at 8:23 PM, bartc wrote:
>> On 20/05/2017 19:37, Chris Angelico wrote:
>>
>>> rosuav at sikorsky:~/linux$ find -name \*.c -or -name \*.h | wc -l
>>> 44546
>>>
>>> These repositories, by the way, correspond to git URLs
>>> https://github.com/python/cpython,
>>> git://pike-git.lysator.liu.se/pike.git,
>>> git://source.winehq.org/git/wine, and
>>> https://github.com/torvalds/linux respectively, if you want to check
>>> my numbers. Two language interpreters, a popular execution subsystem,
>>> and an OS kernel.
>>>
>>> I'd like to see you create a single-file version of the Linux kernel
>>> that compiles flawlessly on any modern compiler and has no configure
>>> script.
>>
>>
>> I've had a look at the Linux stuff. (BTW, when copying to Windows,
>> the file "aux" occurs several times, which causes problems as it's a
>> reserved filename I think. Also there were a dozen conflicts where
>> different versions of the same file wanted to be stored at the same
>> location.)
>
> I don't understand where you would have obtained the sources that
> there are duplicate files. It's easiest just to clone someone's git
> repo (eg Linus Torvald's).

It happened to me recently when cloning a git repository from GitHub,
using GitHub Desktop, to a Mac OS file system. Some filenames differed
only in case, like "INFO" and "info" in the same directory. Mac OS
considered them the same file, Git tried to associate them with
different objects, or something like that. Cat-astrophic :)

Something similar happened on Windows with filenames that ended in a
period, in the same repository after the problems on Mac OS had been
fixed. Apparently Windows considers "log-3.1." the same as "log-3.1" -
is that right? (This cloning attempt was not made by me but by a
colleague who has access to a Windows computer. It was mostly calendar
dates in a format that uses periods.)

I was surprised that Git (or GitHub Desktop) simply failed so badly.
Not sure what it could have done instead.

(There were also filenames that Mac OS or Windows rejected. Also
filenames that were truly horrible - a couple contained backspaces.)

Incidentally, I used Python scripts to find and fix issues in those
filenames, including character encoding issues. Smooth sailing :)