Albert Steppi

> I am more worried about something else. If we split into sphinx-generated documentation for which we maintain previous versions but put some documents on a static website without a...

I've created an FAQ here with more information on the translation project here, https://scientific-python-translations.github.io/faq/. Feel free to take a look and let me know if you'd be interested in participating...

Thanks @mdhaber! Very nice write-up. Looking forward to the discussion.

Also, @fancidev see #19601 and https://github.com/cupy/cupy/pull/8140 for examples of this in action. I’d say we can’t use Boost directly because it doesn’t support CUDA. The hope is to have a...

> If what @steppi said about making special a separate codebase and hydrating all stakeholders from a common place, is going to happen soon, then noone probably will care what...

> > or do you foresee it to be adopted by other projects > > I'll let @steppi answer himself, though widespread reusability is certainly a goal AFAICT (both in...

The test failure ``` ERROR: objects in refguide but not in scipy.special.__all__:: assoc_legendre_p assoc_legendre_p_all legendre_p legendre_p_all sph_harm_y sph_harm_y_all sph_legendre_p sph_legendre_p_all This issue should likely be fixed by removing these objects...

You can get rid of this warning on gcc ``` ../scipy/special/special/recur.h:89:6: note: the ABI of passing structure with ‘complex float’ member has changed in GCC 4.4 89 | void forward_recur(InputIt...

@izaid, I'm going to go ahead and make the small changes mentioned above myself and push since I know you're busy now.

The multiufuncs still have a lot of scaffolding methods that are not meant to be user facing which are still public. I'll push an update for this too. ``` 'key',...