Picking up from #15731, there are many places in numpy where we do something like:

try:
    something_which_throws_typeError
except TypeError:
    raise ValueError("a clearer explanation of what went wrong")

It would produce a marginally clearer error if we could change these to use traceback chaining. Our two options are either:

1. The inner error provides valuable infor

If somebody has some time for FUSE benchmarking:

diff --git a/src/borg/fuse.py b/src/borg/fuse.py
index 429790e4..27ab1c1a 100644
--- a/src/borg/fuse.py
+++ b/src/borg/fuse.py
@@ -644,12 +644,13 @@ def read(self, fh, offset, size):
                 data = self.data_cache[id]
                 if offset + n == len(data):
                     # evict fully read chunk from cache
-     

astropy/astropy#9468 highlighted that there are code snippets in docstrings that are not actually picked up during doctesting. I strongly feel that shouldn't be the case, we should skip any such testing in very rare occasions.
I tag this as a coordinates issue, but they may be other sub packages affected by the same problem.

Currently the toggle_fullscreen() contain these lines:

This function only works under the UNIX X11 video driver. For most situations it is better to call pygame.display.set_mode() with new display flags.

This is no longer accurate as the function works on windows for sure (tested) and looking at the code likely works on mac and with other display drivers on linux too. I believe it is also

MICROPY_PY_COLLECTIONS_ORDEREDDICT is set individually for every port. We should centralize it's use to py/circuitpy* settings. MICROPY_CPYTHON_COMPAT is an example of a setting that has already been centralized.

../../ports/unix/mpconfigport.h
102:#define MICROPY_PY_COLLECTIONS_ORDEREDDICT (1)

../../ports/nrf/mpconfigport.h
63:#define MICROPY_PY_COLLECTIONS_ORDEREDDICT       (1

Currently, the libexamples module is built in syslog-ng unconditionally.

This causes some inconvenience for those who want to experiment with the tutorials in gitbook: their drivers will conflict with the shipped version. They either need to choose another name and adapt significant amount of code for the followup, or need to disconnect the examples module from the build system, prior their wor

hi,
as you know, in SoLoud, the number of filters are limited
we should implement more like different reverbs, fir and irr filters, (these could be used to implement HRTF support), Chorus, One Poll, One Zero, Pole Zero, Two Pole, Two Zero, etc
a library exists called stk under zlib license which already implemented these maybe we can implement some of these out