[MIR] python-babel
Bug #941913 reported by
Chuck Short
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-babel (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
Availability: Currently in universe
Rationale: Dependency for nova.
Security: No security history.
Quality Assurance: Package works out of the box with no prompting. There is no major bugs in Ubuntu and the is no major bugs in Debian.
Standards Compliance: FHS and Debian Policy compliant.
Maintenance: Simple python package that the Ubuntu Server Team will take care of.
Dependencies: All are in main except python-tz.
Changed in python-babel (Ubuntu): | |
status: | Expired → Triaged |
importance: | Undecided → High |
To post a comment you must log in.
Would be nice to see a bug subscriber.
Tests are run, which is great. But two tests fail for me... Does this build clean for you? (It built cleanly in the archive a few weeks ago...)
python-babel also ships its own binary copy of certain locale data, which I'm not super thrilled about. We already have the less-comprehensive locales package as well as the much more comprehensive python-pyicu package.
Unfortunately, we can't just change nova to use pyicu because nova's interest is not in the babel library, but the pybabel build tool for managing gettext files. (Another duplicated tool in main.) But nova upstream used to use distutils for managing those files and explicitly went back to using babel, so it's unlikely they'll want to switch back yet again.
So, if we need python-babel for translations, I'm fine with us adding it to main. But two things:
A) Can I get a confirmation about the failing tests and ideally a fix if they are real?
B) Does nova really need python-babel if all it does is manage gettext files? Won't that be handled by the langpacks once it's in main? (i.e. this package won't need to ship its own po files)