Fix ValueError when addplot column is all NaN

.github/ISSUE_TEMPLATE/ask-a-question.md

@@ -0,0 +1,10 @@
+---
+name: Ask a Question
+about: Question about usage, project priorities, or anything else related to mplfinance.
+title: ''
+labels: 'question'
+assignees: ''
+
+---
+
+Ask anything you want about mplfinance usage, project philosophy and/or priorities, or anything else related to mplfinance.

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,38 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: 'Bug Report:'
+labels: 'bug'
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+ - Device: [e.g. iPhone6]
+ - OS: [e.g. iOS8.1]
+ - Browser [e.g. stock browser, safari]
+ - Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: 'Feature Request:'
+labels: 'enhancement'
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/feedback.md

@@ -0,0 +1,11 @@
+---
+name: Feedback
+about: What do you think of mplfinance?  Pros? Cons?  Thoughts?
+title: 'Comment:'
+labels: 'feedback'
+assignees: ''
+
+---
+
+What do you think of mplfinance?  Pros? Cons?  Thoughts?
+Thank you for taking the time to provide feedback.  Much appreciated!

.github/workflows/mplfinance_checks.yml

@@ -0,0 +1,76 @@
+name: mplfinance Checks
+on: [ workflow_dispatch, pull_request ]
+jobs:
+  Regression_Tests:
+    runs-on: ubuntu-20.04
+    strategy:
+      matrix:
+        python-version: ['3.8', '3.9', '3.10' ]
+    steps:
+      - name: Preliminary Information
+        run: |
+          echo "The job was automatically triggered by a ${{ github.event_name }} event."
+          echo "This job is now running on a ${{ runner.os }} server hosted by GitHub!"
+          echo "The name of your branch is ${{ github.ref }} and your repository is ${{ github.repository }}."
+          echo "  "
+          echo "github.ref = ${{ github.ref }}"
+          echo "github.sha = ${{ github.sha }}"
+          echo "github.event.pull_request.head.ref = ${{ github.event.pull_request.head.ref }}"
+          echo "github.event.pull_request.head.sha = ${{ github.event.pull_request.head.sha }}"
+          echo "github.event.pull_request.base.ref = ${{ github.event.pull_request.base.ref }}"
+          echo "github.event.pull_request.base.sha = ${{ github.event.pull_request.base.sha }}"
+          echo "  "
+
+      - name: Check out repository code
+        uses: actions/checkout@v2
+
+      - run: echo "The ${{ github.repository }} repository has been cloned to the runner."
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v4
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install pytest
+          if [ -f requirements.txt ]; then pip install -r requirements.txt; fi
+
+      - name: Install My Package
+        run: pip install .
+
+      - name: Run Pytest
+        run: python -m pytest
+
+      - run: echo "This job's status is ${{ job.status }}."
+
+  Pull_Request_Updates_Version:
+    runs-on: ubuntu-20.04
+    if: github.event_name == 'pull_request'
+    steps:
+      - name: Check out repository code
+        uses: actions/checkout@v2
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v2
+        with:
+          python-version: '3.10'
+
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install packaging
+
+      - name: Fetch base and head on PR
+        if: ${{ github.event.pull_request.base.sha }}
+        run: |
+          git fetch origin master ${{ github.event.pull_request.base.sha }}
+          git fetch origin master ${{ github.event.pull_request.head.sha }}
+
+      - name: Check that Pull Request includes updating the Version
+        run: |
+          git show ${{ github.event.pull_request.base.sha }}:src/mplfinance/_version.py > scripts/tv0.py
+          git show ${{ github.sha }}:src/mplfinance/_version.py > scripts/tv1.py
+          python scripts/version_update_check.py tv0 tv1
+

.github/workflows/pubPyPI.yml

