remove pypandoc, use .rst formatted README until python packaging supports markdown

Author: skvark

README.md

@@ -0,0 +1,151 @@
++-------------+------------------+
+| Platform    | Status           |
++=============+==================+
+| Windows     | |buildstatus|    |
++-------------+------------------+
+| Manylinux   | |Build Status|   |
++-------------+------------------+
+
+OpenCV on wheels
+================
+
+Unofficial OpenCV packages for Python.
+
+Work in progress!
+
+The aim of this repository is to provide means to package each new
+`OpenCV release <https://github.com/Itseez/opencv/releases>`__ for the
+most used Python versions and platforms.
+
+At the same time it allows anyone to build a custom version of OpenCV
+for any Python version: just fork this repo and modify the build files
+and scripts to fit your needs.
+
+Why?
+----
+
+1. Installation of OpenCV for Python is pretty hideous:
+
+   1. Download OpenCV
+   2. Find cv2.pyd from the package
+
+      -  If it exists, copy it to the root of Python site-packages
+      -  If it does not exist for some reason for your setup, you have
+         to setup the build environment and compile it manually
+
+   3. Try to import cv2 and hope it works
+
+2. Everyone should be able to install OpenCV (or any package for that
+   matter) with pip with a single command without building anything
+3. Python `wheels <http://pythonwheels.com/>`__ are nice, we should use
+   them more
+
+Documentation
+-------------
+
+The project is structured like a normal Python package with a standard
+``setup.py`` file. The build process is as follows (see
+``appveyor.yml``):
+
+1. Checkout repository and submodules
+
+   -  OpenCV is included as submodule and the version is updated
+      manually when a new OpenCV release has been made
+
+2. Find OpenCV version from the sources
+3. Upgrade pip and install numpy for each Python version
+4. Build OpenCV
+
+   -  tests are disabled, otherwise build time increases too much
+
+5. Copy each ``.pyd/.so`` file to cv2 folder of this project and
+   generate wheel
+6. Install the generated wheels for each Python version
+7. Test that the Python versions can import them
+8. TO DO: upload the wheels to PyPi
+
+Currently the ``find_version.py`` file parses OpenCV version information
+from the OpenCV sources. OpenCV depends on numpy, so ``setup.py`` checks
+the numpy version also with the help of pip.
+
+As described earlier, for example the ``.pyd`` file on Windows is
+normally copied to site-packages. To avoid polluting the root folder the
+``__init__.py`` file in cv2 folder handles the import logic correctly by
+importing the actual ``.pyd`` module and replacing the imported cv2
+package in ``sys.modudes`` with the cv2 module to retain backward
+compatibility.
+
+Licensing
+---------
+
+Opencv-python package (scripts in this repository) is available under
+MIT license. The OpenCV itself is available under `3-clause BSD
+License <https://github.com/opencv/opencv/blob/master/LICENSE>`__
+(`LICENSE-3RD-PARTY.txt <https://github.com/skvark/opencv-python/blob/master/LICENSE-3RD-PARTY.txt>`__).
+
+Versioning
+----------
+
+Currently the ``find_version.py`` script searches for the version
+information from OpenCV sources and appends also a revision number
+specific to this repository to the version string.
+
+Releases
+~~~~~~~~
+
+A release is made and uploaded to PyPI when a new tag is pushed to
+master branch. These tags differentiate packages (this repo might have
+modifications but OpenCV version stays same) and should be incremented
+sequentially. In practice, release version numbers look like this:
+
+``cv_major.cv_minor.cv_revision.package_revision`` e.g. ``3.1.0.0``
+
+Development builds
+~~~~~~~~~~~~~~~~~~
+
+Every commit to the master branch of this repo will be built. Possible
+build artifacts use local version identifiers:
+
+``cv_major.cv_minor.cv_revision+git_hash_of_this_repo`` e.g.
+``3.1.0+14a8d39``
+
+These artifacts can't be and will not be uploaded to PyPI.
+
+Manylinux wheels
+----------------
+
+Linux wheels are built using
+`manylinux <https://github.com/pypa/python-manylinux-demo>`__. These
+wheels should work out of the box for most of the distros out there
+since they are built against an old version of glibc.
+
+Supported Python versions
+-------------------------
+
+Windows:
+~~~~~~~~
+
+There's a build time limitation (AppVeyor open source builds may take
+max. 1 hour) which restricts the supported Python versions to two. As
+Python's 2.x releases are slowly approaching legacy state, 2.7.x
+releases will be the only supported Python 2 versions on Windows. On
+Python 3 side, builds will be run only for the latest release.
+
+However, if you wan't to get some other versions, just fork this repo
+and change the dependencies.
+
+Linux
+~~~~~
+
+Manylinux wheels are built for all the Python versions which are
+supported by the manylinux containers.
+
+OS X
+~~~~
+
+TODO
+
+.. |buildstatus| image:: https://ci.appveyor.com/api/projects/status/5kjqpmvll5dwj5jd?svg=true
+   :target: https://ci.appveyor.com/project/skvark/opencv-python
+.. |Build Status| image:: https://travis-ci.org/skvark/opencv-python.svg?branch=master
+   :target: https://travis-ci.org/skvark/opencv-python

README.rst

@@ -1,4 +1,3 @@
 numpy==1.11.1
 wheel
 twine
-pypandoc

requirements.txt

@@ -4,20 +4,12 @@
 import os
 import sys
 import pypandoc
+import io
 
 long_description = ""
 
-print("Trying to download pandoc...")
-pypandoc.download_pandoc()
-
-try:
-    long_description = pypandoc.convert('README.md', 'rst')
-except OSError as e:
-    print("Pandoc not found.")
-    import io
-    # pandoc is not installed, fallback to using raw contents
-    with io.open('README.md', encoding="utf-8") as f:
-        long_description = f.read()
+with io.open('README.rst', encoding="utf-8") as f:
+    long_description = f.read()
 
 # cv_version.py should be generated by running find_version.py
 from cv_version import opencv_version