warner
commented
6 years ago Oops, actually the filename is fine. The href has the embedded slash, but clicking on the link causes a download option that gets the right name. The only thing that appears to fail is cut-and-paste the link and then downloading it with e.g. wget: that leaves you with a file named dist%2Fzfec-1.5.2-cp27-cp27m-win32.whl. But I'm guessing that's a bug in the way appveyor displays the pathnames.
Appveyor is a windows CI service (like Travis, but only for windows). We're using it for tests and to build binary wheels, since I don't have a windows machine of my own. There's a section in the .appveyor.yml config file that's supposed to upload the generated .whl file into the Appveyor "Artifacts" archive, but the config is doing the wrong thing, since the generated filename has an embedded backslash:
dist\zfec-1.5.2-cp36-cp36m-win32.whlhttps://ci.appveyor.com/project/tahoe-lafs/zfec/build/job/4yaq2osd7v2hiiar/artifacts
I don't yet know what the correct syntax is, to get a variably-named file in the dist/ directory. On Tahoe-LAFS we tried just - path: dist, and that produces a single zipfile named dist.zip which contains the whole directory. What I want is to get separate artifact files for every file inside dist/, and I don't know the name of the files ahead of time (since they'll depend upon the version number and commit id).