|
5 | 5 | classes we care about change, or if a new version of Python supports a new |
6 | 6 | Unicode standard and we want it to affect our string decoding. |
7 | 7 |
|
8 | | -The file that we generate is based on Unicode 9.0, as supported by Python 3.6. |
| 8 | +The file that we generate is based on Unicode 11.0, as supported by Python 3.7. |
9 | 9 | You can certainly use it in earlier versions. This simply makes sure that we |
10 | 10 | get consistent results from running ftfy on different versions of Python. |
11 | 11 |
|
@@ -39,16 +39,16 @@ def make_char_data_file(do_it_anyway=False): |
39 | 39 | Build the compressed data file 'char_classes.dat' and write it to the |
40 | 40 | current directory. |
41 | 41 |
|
42 | | - If you run this, run it in Python 3.6 or later. It will run in earlier |
43 | | - versions, but you won't get the Unicode 9 standard, leading to inconsistent |
44 | | - behavior. |
| 42 | + If you run this, run it in Python 3.7.0 or later. It will run in earlier |
| 43 | + versions, but you won't get the Unicode 11 standard, leading to inconsistent |
| 44 | + behavior. Pre-releases of Python 3.7 won't work (Unicode 11 wasn't out yet). |
45 | 45 |
|
46 | 46 | To protect against this, running this in the wrong version of Python will |
47 | 47 | raise an error unless you pass `do_it_anyway=True`. |
48 | 48 | """ |
49 | | - if sys.hexversion < 0x03060000 and not do_it_anyway: |
| 49 | + if sys.hexversion < 0x030700f0 and not do_it_anyway: |
50 | 50 | raise RuntimeError( |
51 | | - "This function should be run in Python 3.6 or later." |
| 51 | + "This function should be run in Python 3.7.0 or later." |
52 | 52 | ) |
53 | 53 |
|
54 | 54 | cclasses = [None] * 0x110000 |
|
0 commit comments