Conversation
|
@rokuingh the docs on this branch state that this is the test procedure: Is that still correct, or does this need to be updated? |
|
@rokuingh the ESMPy doc builds on CircleCI are failing like this: See here. How should the doc build procedure be changed? Note that if you want to test the ESMPy doc build container locally, you can use these instructions: |
|
This is still the correct test procedure (using nose) up through Python 3.9. For Python 3.10 we need to migrate to nose2 or something else like pytest, which I haven't finished yet. The installation at Python 3.10 is not yet finished either. |
|
I just had successful pip install and nose2 tests on Python 3.9.5. Did you not expect the nose2 tests to work on Python 3.9? In general, I think we should try to move away from two different install/test procedures based on Python version because it adds a lot of complexity to manage. Given that, what minimum version of Python do you recommend and will that use pip install and nose2? |
|
Yes pip and nose2 should work for 3.9, and probably all the way back through the 3 series. The issue we have with nose2 is that it doesn't have the same features for separating and running tests in groups like examples, slow, data, parallel etc. |
|
@rokuingh there must be some workaround to this issue, such as defining the tests in different directories or specifying specific tests when we run nose2, etc. Can you propose a workaround? |
|
@rokuingh your latest commit that added setup.py back causes install issues on Cheyenne: |
…for removal do not exist
…et and clean up dryruns
No description provided.