Russ Nelson

By the way, if you're running pyupdater, you don't get a chance to sign the executable, as it runs pyinstaller and the exe goes straight into the .zip file. Here's...

What about using a list instead of a string, where each element of the list is a component of the path. On the one hand, it seems like you would...

Which is fine, but my suggested solution still applies. Python has a perfectly fine system for expressing metadata like this.

Oh, no, no, it's much uglier than that: --add-data [["C:","path","to","source"]["path","to","dest"]] Or, if you use the trope: --add-data[ "C:/path/to/source".split("/"), "path/to/dest".split("/")]

Can you explain why embedded spaces in path names can be a problem? Windows uses them all the time, e.g. in Program Files. Works fine with anything where you aren't...

I agree. A problem in Linux. Not Windows. Windows users expect filenames to have spaces. If you're going to complain about a problem on Linux, then you shouldn't use a...

Let's say, then, that your change would be accepted. How would people specify that they want their program name to be passed-through to the filename with no changes?

Yes, pyinstaller builds the .exe, and then somebody (pyinstaller? pyupdater?) has to sign it before it goes into the .zip file. I haven't found any information about either entity having...

I've found a not-exactly-workaround workaround: sign it in the pyinstaller .spec file. It's Python after all. Since writing this comment, I've found that I can insert these two lines after...

Could you share your PyUpdater client code which is producing this output? If necessary, can you put it into a small test program?