From 0e697e2977d5b62ae4ec1ffca16587346f87a96f Mon Sep 17 00:00:00 2001
From: Alexander Neumann <aleneum@gmail.com>
Date: Sat, 30 Sep 2017 18:08:50 +0200
Subject: [PATCH] Add AppVeyor.yml

Enable Windows CI testing
---
 appveyor.yml | 39 +++++++++++++++++++++++++++++++++++++++
 1 file changed, 39 insertions(+)
 create mode 100644 appveyor.yml

diff --git a/appveyor.yml b/appveyor.yml
new file mode 100644
index 00000000..6817365b
--- /dev/null
+++ b/appveyor.yml
@@ -0,0 +1,39 @@
+environment:
+
+  matrix:
+    # http://www.appveyor.com/docs/installed-software#python
+    - PYTHON: "C:\\Python27"
+    - PYTHON: "C:\\Python33"
+    - PYTHON: "C:\\Python34"
+    - PYTHON: "C:\\Python35"
+    - PYTHON: "C:\\Python36"
+    - PYTHON: "C:\\Python27-x64"
+    - PYTHON: "C:\\Python33-x64"
+    - PYTHON: "C:\\Python34-x64"
+    - PYTHON: "C:\\Python35-x64"
+    - PYTHON: "C:\\Python36-x64"
+
+install:
+  - "%PYTHON%\\python.exe -m pip install -r requirements.txt"
+  - "%PYTHON%\\python.exe -m pip install -r requirements_test.txt"
+
+build: off
+
+test_script:
+  - "%PYTHON%\\python.exe -m nose --with-coverage --with-doctest"
+
+#after_test:
+#  # This step builds your wheels.
+#  # Again, you only need build.cmd if you're building C extensions for
+#  # 64-bit Python 3.3/3.4. And you need to use %PYTHON% to get the correct
+#  # interpreter
+#  - "%PYTHON%\\python.exe setup.py bdist_wheel"
+
+#artifacts:
+#  # bdist_wheel puts your built wheel in the dist directory
+#  - path: dist\*
+
+#on_success:
+#  You can use this step to upload your artifacts to a public website.
+#  See Appveyor's documentation for more details. Or you can simply
+#  access your wheels from the Appveyor "artifacts" tab for your build.
\ No newline at end of file