@@ -0,0 +1,43 @@
+name: Upload Mplfinance to PyPI
+
+on:
+  workflow_dispatch:
+    inputs:
+      tag:
+        description: 'version tag to deploy'
+        required: true
+        type: string
+
+jobs:
+  build_and_deploy:
+    runs-on: ubuntu-latest
+    steps:
+    - name: Checkout Repository
+      uses: actions/checkout@v3
+      with:
+        ref:  ${{ github.event.inputs.tag }}
+
+    - name: Display Coded Version 
+      #run: git show ${{ github.sha }}:src/mplfinance/_version.py
+      run: egrep 'version_info .*=' src/mplfinance/_version.py
+
+    - name: Set up Python
+      uses: actions/setup-python@v4
+      with:
+        python-version: '3.x'
+
+    - name: Install dependencies
+      run: |
+        python -m pip install --upgrade pip
+        pip install setuptools wheel twine
+
+    - name: Build 
+      run: |
+        python setup.py sdist bdist_wheel
+        ls -l dist/*
+
+    - name: Publish distribution to PyPI
+      env:
+        TWINE_USERNAME: __token__
+        TWINE_PASSWORD: ${{ secrets.PYPI_API_TOKEN }}
+      run: twine upload dist/*

.github/workflows/pubTestPyPI.yml

@@ -0,0 +1,43 @@
+name: Upload Mplfinance to TestPyPI
+
+on:
+  workflow_dispatch:
+    inputs:
+      tag:
+        description: 'version tag to deploy'
+        required: true
+        type: string
+
+jobs:
+  build_and_deploy:
+    runs-on: ubuntu-latest
+    steps:
+    - name: Checkout Repository
+      uses: actions/checkout@v3
+      with:
+        ref:  ${{ github.event.inputs.tag }}
+
+    - name: Display Coded Version 
+      #run: git show ${{ github.sha }}:src/mplfinance/_version.py
+      run: egrep 'version_info .*=' src/mplfinance/_version.py
+
+    - name: Set up Python
+      uses: actions/setup-python@v4
+      with:
+        python-version: '3.x'
+
+    - name: Install dependencies
+      run: |
+        python -m pip install --upgrade pip
+        pip install setuptools wheel twine
+
+    - name: Build 
+      run: |
+        python setup.py sdist bdist_wheel
+        ls -l dist/*
+
+    - name: Publish distribution to Test PyPI
+      env:
+        TWINE_USERNAME: __token__
+        TWINE_PASSWORD: ${{ secrets.TEST_PYPI_API_TOKEN }}
+      run: twine upload --repository-url https://test.pypi.org/legacy/ dist/*

.gitignore

@@ -6,3 +6,5 @@ __pycache__
 *.egg-info
 .tox/
 .cache/
+*.code-workspace
+*.ipynb_checkpoints/

CODE_OF_CONDUCT.md

@@ -0,0 +1,4 @@
+
+#### All typical collaboration codes of conduct apply:
+
+### Treat people fairly, with respect, and overall [be a mensch](https://www.google.com/search?q=mensch).

CONTRIBUTING.md

@@ -0,0 +1,37 @@
+## Contributing Basics
+
+- Contributing can be as simple as **asking questions**, participating in discussions, suggesting enhancements, etc.  **All of these are valuable!**  There are many ways to contribute.  We also very much appreciate when you share the creative things you've done *using* mplfinance (both code and plot images).  And, of course, writing code for mplfinance is also a great way to contribute.    Thank you.
+
+- All of the usual/typical open source contribution guidelines apply (see for example, **[Matplotlib Contributing](https://matplotlib.org/stable/devel/contributing.html)** and **[Open Source Guide to Contributing](https://opensource.guide/how-to-contribute/)**).  Therefore, here, on this page, we will mention just a few items that we may be particular about in **mplfinance**.
+
+---
+
+## Fork Clone Workflow
+- The standard workflow for contributing on GitHub is called **Fork/Clone**.  For those who may not be familiar, here is a brief summary and some reference links.  
+  - *We assume you are familiar with **git** basics: `git clone`, `git commit`, etc*.
+- Note: a "Fork" is just a `git clone` *that is created on, and that lives on, GitHub.com*.  You create a fork using the **Fork** button on GitHub: This allows GitHub to track the relationship between the original github repository, and your Fork.  (In that sense a "fork" is slightly more than just a plain "clone", but only as much as GitHub.com adds some tracking and other minor features to make integration easier).
+- The basic workflow is:
+  1. Create a **Fork** of the mplfinance repository.  (See references below for details.)  The fork will exist under *your* github account.  
+  2. **Clone** *your* Fork to your local machine (`git clone`).
+  3. Work on your cloned copy of the repository, `git commit` the changes, and then **`git push`** them *to your GitHub fork*.
+  4. When you are satisfied with the code in your fork then, **on the GitHub page for your fork, *open a Pull Request (PR)***.  A Pull Request effectively asks for the changes in your fork be pulled into the main mplfinance repository.  The PR provides, on github, a place to see the changes, and to post comments and discussion about them.
+  5. After code review, if you are asked by a maintainer to make additional changes, you do *not* have to re-enter another Pull Request (as long as the original PR is still open).  Rather, make the changes in your local clone, and simply `git push` them to your fork again.  The changes will automatically flow into the open Pull Request.
+  6. When done, the maintainer of the repository will merge the changes from your fork into the mplfinance repository.  The PR will automatically be closed.  (Your fork, however, will continue to exist, and can be used again for additional Pull Requests in the future; See GitHub documentation for how to keep your Fork up to date).
+
+- Some References:
+- GitHub documentation:
+  - **https://docs.github.com/en/get-started/quickstart/contributing-to-projects**
+- and some user gists:
+  - https://gist.github.com/Chaser324/ce0505fbed06b947d962
+  - https://gist.github.com/rjdmoore/ed014fba0ee2c7e75060ccd01b726cb8
+
+---
+
+## Coding Standards
+- I am not super strict about adhearing to every aspect of PEP 8, *nor am I lenient*.  I tend to walk the middle of the road: If something is a good and common, then it should be adheared to.  
+- Here are a few items that I (perhaps uniquely) tend to care about in particular:
+  - If you write code, please don't use tabs; rather use spaces.
+  - If you work on a pre-existing code file, please try to more-or-less emulate the style that already exists in that file.
+  - If you add a significant feature --that is, a feature for which explaining its usage takes more than just a few sentences-- please also create a "tutorial notebook" for that feature.  **[For examples of tutorial notebooks, please see the jupyter notebooks in the examples folder.](https://github.com/matplotlib/mplfinance/tree/master/examples)**
+  - If you add a significant feature, please also create a regression test file **[in the tests folder](https://github.com/matplotlib/mplfinance/tree/master/tests)**, similar to the other regression tests that are there.  *Often, the simplest way to do this is to take a few of the examples from the feature's "tutorial notebook"* (see previous point).
+

LICENSE

@@ -0,0 +1,49 @@
+License agreement for mplfinance
+=================================
+
+1. This LICENSE AGREEMENT is between the Matplotlib Development Team
+("MDT"), and the Individual or Organization ("Licensee") accessing and
+otherwise using matplotlib software in source or binary form and its
+associated documentation.
+
+2. Subject to the terms and conditions of this License Agreement, MDT
+hereby grants Licensee a nonexclusive, royalty-free, world-wide license
+to reproduce, analyze, test, perform and/or display publicly, prepare
+derivative works, distribute, and otherwise use matplotlib
+alone or in any derivative version, provided, however, that MDT's
+License Agreement and MDT's notice of copyright, i.e., "Copyright (c)
+2012- Matplotlib Development Team; All Rights Reserved" are retained in
+matplotlib  alone or in any derivative version prepared by
+Licensee.
+
+3. In the event Licensee prepares a derivative work that is based on or
+incorporates matplotlib or any part thereof, and wants to
+make the derivative work available to others as provided herein, then
+Licensee hereby agrees to include in any such work a brief summary of
+the changes made to matplotlib .
+
+4. MDT is making matplotlib available to Licensee on an "AS
+IS" basis.  MDT MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
+IMPLIED.  BY WAY OF EXAMPLE, BUT NOT LIMITATION, MDT MAKES NO AND
+DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
+FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF MATPLOTLIB
+WILL NOT INFRINGE ANY THIRD PARTY RIGHTS.
+
+5. MDT SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF MATPLOTLIB
+ FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR
+LOSS AS A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING
+MATPLOTLIB , OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF
+THE POSSIBILITY THEREOF.
+
+6. This License Agreement will automatically terminate upon a material
+breach of its terms and conditions.
+
+7. Nothing in this License Agreement shall be deemed to create any
+relationship of agency, partnership, or joint venture between MDT and
+Licensee.  This License Agreement does not grant permission to use MDT
+trademarks or trade name in a trademark sense to endorse or promote
+products or services of Licensee, or any third party.
+
+8. By copying, installing or otherwise using matplotlib ,
+Licensee agrees to be bound by the terms and conditions of this License
+Agreement.

MANIFEST.in

@@ -0,0 +1 @@
+include LICENSE