Windows support in Travis CI

[cher-nov]

FYI
https://blog.travis-ci.com/2018-10-11-windows-early-release
https://travis-ci.community/t/python-support-on-windows/241

And yes, your project is simply amazing, keep up the good work!

[hannes]

FWIW, I managed to get cibuildwheel to work on Windows Travis, here the relevant snippet of my .travis.yml

language: cpp

before_install:
  - eval "${MATRIX_EVAL}"

env:
  global:
    - CIBW_BUILD='cp37-*'
    - CIBW_TEST_REQUIRES='pytest'
    - CIBW_BEFORE_BUILD='pip install "numpy>=1.16" && pip install "pandas>=0.24" && pip install "pytest>=4.3" && pip install cmake==3.13.3'
    - CIBW_TEST_COMMAND='python -m pytest {project}/tests'

matrix:
  include:

    - os: windows
      name: Python Package
      language: cpp
      filter_secrets: false

      before_install:
        - choco install python3 --version 3.7.3 --sidebyside -y --forcex86 --force --params "/InstallDir:C:\Python37"
        - choco install python3 --version 3.7.3 --sidebyside -y --force --params "/InstallDir:C:\Python37-x64"

        - C:/Python37-x64/python.exe -m pip install --upgrade pip
        - C:/Python37-x64/python.exe -m pip install "cibuildwheel==0.10.2"

      script:
        - cd tools/pythonpkg
        - C:/Python37-x64/python.exe  setup.py sdist
        - mkdir duckdb_tarball && tar xvf dist/duckdb-*.tar.gz --strip-components=1 -C duckdb_tarball
        - C:/Python37-x64/python.exe -m cibuildwheel --platform windows --output-dir wheelhouse duckdb_tarball
        - cd ../..

[Czaki]

#160 is merged. So you may close this issue.

[cher-nov]

@joerick Could you please also state this in the ReadMe?

[Czaki]

It is in readme.

[cher-nov]

@Czaki https://github.com/joerick/cibuildwheel#usage

cibuildwheel currently works Travis CI and CircleCI to build Linux and Mac wheels, and AppVeyor to build Windows wheels. Azure Pipelines supports all three.

This is slightly unclear.

[YannickJadoul]

Thanks, @cher-nov! We missed that when @Czaki recently added support for Windows on Travis CI :)

I've just pushed a quick commit to the README that has fixed the mistake: 8c9345f

(@joerick, I didn't think a single line in the README was worth a full PR and review; but feel free to correct if you want to formulate it differently!)

[joerick]

All good, thanks for the report & update :)