Opened 8 years ago
Closed 8 years ago
#27671 closed Cleanup/optimization (wontfix)
Exclusion of .po files from next source distributions
| Reported by: | Illia Volochii | Owned by: | nobody |
|---|---|---|---|
| Component: | Internationalization | Version: | |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Should we actually have both .po and .mo files in source distributions?
I think, it will be better if there are only .mo ones.
This .po files are not used after they are compiled, are they?
But they take up quite a lot of memory (6.29 MB - it is about 21.5% of a whole Django distribution).
Change History (3)
comment:2 by , 8 years ago
I don't have much expertise here, but a few points come to mind:
Do other Python packages exclude po files?
At least for things like CSS and JavaScript, Debian wants us to include the source files rather than only minified versions. A similar principle might apply for po/mo files.
Does the test suite pass without po files?
comment:3 by , 8 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
No, excluding po files is not an option, like we wouldn't distribute only .pyc (or __pycache__). We are talking about a *source* distribution, aren't we?
See also #23321 about removal of .mo files.