Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add .appveyor.yml #200

Merged
merged 1 commit into from Jul 25, 2016
Merged

Add .appveyor.yml #200

merged 1 commit into from Jul 25, 2016

Conversation

mhils
Copy link
Contributor

@mhils mhils commented Jul 25, 2016

This PR adds an AppVeyor configuration that auto-builds lxml wheels for Python 2.7 and 3.5 on Windows:
https://ci.appveyor.com/project/mhils/lxml/build/1.0.25

If you click on the individual jobs, you can go to the artifacts tab and download the wheels from AppVeyor. I tested both the Python 2.7 and 3.5 binaries and they all seem to work 馃槂

@scoder
Copy link
Member

scoder commented Jul 25, 2016

Thanks!

@scoder scoder merged commit 44df3f0 into lxml:master Jul 25, 2016
@mhils mhils deleted the appveyor branch July 25, 2016 19:29
@mhils
Copy link
Contributor Author

mhils commented Jul 25, 2016

Thanks for the quick merge! I guess you still have to sign up at appveyor.com to get builds for this repo (I can only activate them for mhils/lxml),, but that should be a two minute thing. It'd be awesome if you could upload the resulting wheels to PyPI 馃槉

@mvantellingen
Copy link
Contributor

Can we also do this for Python 3.3 and 3.4? That would make testing libraries on windows against lxml much easier (I use it for https://github.com/mvantellingen/python-zeep/blob/master/appveyor.yml).

I can work on this, but perhaps there was a reason that 3.3 and 3.4 were excluded

@scoder
Copy link
Member

scoder commented Jul 27, 2016

pre-Py3.5 wheels are already available. See https://pypi.python.org/pypi/lxml/3.6.0. They should eventually become available for 3.6.1 as well. Py3.5 uses a newer C compiler, which makes it a different target than the previous versions.

Note that it's generally a good idea to specify the dependency versions in your requirements.txt file instead of relying on the latest version.

@scoder
Copy link
Member

scoder commented Jul 27, 2016

I tried building on appveyor, but it keeps failing:

Build started
git clone -q --branch=master https://github.com/lxml/lxml.git C:\projects\lxml
Specify a project or solution file. The directory does not contain a project or solution file.

I tried setting the configuration file name explicitly to .appveyor.yml in the settings, but that doesn't help. Any hints?

@mhils
Copy link
Contributor Author

mhils commented Jul 27, 2016

If you set the filename to .appveyor.yml on the website, the next commit/push should build - maybe force that by pushing a new random branch?

@mhils
Copy link
Contributor Author

mhils commented Aug 2, 2016

@scoder: Did you get AppVeyor to work? Is there anything I can help you with to get this going?

@scoder
Copy link
Member

scoder commented Aug 6, 2016

No, no change so far and I won't have time to take a deeper look any time out.

@mhils
Copy link
Contributor Author

mhils commented Aug 18, 2016

Excited to see manylinux wheels up on PyPi! 馃槂
Please let me know if I can help getting this going again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants