v0.1.0

Cargo.toml

@@ -1,9 +1,9 @@
 [package]
 authors = ["konstin <[email protected]>"]
 name = "pyo3-pack"
-version = "0.0.2"
-description = "Build and publish python packages from crates with pyo3 bindings"
-exclude = ["get_fourtytwo/**/*", "integration-test/**/*", "ci/*"]
+version = "0.1.0"
+description = "Build and publish crates with pyo3 bindings as python packages"
+exclude = ["get_fourtytwo/**/*", "integration-test/**/*", "sysconfig/*"]
 readme = "Readme.md"
 repository = "https://github.com/pyo3/pyo3-pack"
 license = "MIT OR Apache-2.0"

Readme.md

@@ -8,7 +8,7 @@
 
 Build and publish crates with pyo3 bindings as python packages.
 
-This project is meant as a zero configuration replacement for [setuptools-rust](https://github.com/PyO3/setuptools-rust). It supports building wheels for python 2.7 and 3.5+ on windows, linux and mac and can uploads them to pypi.
+This project is meant as a zero configuration replacement for [setuptools-rust](https://github.com/PyO3/setuptools-rust). It supports building wheels for python 2.7 and 3.5+ on windows, linux and mac and can upload them to pypi.
 
 ## Usage
 
@@ -81,7 +81,7 @@ OPTIONS:
 
 ### Manylinux and auditwheel
 
-For portability reasons, native python modules on linux must only dynamically link a set of very few libraries which are installed basically everywhere, hence the name manylinux. The pypa offers a special docker container and a tool called [auditwheel](https://github.com/pypa/auditwheel/) to ensure compliance with the [manylinux rules](https://www.python.org/dev/peps/pep-0513/#the-manylinux1-policy). pyo3-pack contains a reimplementation of the most important part of auditwheel that is run when building, so there's no need to use external tools. If for some reason you want to disable this check, use the `--skip-auditwheel` flag.
+For portability reasons, native python modules on linux must only dynamically link a set of very few libraries which are installed basically everywhere, hence the name manylinux. The pypa offers a special docker container and a tool called [auditwheel](https://github.com/pypa/auditwheel/) to ensure compliance with the [manylinux rules](https://www.python.org/dev/peps/pep-0513/#the-manylinux1-policy). pyo3-pack contains a reimplementation of the most important part of auditwheel that checks the generated library, so there's no need to use external tools. If you want to disable the manylinux compliance checks for some reason, use the `--skip-auditwheel` flag.
 
 ## Code
 

appveyor.yml

@@ -6,9 +6,6 @@ environment:
   global:
     RUST_BACKTRACE: full
   matrix:
-    # For the integration test
-    - TARGET: x86_64-pc-windows-msvc
-      CHANNEL: nightly
     # 32-bit
     - TARGET: i686-pc-windows-gnu
       CHANNEL: stable
@@ -19,6 +16,11 @@ environment:
       CHANNEL: stable
     - TARGET: x86_64-pc-windows-msvc
       CHANNEL: stable
+    # For the integration test
+    # The test passes, but the build still fails for an unknown reason.
+    # If this is the last entry, we still get the binaries on releases until the this cause is fixed
+    - TARGET: x86_64-pc-windows-msvc
+      CHANNEL: nightly
 
 matrix:
   fast_finish: true

get_fourtytwo/Cargo.toml

@@ -1,7 +1,7 @@
 [package]
 authors = ["konstin <[email protected]>"]
 name = "get-fourtytwo"
-version = "1.7.0"
+version = "2.0.0"
 description = "This implements a dummy function (get_fortytwo.DummyClass.get_42()) in rust"
 readme = "Readme.md"