Code warnings during docs build
See original GitHub issueWhile building documentation, I get the warnings below, at least some of which suggest documentation is out of date. Generally, I don’t think any code we include should generate warnings, so it would be good to fix this. More generally, perhaps we should start failing on any warning from the docs build?
/usr/lib/python3/dist-packages/numpy/lib/function_base.py:3405: RuntimeWarning: All-NaN slice encountered
r = func(a, **kwargs)
WARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
WARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
/data/mhvk/packages/astropy/build/lib.linux-x86_64-3.7/astropy/timeseries/downsample.py:28: RuntimeWarning: Mean of empty slice
result.append(function(array[indices[i]:indices[i+1]]))
/data/mhvk/packages/astropy/build/lib.linux-x86_64-3.7/astropy/timeseries/downsample.py:29: RuntimeWarning: Mean of empty slice
result.append(function(array[indices[-1]:]))
WARNING: ErfaWarning: ERFA function "utctai" yielded 1 of "dubious year (Note 3)" [astropy._erfa.core]
/usr/lib/python3/dist-packages/matplotlib/figure.py:98: MatplotlibDeprecationWarning:
Adding an axes using the same arguments as a previous axes currently reuses the earlier instance. In a future version, a new instance will always be created and returned. Meanwhile, this warning can be suppressed, and the future behavior ensured, by passing a unique label to each axes instance.
"Adding an axes using the same arguments as a previous axes "
WARNING: AstropyDeprecationWarning: Importing LombScargle from astropy.stats has been deprecated and will no longer be supported in future. Please import this class from the astropy.timeseries module instead [astropy.stats.lombscargle]
WARNING: AstropyDeprecationWarning: Importing BoxLeastSquares from astropy.stats has been deprecated and will no longer be supported in future. Please import this class from the astropy.timeseries module instead [astropy.stats.bls]
Issue Analytics
- State:
- Created 4 years ago
- Comments:21 (21 by maintainers)
Top Results From Across the Web
Warnings when building docs · Issue #1562 · vyperlang/vyper
The Issue. Vyper docs are building, but many warnings are raised and some of the warnings mean the docs aren't displaying as intended....
Read more >See all warnings as errors when building Sphinx docs on ...
Turn warnings into errors ( -W and --keep-going options). This means the build fails if there is a warning and exits with exit...
Read more >Use Notes and Warnings — RST - Sphinx | Sublime
Warnings are formatted in the same way as notes. In the same way, lines must be broken and indented under the warning tag....
Read more >Suppress code analysis warnings - .NET - Microsoft Learn
This article covers the various ways you can suppress warnings from code analysis when you build your .NET app. You can suppress code...
Read more >UVISION: Stopping Build When Warnings Are Detected
Yes. You may change the Stop on Exit-Code options in the Properties dialog to stop the build process when a warning occurs. To...
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
Ugh… Maybe it is time to trim the change log too. It takes so much time to render as it is…
Closing since I’ve not seen extraneous warnings for a while.