Move unicode Python script into libstd_unicode crate.

[frewsxcv]

The only place this Python script is used is inside the libstd_unicode
crate, so lets move it there.

[rust-highfive]

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @alexcrichton (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

[alexcrichton]

@bors: r+

Nice!

If you're feeling adventurous, want to open an issue for translating this to the build script as well?

[bors]

📌 Commit ed1b78c has been approved by alexcrichton

[hanna-kruppe]

Many of the scripts in src/etc are only used from one place. I've considered it a dumping place for this sort of generator scripts. If we instead want build-time scripts to be stored in the crate they're related to, we should be consistent about it. (Obviously that doesn't have to happen in this PR but a I-cleanup issue would be good.)

[frewsxcv]

If you're feeling adventurous, want to open an issue for translating this to the build script as well?

Assuming what you mean is that we should call this Python file whenever we build this crate to generate that file (or something along those lines), one downside is that it creates another network dependency, which isn't great. Not a show stopper, but worth pointing out

[alexcrichton]

@frewsxcv oh sorry to clarify what I meant was actually rewriting the python logic in Rust, basically translating it into the build script.

I had forgotten about the network dependency though! In that case let's just leave it be.

[bors]

⌛ Testing commit ed1b78c with merge 42a4f37...