Permalink
Browse files

Add Pipfile.lock to .gitignore

  • Loading branch information...
prkumar committed Jun 20, 2018
1 parent 5f4ecc6 commit a2b070a5366c758a7d347f488b48e0aa2760a3e2
Showing with 13 additions and 13 deletions.
  1. +13 −0 .gitignore
  2. +0 −13 CONTRIBUTING.rst
View
@@ -103,3 +103,16 @@ ENV/
# pytest
.pytest_cache
# Pipfile & Pipfile.lock
#
# When developing libraries, it is generally recommended to exclude
# Pipfile and Pipfile.lock from version control [1]. Notably, including
# Pipfile in the repo is fine when it is used to specify development
# dependencies (e.g., tox), as long as the file does not repeat abstract
# dependencies that are already defined within setup.py [2].
#
# [1]: https://github.com/pypa/pipenv/issues/1911#issuecomment-379422008
# [2]: https://docs.pipenv.org/advanced/#pipfile-vs-setup-py
#
Pipfile.lock
View
@@ -54,19 +54,6 @@ Before submitting a pull request, run all tests with tox_:
.. _tox: https://tox.readthedocs.io/en/latest/
Recommended Python Version for Development
------------------------------------------
We strongly encourage using Python 3.6 for development.
Our ``Pipfile.lock`` was created using ``pipenv`` on Python 3.6.
Contributors using Python 2.7 and 3.3 may experience issues during
installation, since some development dependencies require Python
3.4+. However, as a workaround for development on an earlier version
of Python, you can try using the ``--skip-lock`` flag with
``pipenv install``.
Making Changes to the Source
============================
To find a feature or bug to work on, checkout the open GitHub issues with the

0 comments on commit a2b070a

Please sign in to comment.