Nobody would have to use the original (you call it fat) Version of Python3.8
- because there would be pkgs.python38-slim
Fact check:
The difference in SIZE of pkgs.python38 and pkgs.python38Full is 3.4M (that is “fat” in your opinion)
- for micro services there are some people who want to get rid of this “overhead” - but those would use e.g.
alpineanyways - Nobody who wants to create a Data Science development environment with a sizes up to ~10GB (pure docker) will notice or even care about this <3.4M
But the truth is that these 3.4M cannot be called overhead because in an environment it’s getting vanished with all the needed dependencies of other python dependencies (for , stats/simulation, deep learning, visualization, geo-spatial, web dev , vision, audio, …, R, rPackages )
- e.g. the size of this random example bis 6.4M with and without
python38[Full](what surprises me, too - please validate it as well)
where is the place to find those statistics about nixpkgs? Sounds interesting!
How can you know about the reason of the people?
only because till now the focus of development with python in nixos was not focuses to development with UI components or interactions does not means that it is changing in the present/future, right?
Lets be open and keep up to the “user expected” standard
- Agile Principle 2: Welcoming changing requirements
If people try nixpkgs and expect python3.8 (the original Python) BUT using pkgs.python38 (the nixpkgs minimal version without the expected feature)
→ their build will fail and they won't use nix/nixpgs
→ so statistics is not all you should think about [because it reflects only the behavior of the past]
can you explain why you are so desperate about the original Python interpreter/ python3Full as its derivative in nixpkgs?