These are chat archives for astropy/ci-helpers

16th
Feb 2017
Brigitta Sipocz
@bsipocz
Feb 16 2017 13:38
@astrofrog - are you around?
The missing osx astropy+np1.12 bites most packages really badly, but on the other hand I feel that updating numpy stable to be 1.12 a month after the release is expected.
Should we do a workaround somehow?
Thomas Robitaille
@astrofrog
Feb 16 2017 15:34
I'm around sorry
thinking...
Brigitta Sipocz
@bsipocz
Feb 16 2017 15:36
we already have a few workarounds, so I'm ok to add another to make both numpy=stable and astropy=stable happy. This won't solve the problem with other missing dependencies though, but I think it should be delegated back to the packages themselves to deal with (e.g they are pinning pyqt to a version here: https://github.com/astropy/ci-helpers/issues/166#issuecomment-280234536, so then that should be their problem that it's not available on new versions)
Thomas Robitaille
@astrofrog
Feb 16 2017 15:36
What about for now if both astropy and numpy are set to stable we set the numpy version to 1.11
alternatively we could change back to 1.11 and just say we'll update to 1.12 once conda packages with 1.12 are aroujnd
I mean it's not ideal, but it's pragmatic
easiest might be the first option though, just setting it to 1.11 if both astropy and numpy are set to stable
Brigitta Sipocz
@bsipocz
Feb 16 2017 15:38
but 1.12 is out for a while, and many package is happily passing with the current setup
Thomas Robitaille
@astrofrog
Feb 16 2017 15:38
Ok, so let's deal with just the double stable case in a workaround?
Brigitta Sipocz
@bsipocz
Feb 16 2017 15:39
OK. My alternative would be to install astropy from pip in that case?
actually a bit surprising as it's not happening, https://github.com/astropy/ci-helpers/blob/master/travis/setup_dependencies_common.sh#L298 did this trick before...
Thomas Robitaille
@astrofrog
Feb 16 2017 15:58
Yes that might be a better solution
ah but the issue is that in this case astropy never gets installed to start with