This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author p-ganssle
Recipients Bert JW Regeer, Guillaume Sanchez, Manishearth, Socob, _savage, benjamin.peterson, bianjp, ezio.melotti, lemburg, loewis, mcepl, methane, mrabarnett, p-ganssle, r.david.murray, scoder, serhiy.storchaka, steven.daprano, terry.reedy, vstinner, xiang.zhang
Date 2020-01-06.18:52:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1578336726.11.0.94942387971.issue30717@roundup.psfhosted.org>
In-reply-to
Content
> Oh, also, if y'all are fine with binding to Rust (through a C ABI) I'd love to help y'all use unicode-segmentation, which is much less work that pulling in ICU. Otherwise if y'all have implementation questions I can answer them. This spec is kinda tricky to implement efficiently, but it's not super hard.

Is the idea here that we'd take on a new dependency on the compiled `unicode-segmentation` binary, rather than adding Rust into our build system? Does `unicode-segmentation` support all platforms that CPython supports? I was under the impression that Rust requires llvm and llvm doesn't necessarily have the same support matrix as CPython (I'd love to be corrected if I'm wrong on this).

(Note: I don't actually know what the process is for taking on new dependencies like this, just trying to point at one possible stumbling block.)
History
Date User Action Args
2020-01-06 18:52:06p-gansslesetrecipients: + p-ganssle, lemburg, loewis, terry.reedy, scoder, vstinner, benjamin.peterson, mcepl, ezio.melotti, mrabarnett, steven.daprano, r.david.murray, methane, serhiy.storchaka, _savage, xiang.zhang, Socob, Guillaume Sanchez, Bert JW Regeer, bianjp, Manishearth
2020-01-06 18:52:06p-gansslesetmessageid: <1578336726.11.0.94942387971.issue30717@roundup.psfhosted.org>
2020-01-06 18:52:06p-gansslelinkissue30717 messages
2020-01-06 18:52:05p-gansslecreate