The implementation ofshrink relies onscipy, which I do not believe we want to make a dependency for building the docs.

See, for example, thedouble pendulum example which implements the code in python rather than using a scipy method which would provide better results.

Good observation! (Should probably not approve stuff with a heavy cold...)

It would be great to get rid of the scipy dependency.

The implementation ofshrink relies onscipy, which I do not believe we want to make a dependency for building the docs.

Would it be okay if the example uses "shrink=None" so that importing scipy is bypassed?
I think theshrink option gives a more pleasing result, and it would be good if we can let the users play with it.
If this is not acceptable, I can simply remove the shrink option and its dependency on scipy.

Welcome back@leejjoon !

I think the effect you are looking for can be had with library-native changes to theexplode parameter rather than passing throughscipy.ndimage.

Here is a quick example demonstrating the differences between the example as is (with your fixes so that it works, but withoutshrink, with your shrink implementation and with noshrink, but a uniform0.1 forexplode rather than(0, 0.05, 0, 0)

Okay, I have removed shrink parameter so the scipy dependency. However, I still think that it would be good to have ashrink parameter as it offers a rather general solution not specific to pie chart.

I also have rebased the PR to the current main and force-pushed it.

Welcome back@leejjoon !

Thanks!