.appveyor.yml

# Reference: https://www.appveyor.com/docs/appveyor-yml/

# branches to build
branches:
  # whitelist
  only:
    - default

# Reference: https://packaging.python.org/guides/supporting-windows-using-appveyor/
environment:

  matrix:

    # For Python versions available on Appveyor, see
    # http://www.appveyor.com/docs/installed-software#python

    - PYTHON: "C:\\Python36-x64"
    - PYTHON: "C:\\Python37-x64"

install:
  - "set PATH=%PYTHON%;%PYTHON%\\Scripts;%PATH%"
  - python -m pip install -U pip setuptools wheel
  - python -m pip install -U pytest black numpy cython

build_script:
  - pip install -e .

test_script:
  # Put your test command here.
  # If you don't need to build C extensions on 64-bit Python 3.3 or 3.4,
  # you can remove "build.cmd" from the front of the command, as it's
  # only needed to support those cases.
  # Note that you must use the environment variable %PYTHON% to refer to
  # the interpreter you're using - Appveyor does not do anything special
  # to put the Python version you want to use on PATH.
  # - "build.cmd %PYTHON%\\python.exe setup.py test"
  #
  # For now, don't test
  # Reference: https://packaging.python.org/guides/supporting-windows-using-appveyor#testing-with-tox
  # echo "TODO: tox tests can be tricky in Windows"
  # - set PYTHONPATH=.
  - python -m pytest transonic data_tests/ipynb

# 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
  # - "build.cmd %PYTHON%\\python.exe setup.py bdist_wheel"

# artifacts:
  # Any remenants after build / test
  # - path: build\*

#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.