nostr:npub16mtxp68k8c3p2sj0wzhagt3kd8ywkvzlkfyt3vrx9cahzfz000vs8dpnwy The reason for that is that it's super hard to convert an SVG path to something shapely understands while covering all the million corner cases and not doing something unexpected. For example, an SVG path can have both cubic bezier curves and circular arcs on its outline, which shapely would have to render out to a list of straight lines to some precision first, which is probably not what an user extends.