statically link this package's native code against the particular version of libstdc++ available at link time. This breaks other packages which have native code and depend on a different version of libstdc++.
It seems reasonable to me to ask your users to have a recent version of libstdc++ and libgcc available. Or perhaps you could publish two packages to PyPI, this one and one that uses a dynamic link?
These lines here,
https://github.com/GoogleCloudPlatform/cloud-profiler-python/blob/ea964fc72095ca60492e7e5e1e4a45b01a91eccc/setup.py#L46-L53
statically link this package's native code against the particular version of libstdc++ available at link time. This breaks other packages which have native code and depend on a different version of libstdc++.
It seems reasonable to me to ask your users to have a recent version of libstdc++ and libgcc available. Or perhaps you could publish two packages to PyPI, this one and one that uses a dynamic link?
Thanks!
PS: I discovered this because version 4.0.0 is incompatible with libsass.