MNT: Remove numpy !=1.15.3 pin when 1.15.4 is out
See original GitHub issueThis is a follow up of https://github.com/astropy/astropy/pull/8043#discussion_r230244725
When Numpy 1.15.4 is out and available in default conda
channels for the main OSes that we support, we have to remove the pin in:
setup.py
pip-requirements
- Installation doc (
install.rst
)
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
ImportError failure with NumPy 1.15.4 #9 - GitHub
With NumPy 1.15.4, I see an ImportError when trying to execute the tests. Here's a transcript from a session using Python 3.8.1 (from ......
Read more >Pandas incompatible with numpy - Stack Overflow
In conda list, my numpy version is 1.19.1. I checked the above directory to find that it has only numpy 1.15.3 inside and...
Read more >NumPy 1.15.4 Release Notes
This is a bugfix release for bugs and regressions reported following the 1.15.3 release. The Python versions supported by this release are 2.7,...
Read more >Changelog — ligo.skymap v1.0.4.dev3+gf630e5f
Un-pin Numpy version now that Numpy 1.15.4 is out. The bayestar-localize-lvalert and ligo-skymap-from-samples tools can now natively output multi-resolution ...
Read more >Bug listing with status UNCONFIRMED as at 2022/12/21 18 ...
... rootfs" mount entry" status:UNCONFIRMED resolution: severity:major ... Bug:672464 - "dev-python/numpy-1.15.4 USE=mkl - fails at either build time or run ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
1.15.4 has been released: https://mail.python.org/pipermail/numpy-discussion/2018-November/078913.html
Re: why – The argument was that we never pin bugfix like this, so no reason to start now. (Link to original comment for this request in my original post.)