Initial version

Author: aragilar

.gitattributes

@@ -0,0 +1 @@
+spaceplot/_version.py export-subst

.gitignore

@@ -0,0 +1,8 @@
+.cache
+.tox
+spaceplot.egg-info
+_build
+.coverage
+dist
+build
+.pytest_cache

.travis.yml

@@ -0,0 +1,57 @@
+language: python
+branches:
+  only:
+    # This is where pull requests from "bors r+" are built.
+    - staging
+    # This is where pull requests from "bors try" are built.
+    - trying
+    # Uncomment this to enable building pull requests.
+    - master
+
+sudo: false
+
+cache:
+  directories:
+    - $HOME/.cache/pip
+
+matrix:
+  include:
+    - python: 3.4
+      env:
+      - TOXENV=py34
+    - python: 3.5
+      env:
+      - TOXENV=py35
+    - python: 3.6
+      env:
+      - TOXENV=py36
+    - python: 3.5
+      env:
+      - TOXENV=flake8
+    - python: 3.5
+      env:
+      - TOXENV=pylint
+    - python: 3.5
+      env:
+      - TOXENV=docs
+    - python: 3.5
+      env:
+      - TOXENV=doctest
+    - python: 3.5
+      env:
+      - TOXENV=check-manifest
+    - python: 3.5
+      env:
+      - TOXENV=checkreadme
+
+before_install:
+  - pip install codecov # for coverage
+
+install:
+  - pip install tox
+
+script:
+  - tox
+
+after_success:
+  - codecov

CONTRIBUTING.md

@@ -0,0 +1,24 @@
+Copyright (c) 2018, James Tocknell
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+    * Redistributions of source code must retain the above copyright
+      notice, this list of conditions and the following disclaimer.
+    * Redistributions in binary form must reproduce the above copyright
+      notice, this list of conditions and the following disclaimer in the
+      documentation and/or other materials provided with the distribution.
+    * Neither the name of the <organization> nor the
+      names of its contributors may be used to endorse or promote products
+      derived from this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL <COPYRIGHT HOLDER> BE LIABLE FOR ANY
+DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

LICENSE.txt

@@ -0,0 +1,17 @@
+include versioneer.py spaceplot/_version.py
+include DESCRIPTION.rst
+include README.md
+include LICENSE.txt
+include code_of_conduct.md
+include CONTRIBUTING.md
+recursive-include docs *
+recursive-exclude docs/_build *
+include doc-requirements.txt
+include test-requirements.txt
+recursive-include tests *.py
+recursive-include paper *
+include pylintrc
+include tox.ini
+include pypi-intro.rst
+exclude appveyor.yml
+exclude bors.toml

MANIFEST.in

@@ -0,0 +1,77 @@
+# from https://packaging.python.org/en/latest/appveyor/
+branches:
+  only:
+    # This is where pull requests from "bors r+" are built.
+    - staging
+    # This is where pull requests from "bors try" are built.
+    - trying
+    # Uncomment this to enable building pull requests.
+    - master
+environment:
+  matrix:
+
+    # For Python versions available on Appveyor, see
+    # http://www.appveyor.com/docs/installed-software#python
+    # The list here is complete (excluding Python 2.6, which
+    # isn't covered by this document) at the time of writing.
+
+    - PYTHON: "C:\\Python34"
+      TOXENV: "py34"
+      TOXPYTHON: "%PYTHON%\\python.exe"
+
+    - PYTHON: "C:\\Python35"
+      TOXENV: "py35"
+      TOXPYTHON: "%PYTHON%\\python.exe"
+
+    - PYTHON: "C:\\Python36"
+      TOXENV: "py36"
+      TOXPYTHON: "%PYTHON%\\python.exe"
+
+    - PYTHON: "C:\\Python34-x64"
+      TOXENV: "py34"
+      TOXPYTHON: "%PYTHON%\\python.exe"
+
+    - PYTHON: "C:\\Python35-x64"
+      TOXENV: "py35"
+      TOXPYTHON: "%PYTHON%\\python.exe"
+
+    - PYTHON: "C:\\Python36-x64"
+      TOXENV: "py36"
+      TOXPYTHON: "%PYTHON%\\python.exe"
+
+install:
+  # We need wheel installed to build wheels
+  - "%PYTHON%\\python.exe -m pip install --upgrade wheel pip setuptools"
+  - "py -3.5 -m pip install --upgrade wheel pip setuptools"
+  - "py -3.5 -m pip install tox codecov"
+
+build: off
+
+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 evrsion you want to use on PATH.
+  - "py -3.5 -m tox"
+
+# This is commented out as there's no easy way to deal with numpy dropping
+# older python versions without a recent pip/setuptools.
+#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
+#  - "ci\\appveyor\\build.cmd %PYTHON%\\python.exe setup.py bdist_wheel"
+#
+#artifacts:
+#  # bdist_wheel puts your built wheel in the dist directory
+#  - path: dist\*
+
+cache:
+  - "%LOCALAPPDATA%\\pip\\Cache"
+
+on_success:
+  - "py -3.5 -m codecov"

README.md

@@ -0,0 +1,4 @@
+status = [
+  "continuous-integration/travis-ci/push",
+  "continuous-integration/appveyor/branch"
+]

appveyor.yml

@@ -0,0 +1,74 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [INSERT EMAIL ADDRESS]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [https://contributor-covenant.org/version/1/4][version]
+
+[homepage]: https://contributor-covenant.org
+[version]: https://contributor-covenant.org/version/1/4/