> If during the release process, appveyor could build the Windows wheels on py2.7 and py3, and then upload them to pypi, that would be ideal.
Last I checked AppyVeyor can't do this directly. I ended up writing a command line tool to make releases for pywincffi which uses this class to pull release artifacts from a build on AppVeyor: https://github.com/opalmer/pywincffi/blob/master/pywincffi/dev/release.py#L392 The PR mentioned above appears to already push artifacts using sftp so if you wanted to pull artifacts for a specific build you could use the above. I don't know enough about Twisted's release process to know if the above will be useful but if you need to access all artifacts for a branch of the last passing build the above should do it. As for building wheels for Windows on AppVeyor it might be worth looking at the one I've come up with: https://github.com/opalmer/pywincffi/blob/master/appveyor.yml The most notable difference probably is that I'm creating an environment variable called %WITH_COMPILER% which points at a script <https://github.com/opalmer/pywincffi/blob/master/.ci/appveyor/run_with_compiler.cmd> that sets up additional environment variables prior to the install <https://github.com/opalmer/pywincffi/blob/master/.ci/appveyor/install.cmd> or other scripts running. I don't know enough about Twisted's build to know if it's needed but without those environment variables I ended up having problems getting builds through for Python 2/3 for both 32-bit and 64-bit variants even when using setuptools. I don't know if the situation has improved since but it might be worth looking at if Twisted's build on appyveor runs into issues. On Mon, Jan 8, 2018 at 3:56 PM, Craig Rodrigues <rodr...@crodrigues.org> wrote: > > > On Sun, Jan 7, 2018 at 10:14 PM, Adi Roiban <a...@roiban.ro> wrote: > >> >> I no longer have time to work on it, but I think that is possible to >> build wheels for py2.7 and py3 on appveyor >> > > > If during the release process, appveyor could build the Windows wheels on > py2.7 and py3, and then upload > them to pypi, that would be ideal. > > Didn't you implement something for one of the Twisted subprojects where if > a git tag was created and pushed to github, then it would build and upload > to pypi? > That would be the ideal thing to implement with appveyor for the main > Twisted project. > > -- > Craig > > _______________________________________________ > Twisted-Python mailing list > Twisted-Python@twistedmatrix.com > https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python > >
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
