#35663 closed New feature (invalid)
Save disk space of pip install Django through opt-in to translations
Reported by: | Leandro de Souza | Owned by: | |
---|---|---|---|
Component: | Packaging | Version: | 4.2 |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Hey there!
While working on a new PC and suffering with lack of storage size I noticed that after installing Django on my virtual environment approximately 400-500MB of disk space is being used by the django
package, I was curious to find out what was being the culprit on it, and it turns out most of the disk usage inside the django
package is due to, translations, from several languages. On a specific project that will be only used on my country, I won't need any of those files and they're just taking a lot of precious disk space.
Would it be nice if we could opt-in for the translations since they take a lot of disk space.
Cheers
Change History (5)
comment:1 by , 3 months ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Type: | Uncategorized → New feature |
comment:2 by , 3 months ago
Summary: | Pip install Django takes ~0.5 GB → Save disk space of pip install Django through opt-in to translations |
---|
comment:3 by , 3 months ago
On my system:
$ du -hs ~/virtualenvs/.../lib/python3.11/site-packages/django 50M ~/virtualenvs/.../lib/python3.11/site-packages/django
comment:4 by , 3 months ago
Yup was going to make the same comment earlier: something's wrong if you're getting 500MB because I only have 30MB in my Django site-packages dir.
It's an interesting idea. Being able to do something
pip install Django[en,es,de]
would be cool but I think it's not backwards compatible - I think we would needDjango
to install all languages by defaultAs this is a request for new functionality, the recommended path forward is to propose and discuss the request with the community and gain consensus. To do that, please consider starting a new conversation on the Django Forum, where you'll reach a wider audience and likely get extra feedback.
If there is a community agreement for the feature request, which also has deemed it to be feasible given Django's backwards compatibility constraints, you are welcome to come back to the ticket and point to the forum topic, so we can then re-open it. For more details, please see the documented guidelines for requesting features.