Remove leading and trailing spaces in README

README.md

@@ -37,7 +37,7 @@ Usage
 
     ```
     language: python
-    
+
     matrix:
       include:
         - sudo: required
@@ -65,12 +65,12 @@ Usage
       - path: "wheelhouse\\*.whl"
         name: Wheels
     ```
-    
+
   Appveyor will store the built wheels for you - you can access them from the project console. Alternatively, you may want to store them in the same place as the Travis CI build. See [Appveyor deployment docs](https://www.appveyor.com/docs/deployment/) for more info, or see [Delivering to PyPI](#delivering-to-pypi) below.
-    
+
 - Commit those files, enable building of your repo on Travis CI and Appveyor, and push.
 
-All being well, you should get wheels delivered to you in a few minutes. 
+All being well, you should get wheels delivered to you in a few minutes.
 
 > ⚠️ Got an error? Check the [checklist](#it-didnt-work) below.
 
@@ -108,7 +108,7 @@ usage: cibuildwheel [-h]
                     [--output-dir OUTPUT_DIR]
                     [--platform PLATFORM]
                     [project_dir]
-    
+
 Build wheels for all the platforms.
 
 positional arguments:
@@ -126,7 +126,7 @@ optional arguments:
                         you need to run in Windows, and it will build and test
                         for all versions of Python at C:\PythonXX[-x64].
   --output-dir OUTPUT_DIR
-                        Destination folder for the wheels. 
+                        Destination folder for the wheels.
 
 ```
 
@@ -156,13 +156,13 @@ Python tags look like `cp27` `cp34` `cp35` `cp36`
 
 Platform tags look like `macosx_10_6_intel` `manylinux1_x86_64` `manylinux1_i686` `win32` `win_amd64`
 
-You can also use shell-style globbing syntax (as per `fnmatch`) 
+You can also use shell-style globbing syntax (as per `fnmatch`)
 
 Examples:
-- Skip building on Python 2.7 on the Mac: `cp27-macosx_10_6_intel`  
-- Skip building on Python 2.7 on all platforms: `cp27-*`  
-- Skip Python 2.7 on Windows: `cp27-win*`  
-- Skip Python 2.7 on 32bit Windows: `cp27-win32`  
+- Skip building on Python 2.7 on the Mac: `cp27-macosx_10_6_intel`
+- Skip building on Python 2.7 on all platforms: `cp27-*`
+- Skip Python 2.7 on Windows: `cp27-win*`
+- Skip Python 2.7 on 32bit Windows: `cp27-win32`
 - Skip Python 3.4 and Python 3.5: `cp34-* cp35-*`
 - Skip Python 3.6 on Linux: `cp36-manylinux*`
 - Only build on Python 3.6: `cp27-* cp34-* cp35-*`
@@ -188,10 +188,10 @@ You must set this variable to pass variables to Linux builds (since they execute
 
 You can use `$PATH` syntax to insert other variables, or the `$(pwd)` syntax to insert the output of other shell commands.
 
-Example: `CFLAGS="-g -Wall" CXXFLAGS="-Wall"`  
-Example: `PATH=$PATH:/usr/local/bin`  
-Example: `BUILD_TIME="$(date)"`  
-Example: `PIP_EXTRA_INDEX_URL="https://pypi.myorg.com/simple"`  
+Example: `CFLAGS="-g -Wall" CXXFLAGS="-Wall"`
+Example: `PATH=$PATH:/usr/local/bin`
+Example: `BUILD_TIME="$(date)"`
+Example: `PIP_EXTRA_INDEX_URL="https://pypi.myorg.com/simple"`
 
 Platform-specific variants also available:
 `CIBW_ENVIRONMENT_MACOS` | `CIBW_ENVIRONMENT_WINDOWS` | `CIBW_ENVIRONMENT_LINUX`
@@ -209,11 +209,11 @@ If dependencies are required to build your wheel (for example if you include a h
 
 The active Python binary can be accessed using `{python}`, and pip with `{pip}`. These are useful when you need to write `python3` or `pip3` on a Python 3.x build. `{project}` can be used as a placeholder for the absolute path to the project's root.
 
-Example: `{pip} install .`  
-Example: `{pip} install pybind11`  
+Example: `{pip} install .`
+Example: `{pip} install pybind11`
 Example: `yum install -y libffi-dev && {pip} install .`
 
-Platform-specific variants also available:  
+Platform-specific variants also available:
  `CIBW_BEFORE_BUILD_MACOS` | `CIBW_BEFORE_BUILD_WINDOWS` | `CIBW_BEFORE_BUILD_LINUX`
 
 | Environment variables: `CIBW_MANYLINUX1_X86_64_IMAGE` and `CIBW_MANYLINUX1_I686_IMAGE`
@@ -225,7 +225,7 @@ An alternative docker image to be used for building [`manylinux1`](https://githu
 
 Beware to specify a valid docker image that can be used the same as the official, default docker images: all necessary Python and pip versions need to be present in `/opt/python/`, and the `auditwheel` tool needs to be present for `cibuildwheel` to work. Apart from that, the architecture and relevant shared system libraries need to be manylinux1-compatible in order to produce valid `manylinux1` wheels (see https://github.com/pypa/manylinux and [PEP 513](https://www.python.org/dev/peps/pep-0513/) for more details).
 
-Example: `dockcross/manylinux-x64`  
+Example: `dockcross/manylinux-x64`
 Example: `dockcross/manylinux-x86`
 
 | Environment variable: `CIBW_TEST_COMMAND`
@@ -244,7 +244,7 @@ Optional.
 
 Space-separated list of dependencies required for running the tests.
 
-Example: `pytest`  
+Example: `pytest`
 Example: `nose==1.3.7 moto==0.4.31`
 
 --
@@ -274,13 +274,13 @@ After you've built your wheels, you'll probably want to deliver them to PyPI.
 On your development machine, do the following...
 
 ```bash
-# Clear out your 'dist' folder. 
+# Clear out your 'dist' folder.
 rm -rf dist
 # Make a source distribution
 python setup.py sdist
 
 # 🏃🏻
-# Go and download your wheel files from wherever you put them. Put 
+# Go and download your wheel files from wherever you put them. Put
 # them all into the 'dist' folder.
 
 # Upload using 'twine' (you may need to 'pip install twine')
@@ -311,7 +311,7 @@ If your wheel didn't compile, check the list below for some debugging tips.
 Working examples
 ----------------
 
-Here are some repos that use cibuildwheel. 
+Here are some repos that use cibuildwheel.
 
 - [pyinstrument_cext](https://github.com/joerick/pyinstrument_cext)
 - [websockets](https://github.com/aaugustin/websockets)
@@ -377,7 +377,7 @@ Changelog
 
 13 April 2017
 
-- Added `CIBW_SKIP` option, letting users explicitly skip a build 
+- Added `CIBW_SKIP` option, letting users explicitly skip a build
 - Added `CIBW_BEFORE_BUILD` option, letting users run a shell command before the build starts
 
 ### 0.1.3