-
Notifications
You must be signed in to change notification settings - Fork 457
Upgrade to CLDR 44 #1070
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
v45 is scheduled to be released in less than a week. Maybe best to aim for that straight away? |
#1071 bumps us up to CLDR 44. Cc @nileshpatra via #1059 (comment) – would it be useful for e.g. Debian that there'd be a Babel version that uses CLDR 44, even if CLDR 45 is released soon? That said, the next version of Babel will not officially support Python 3.7 anymore; is that an issue? |
On Mon, Apr 15, 2024 at 07:12:43AM -0700, Aarni Koskela wrote:
#1071 bumps us up to CLDR 44. Cc @nileshpatra via #1059 (comment) – would it be useful for e.g. Debian that there'd be a Babel version that uses CLDR 44, even if CLDR 45 is released soon?
I am not sure if I understand that question. Currently CLDR version in Debian is
44 - which is what we need. It probably will be upgraded to 45 at some point.
That said, the next version of Babel will not officially support Python 3.7 anymore; is that an issue?
No problem.
|
Right, so I think it'll be a good idea to release a version of Babel that basically just bumps up to CLDR 44, just so that version can be easily shipped with the version of Debian that targets CLDR 44.
As far as I understand Debian's stability/release process, that might not be in the immediate cards as soon as 45 is released, though? :) |
On 15 April 2024 9:57:06 pm IST, Aarni Koskela ***@***.***> wrote:
> I am not sure if I understand that question. Currently CLDR version in Debian is 44 - which is what we need.
Right, so I think it'll be a good idea to release a version of Babel that basically just bumps up to CLDR 44, just so that version can be easily shipped with the version of Debian that targets CLDR 44.
> It probably will be upgraded to 45 at some point.
As far as I understand Debian's stability/release process, that might not be in the immediate cards as soon as 45 is released, though? :)
I apologise if I wasn't clear w/ my bug report earlier. Babel is doing fine in debian stable release (which happens roughly every 1.5-2 years) and has cldr version 41.
The cldr version is 44 in current unstable/testing which will be the next stable release around an year from now. cldr maybe updated to 45 in a few months or so since there's still an year in the next Debian stable release. As such there's no set target yet. If you plan to upgrade to 45, you could do so -- I'll apply the relevant patches.
|
As part of the Babel 2.15.0 release, an upgrade to CLDR 44 was included. The new CLDR version changes the date format for the en-GB locale to remove a comma in the full format. This change updates the tests so that both the old and new formats can be handled. This is done instead of pinning babel to a lower version, since we just care that formatting takes place. [Babel issue]: python-babel/babel#1070 [CLDR 44 changes]: https://www.unicode.org/cldr/charts/44/delta/en.html#Formats%20-%20Standard%20-%20Date%20Formats
CLDR v44 has been released a while ago. Are there any plans to include it in babel?
The text was updated successfully, but these errors were encountered: