Closed chjacob-tubs closed 5 years ago
Thanks @robertodr I changed the error messages, will look at the tests tomorrow.
OK, the python tests are a bigger task (see #43), but I promised earlier to look at this. Hope I will find some time for this tomorrow.
In principle yes, but something similar to this line will suffice for the moment:
env PYTHONPATH=$HOME/Software/trash_xcfun/lib64/python:$PYTHONPATH python test/test.py
I've tried it locally and it works. IMHO a) extending test/test.py
to call your newly added interface functions, and b) adding this line to .travis.yml
(disregard .appveyor.yml
for the moment) it's enough to complete this PR and keeping it self-contained.
We can add to the wish list that Python tests should use pytest
(of which I was not aware one year ago when #43 was opened).
Merging #93 into master will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## master #93 +/- ##
=======================================
Coverage 42.07% 42.07%
=======================================
Files 77 77
Lines 1785 1785
=======================================
Hits 751 751
Misses 1034 1034
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact)
,ø = not affected
,? = missing data
Powered by Codecov. Last update a486a3f...e2368fd. Read the comment docs.
@robertodr I added tests of the Python interface and use Pytest for the tests now. The automatic tests still fail because pytest is not available in the test environment. How can I fix that?
That's awesome, thanks! As for your question, you need to:
pytest = "*"
to the the development packages in the Pipfile
and in requirements.txt
so that the two are kept in sync..travis.yml
to: pipenv $PYTHON install --dev
so that Python development packages are installed.Unrelated question: you mentioned some time ago that you were still developing under Python 2.7 Is that still the case? Or can we drop Python 2.7 support?
Thanks! I will merge this once the automatic tests pass.
On the Python 2.7 question: This is all part of a larger cleanup effort and I hope then we will be able to migrate all our code to Python 3. We are not completely there yet but getting closer...
Thanks a lot for this!
I extended the Python interface a but to allow the calculation of the energy density only (without calculating the potential). We are going to use this functionality in PyADF.
How Has This Been Tested?
A test of the interface is included in PyADF (as for the rest of the interface)
Types of changes
Questions
Status