Repository navigation
Adding python 3.6 to CI builds - #815
Conversation
0a2010d to
83160f8
Compare
|
It seems that we have genuine incompatibilities with py3.6: |
|
Apparently py3.6 doesn't support |
|
Or... |
|
Maybe it's enough to add an |
|
OK, so there is one more error left. It seems to be an upstream pytest issue, and while we use the astropy bundled version there isn't a chance to avoid it. (Also it's not yet fixed in pytest itself as of pytest-dev/pytest#2160, so it would probably best to find a fix here for now). I'm not 100% sure, but it seems that using unittest triggers the error, as it's only the esasky module that uses it. |
dddef16 to
f6c2dd2
Compare
75d613b to
3cb2188
Compare
|
This now includes #864 to fix most of the deprecations. |
3cb2188 to
1a586c9
Compare
|
@keflavich - This can't be merged until the unittests are sorted out. However, since the unittest issue affects only the tests, we can make 0.3.5 py3.6 compatible if I factor out the docstring and other py3.6 related changes from here. Should we do that? |
|
Sure, if you have the time
|
1a586c9 to
753531d
Compare
753531d to
6e7a985
Compare
6e7a985 to
d05f5c6
Compare
|
Merging as finally this passed (except the coverage where something is really badly broken somewhere unrelated to this PR). |
Probably we need to wait a bit more until all the dependencies become available on python 3.6.
Edit: this is now based on #869