-
Notifications
You must be signed in to change notification settings - Fork 192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ts add test action #546
Ts add test action #546
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine, although I'm a bit confused about python versions. The yml suggests python 3.7, 3.8 and 3.9. Does that mean it will test these versions? I remember you saying it didn't work on 3.10, but have we dropped support for 3.6?
No, was just doing my usual copy/paste/edit/debug and hadn't considered the minimum python version we'd like to test. How low to go?.. |
I don't think many people are using 3.5 anymore, but 3.6 is still quite common I think. |
Removes 3.10 which is incompatible with nose (nose-devs/nose#1099 & #546)
Adds github actions to perform testing.
Still relying on the same bespoke test script we repurposed from cgat which utilises
nose
. Note thatnose
is no longer supported and cannot be used to test python 3.10 (nose-devs/nose#1099). I tried a few of the suggestions in that issue to resolve the issue but nothing worked straight out of the box.For now, I've dropped testing for
python 3.10
in favour of getting the CI testing back up and running. In the long run, it seems like we should be switching topytest
.