On Fri, Nov 20, 2020 at 10:25 AM Paul Moore <p.f.mo...@gmail.com> wrote: > But what > you end up with is someone discovering that the file you sent with > doesn't work "because it's written in Python, not in <pick another > language that writes native exes>". >
The converse is someone discovering that the file you sent doesn't work "because it was built on Windows, not on <pick another platform that supports Python>". So long as the ONLY operating system, architecture, word size, etc, is the one that you're currently using, it's easy! Just bundle everything and the job's done. How many other architectures will you support? Will your app run? I have had *endless* frustration caused by otherwise cross-platform applications being unnecessarily bundled into native binaries. Why do it? Why cause pain for people just because they've chosen a different OS - or maybe even just because they happen to have a 32-bit version of Windows and you made a 64-bit binary? Hence the descriptor "attractive nuisance". I stand by that. It becomes temptingly easy to do the wrong thing and make pain for people that you don't even know you should be supporting. ChrisA _______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/MP56J67KNWCXMPKQYQNMOSA3SAAV27WE/ Code of Conduct: http://python.org/psf/codeofconduct/
