Repository navigation
Conversation
35f0105 to
8118326
Compare
|
These failures a sort of mysterious to me, @bsipocz. The latest build has a new round of failures related to the escape sequence |
|
Yes, those needed to be fixed in astropy and astroquery, too. Too bad I don't yet have py3.6 locally, so can only test it on travis. |
|
@bsipocz - I just took another look at this PR in light of #664. It looks like 3.6 compatibility requires including an |
|
@aphearin - Yes, there was a change with escape sequences, and py3.6 got a bit stricter, so we need to have raw strings in many cases (e.g with equations). Unfortunatelly don't know a tool to do this automatically (as one may need to change the docstrings themselves, too). |
|
Well, that's a bit of a bummer. FYI, my current release cycle is to try and get |
|
@aphearin - OK, if you are happy with that let's keep this open. Don't worry, I sometimes need menial tasks to fall back on so I'll update this from time to time. |
|
Same here. In order for me to help chip away at this, is the easiest thing for me to just submit PRs against this branch in your fork? |
|
No need for PRs, you can push commits to this branch directly (as a maintainer). |
8118326 to
994f60a
Compare
994f60a to
5da1d1f
Compare
5da1d1f to
9935a47
Compare
We've recently found the probably reason of the halting numpy prerelease builds and made a fix in ci-helpers. So I'm removing it from the allowed failures with the note that since there is no prerelease available at the moment it will pass anyway. I'm almost certain that it should work (the fix worked for e.g. photutils).
But while I was already editing the file, also added the new py 3.6 version to the matrix as well as numpy 1.11.