pychapel 0.1.18: Fix lib path for Chapel > 1.16.0; pip installer; docs.

[awallace-cray]

Makes the pip install (w manual Chapel build) work on Linux again, without addressing everything else to be desired. This should at least get pychapel back the functionality it had, before

• Chapel changed its internal runtime lib path
• The last two pypi releases, which were incomplete ("pych.json not found")

[awallace-cray]

~A change I am considering but have not decided to use yet.~

[awallace-cray]

Updates to docs/source/introduction.rst installation instructions are in progress.

[awallace-cray]

Tested. Ready for review.

Reviewers: use updated installation instructions

Instead of pip install --user "numpy>=1.14" "future>=0.15.2" pyChapel, use

pip install --index-url https://test.pypi.org/simple/ --user pyChapel
pip install --user "numpy>=1.14" "future>=0.15.2"

[awallace-cray]

I moved the copyright blocks to PR #91, just to keep the noise out of this.

[awallace-cray]

Updated the test-pypi release (now 0.1.18.3) pip install --index-url https://test.pypi.org/simple/ --user pyChapel

[lydia-duncan]

pip install --index-url https://test.pypi.org/simple/ --user pyChapel pip install --user "numpy>=1.14" "future>=0.15.2"

This command does not work for me in my environment, I get:

Could not fetch URL https://test.pypi.org/simple/pychapel/: There was a problem confirming the ssl certificate: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:661) - skipping
  Could not find a version that satisfies the requirement pyChapel (from versions: )
No matching distribution found for pyChapel

My .pip/pip.conf file has the usual permission thing we use in it

[awallace-cray]

2018-02-09 : I repro'd the problem Lydia reported on chapcs11. Removing the old ~/.pip/pip.conf (left over from 2014, I think) fixed that problem. However, when I attempted to finish installing pychapel on chapcs11 w the proposed pip package, I ran into other problems which stopped me. The pip install appeared to work - but when I ran pych -k, it blew up (not shown here right now). I was not able to make that pip install / pych work on chapcs11, so I set it aside to work on other priorities.

[awallace-cray]

2018-02-15 : Just succeeded installing pychapel w the proposed pip install package using the proposed instructions. This time the host was a centos-7 VM.

This result, plus experience from trying to make this work on chapcs11, suggests that the problem

• May be unique to chapcs11 (or something unusual about chapcs11- e.g., unlike on either VM used so far, pip is not installed on the system on chapcs11, so Lydia and I both user-installed it.)
• Is likely to be found in the distutils/setuptools Python/pip packaging stuff, rather than something wrong with pychapel itself. Admittedly, the problem on chapcs11 does occur because of some unusual-looking code in pychapel's setup.py (See class post_install(install_data))

[awallace-cray]

2018-02-15 : Just successfully tested the proposed pip install package on another VM, this one a SLES-12 running on AWS. Also, this one did not have pip installed in the system, so I installed that in $HOME/.local with the command easy_install --prefix=$HOME/.local pip, added $HOME/.local/bin to the PATH, and then finished the test install procedure per the instructions (except w pip install --index-url https://test.pypi.org/simple/ --user pyChapel as noted above).

For information only, I tried the unit tests. As before, the tests in module/testing pass using the pip-installed pychapel (you must first pip install --user all the requirements.txt's), but the tests in docs/source/examples do not. That is due to gaps in the current setup.py which I intentionally did not address this time.

[awallace-cray]

This last commit fixes the fatal error that @lydia-duncan and I hit when we tried this on chapcs11.

Reviewers: use updated installation instructions

And instead of pip install --user --upgrade --no-binary pyChapel pyChapel, please use

pip install -i https://test.pypi.org/simple/ --user --upgrade --no-binary pyChapel pyChapel

(pip install --user "numpy>=1.14" "future>=0.15.2" is a separate command to run at the same time)

[awallace-cray]

Updated installation instructions with "Mention easy_install".

[awallace-cray]

Rebase only: That last commit cd678ee just squashes the previous dba8d22 into 167f78b