# Allow beta UCD files to be used in the future?

**URL:** <https://discuss.python.org/t/allow-beta-ucd-files-to-be-used-in-the-future/106626>\
**Category:** Core Development\
**Created:** [March 21, 2026, 12:42am UTC](https://discuss.python.org/t/allow-beta-ucd-files-to-be-used-in-the-future/106626 "2026-03-21T00:42:30Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![clin1234](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/clin1234/32/20576_2.png) [@clin1234](https://discuss.python.org/u/clin1234)\
**Post date:** [March 21, 2026, 12:42am UTC](https://discuss.python.org/t/allow-beta-ucd-files-to-be-used-in-the-future/106626/1 "2026-03-21T00:42:30Z")

</div>

The next beta review period of Unicode, Unicode 18, is expected to last from May to July 2026. [Beta Review Status](https://www.unicode.org/versions/beta.html). Given that according to [PEP 790 – Python 3.15 Release Schedule | peps.python.org](https://peps.python.org/pep-0790/), no new features will be allowed starting in 3.15beta1, such feature would be added in the upcoming 3.16: [PEP 826 – Python 3.16 Release Schedule | peps.python.org](https://peps.python.org/pep-0826/)

This may seem contrived now, but suppose that a future Unicode’s beta review period overlaps with a future Python version’s alpha releases. I think that it would be helpful within [cpython/Tools/unicode/makeunicodedata.py at main · python/cpython](https://github.com/python/cpython/blob/main/Tools/unicode/makeunicodedata.py) to allow pre-release UCD files to be exposed in the `unicodedata` module through some option, given that by a Unicode’s beta review period, code points and names are guranteed to be fixed.

---

<div class="post-metadata">

**Author:** ![Rosuav](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/rosuav/32/3429_2.png) [@Rosuav](https://discuss.python.org/u/Rosuav)\
**Post date:** [March 21, 2026, 1:15am UTC](https://discuss.python.org/t/allow-beta-ucd-files-to-be-used-in-the-future/106626/2 "2026-03-21T01:15:40Z")

</div>

> [@clin1234](#):
>
> given that by a Unicode’s beta review period, code points and names are guranteed to be fixed.

What is still able to change, and will any of that cause confusion in Python?

---

<div class="post-metadata">

**Author:** ![clin1234](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/clin1234/32/20576_2.png) [@clin1234](https://discuss.python.org/u/clin1234)\
**Post date:** [March 21, 2026, 1:02pm UTC](https://discuss.python.org/t/allow-beta-ucd-files-to-be-used-in-the-future/106626/3 "2026-03-21T13:02:23Z")

</div>

According to the site, only property values and algorithms of the characters are subject to revision, and they are very unlikely

---

<div class="post-metadata">

**Author:** ![hugovk](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/hugovk/32/14505_2.png) [@hugovk](https://discuss.python.org/u/hugovk)\
**Post date:** [April 14, 2026, 6:36am UTC](https://discuss.python.org/t/allow-beta-ucd-files-to-be-used-in-the-future/106626/4 "2026-04-14T06:36:02Z")

</div>

| Date | Python 3.15 | Unicode 18.0.0 |
| --- | --- | --- |
| 5 May | b1 | |
| 26 May | | Beta opens |
| 2 Jun | b2 | |
| 23 Jun | b3 | |
| 7 Jul | | Beta closes |
| 18 Jul | b4 | |
| 4 Aug | RC1 | |
| 1 Sep | RC2 | |
| 15 Sep | | Final release |
| 1 Oct | Final release | |

Their beta review is fully contained in our beta period:

> ### Beta Review
> 
> The primary focus for the beta review phase aims is review of character property data and any algorithmic changes which may impact implementations of the new release. Character repertoire has been established, and can be considered stable at this point. Additions or removals of characters are very unlikely before release. The code points and names of new characters are also no longer subject to revision.
> 
> A _complete_ set of data files for the UCD is provided during beta review, as well as complete data for synchronized Unicode Technical standards (UTS #10, UTS #39, UTS #46, and UTS #51) . Implementers should be checking this new data and report on any problems or inconsistencies discovered. All other assets planned for release are also updated for the beta review, including the preliminary code charts and all the annexes. Feedback on those other assets is also welcome during beta review.

---

<div class="post-metadata">

**Author:** ![ncoghlan](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/ncoghlan/32/14266_2.png) [@ncoghlan](https://discuss.python.org/u/ncoghlan)\
**Post date:** [April 14, 2026, 7:07am UTC](https://discuss.python.org/t/allow-beta-ucd-files-to-be-used-in-the-future/106626/5 "2026-04-14T07:07:39Z")

</div>

We benefit from the likes of Fedora accommodating our beta releases within their beta testing periods, so adopting a comparable policy for the standard library with respect to the Unicode database beta period seems reasonable to me.

---

<div class="post-metadata">

**Author:** ![malemburg](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/malemburg/32/50_2.png) [@malemburg](https://discuss.python.org/u/malemburg)\
**Post date:** [April 14, 2026, 7:51am UTC](https://discuss.python.org/t/allow-beta-ucd-files-to-be-used-in-the-future/106626/6 "2026-04-14T07:51:57Z")

</div>

> [@clin1234](#):
>
> allow pre-release UCD files to be exposed in the `unicodedata` module through some option

How exactly would you see that working ?

Note that the Unicode database is not only used for the data in `unicodedata`, but also for many other string methods, so changes are immediately and widely visible, even if you don’t make use of `unicodedata`.

I’m not against the idea of optionally making it available, but it does add quite a bit of maintenance overhead and it’s also not clear how testing would work.

If you’re only interested in the `unicodedata` module getting updated, this would make things easier, but then you could also use a package on PyPI to be able to access multiple versions of the Unicode database for this purpose.

---

<div class="post-metadata">

**Author:** ![SnoopJ](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/snoopj/32/7944_2.png) [@SnoopJ](https://discuss.python.org/u/SnoopJ)\
**Post date:** [April 14, 2026, 5:03pm UTC](https://discuss.python.org/t/allow-beta-ucd-files-to-be-used-in-the-future/106626/7 "2026-04-14T17:03:23Z")

</div>

I’m a soft +1 on this, especially as I was recently reminded of [some changes](https://github.com/python/cpython/pull/109560/changes#diff-17ec60c9bf5044a66fffc2f5bd5b6c4a6df192332bd2762ddf4336a80f8f8f25R1110-R1112) to `makeunicodedata.py` that were required in the course of a routine update. It’s nice to get advance notice of that kind of thing. On the other hand, I don’t think there is a _big_ need for this in CPython.

Actually, I think no big changes to `Tools/` (and associated maintenance burden) are required to support this. The UCD files are all named the same way, and the only difference in the `unicode.org` URLs is the use of `draft` in place of the version. The build seems to work fine if we change `UNIDATA_VERSION = “draft”`, see below.

On the assumption that this continues to work (decent odds, `unicode.org` URLs are pretty predictable), the only change necessary is probably to allow the target `UNIDATA_VERSION` to be changed at the commandline. The bigger concern is what the workflow for testing against Unicode draft versions should be, and how that intersects with the existing workflows that a release manager is juggling (i.e. along the lines of Hugo’s remarks).

```python
[jgerity@giskard ~/repos/cpython (main 2026-04-14 *⏳)]
$ git diff Tools/unicode/ # unicodedata files were also updated by the tool
diff --git a/Tools/unicode/makeunicodedata.py b/Tools/unicode/makeunicodedata.py
index 5db850ca2d1..6a465bfdaf1 100644
--- a/Tools/unicode/makeunicodedata.py
+++ b/Tools/unicode/makeunicodedata.py
@@ -45,7 +45,7 @@
 # * Doc/library/stdtypes.rst, and
 # * Doc/library/unicodedata.rst
 # * Doc/reference/lexical_analysis.rst (three occurrences)
-UNIDATA_VERSION = "17.0.0"
+UNIDATA_VERSION = "draft"
 UNICODE_DATA = "UnicodeData%s.txt"
 COMPOSITION_EXCLUSIONS = "CompositionExclusions%s.txt"
 EASTASIAN_WIDTH = "EastAsianWidth%s.txt"
[jgerity@giskard ~/repos/cpython (main 2026-04-14 *⏳)]
$ ./configure && make -j10
... snip ...
[jgerity@giskard ~/repos/cpython (main 2026-04-14 *⏳)]
$ ./python -c "import sys, unicodedata; print(sys.version); print(unicodedata.name(chr(0x16D98)))" # randomly selected codepoint new in 18.0.0
3.15.0a8+ (heads/main-dirty:3cb7eaec857, Apr 14 2026, 12:07:40) [GCC 13.3.0]
CHISOI SIGN ANUSVARA
[jgerity@giskard ~/repos/cpython (main 2026-04-14 *⏳)]
$ python3.14 -c "import sys, unicodedata; print(sys.version); print(unicodedata.name(chr(0x16D98)))"
3.14.2 (main, Dec 9 2025, 15:26:04) [GCC 12.3.0]
Traceback (most recent call last):
  File "<string>", line 1, in <module>
    import sys, unicodedata; print(sys.version); print(unicodedata.name(chr(0x16D98)))
                                                       ~~~~~~~~~~~~~~~~ ^^^^^^^^^^^^^^
ValueError: no such name

```

* * *

> [@malemburg](#):
>
> If you’re only interested in the `unicodedata` module getting updated, this would make things easier, but then you could also use a package on PyPI to be able to access multiple versions of the Unicode database for this purpose.

I’ll plug the [`unicodedata2`](https://pypi.org/project/unicodedata2/) project here, which is patterned directly on `unicodedata`, has decent backwards compatibility, and usually updates pretty promptly. It is not built with _multiple_ versions in mind, and has the same narrow perspective on the UCD that the stdlib module does, but when you want _”`unicodedata` but when a not-out-of-date UCD”_ it works great.

There are some other projects on PyPI that aim for a more complete picture of UCD but none of the ones I’ve looked at seem to be particularly active.

---

<div class="post-metadata">

**Author:** ![clin1234](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/clin1234/32/20576_2.png) [@clin1234](https://discuss.python.org/u/clin1234)\
**Post date:** [May 21, 2026, 6:45pm UTC](https://discuss.python.org/t/allow-beta-ucd-files-to-be-used-in-the-future/106626/8 "2026-05-21T18:45:43Z")

</div>

LLVM just recently merged in Unicode 18 tables: [Update Unicode tables to Unicode 18.0. by cor3ntin · Pull Request #198255 · llvm/llvm-project](https://github.com/llvm/llvm-project/pull/198255)

So there’s precedent in merging in beta UCD versions

---

<div class="post-metadata">

**Author:** ![clin1234](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/clin1234/32/20576_2.png) [@clin1234](https://discuss.python.org/u/clin1234)\
**Post date:** [July 16, 2026, 8:43pm UTC](https://discuss.python.org/t/allow-beta-ucd-files-to-be-used-in-the-future/106626/9 "2026-07-16T20:43:56Z")

</div>

Pinging back: I’ve made a PR to LLVM to finish supporting the beta Unicode version: [Finish supporting Unicode 18 by clin1234 · Pull Request #199111 · llvm/llvm-project](https://github.com/llvm/llvm-project/pull/199111)

---

<div class="post-metadata">

**Author:** ![storchaka](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/storchaka/32/217_2.png) [@storchaka](https://discuss.python.org/u/storchaka)\
**Post date:** [July 17, 2026, 6:18am UTC](https://discuss.python.org/t/allow-beta-ucd-files-to-be-used-in-the-future/106626/10 "2026-07-17T06:18:39Z")

</div>

We recently discussed this in [What versions of the Unicode Character Database to support?](https://discuss.python.org/t/what-versions-of-the-unicode-character-database-to-support/105318)

The consensus was that it is not worth to support multiple UCD versions in the stdlib, besides the latests and historical 3.2.0. Recently added functions do not have 3.2.0 equivalent, they are signgle (latest) version only.
