3 ms·

They mention that one reason to remove these modules is storage savings, but then there is no information about how much storage will be freed up by their remov

They mention that one reason to remove these modules is storage savings, but then there is no information about how much storage will be freed up by their removal... Anyone have an idea if it is significant?

d0mine 5y ago
It is just unnecessary breakage for minuscule reward
- adtac 5y ago
  >miniscule reward how so? I see lower maintenance burden and vulnerability surface area as big rewards
  - johndfsgdgdfg 5y ago
    Internet is full of entitled narcissistic people. They can't imagine there're other important things in the world beside themselves and their needs.
    - phkahler 5y ago
      >> Internet is full of entitled narcissistic people. They can't imagine there're other important things in the world beside themselves and their needs. I completely agree with you, but I'm not sure which side of the dead batteries debate you're supporting with it! ;-)
Beltalowda 5y ago
On my system right now: % du -h --exclude=site-packages /usr/lib/python3.10 | tail -n1 41M /usr/lib/python3.10 The amount of savings seems to be about 0.83M: % ls -l \ **/*aifc* \ **/*asynchat* \ **/*asyncore* \ \ **/*cgi* \ **/*cgitb* \ **/*chunk* \ **/*crypt* \ **/*imghdr* \ **/*nntplib* \ **/*ossaudiodev* \ **/*pipes* \ **/*smtpd* \ **/*sndhdr* \ **/*spwd* \ **/*sunau* \ **/*telnetlib* \ **/*uu* \ **/*xdrlib* | awk '{ print $5 }' | paste -sd+ | bc 877283 This excludes the "msilib" and "nis" packages, which aren't on my system (I guess my distro excludes them?), and you should also really round up the files to the disk block size (usually 4k), so let's round it up to 1M. Is that significant? You decide. It doesn't seem all that significant to me given that the stdlib is 41M, so for space-constrained use-cases you're still not going to be able to copy/install all of the stdlib in the first place as it's still not even close to fitting on "devices with just a few hundred kilobyte of storage (e.g. BBC Micro:bit)" that the PEP mentions. I do think that removing these packages is a good idea, but "space savings" seems like a very weak argument.
- loeg 5y ago
  msilib and nis are probably Windows-only.
  - jandrese 5y ago
    NIS is definitely not a Windows thing. Maybe the python module would appear if you installed NIS support on your system?
    - loeg 5y ago
      Oh, you're right. I was thinking NDIS for some reason. Probably the distribution does not support NIS and/or does not enable it in their Python builds.
- Someone 5y ago
  > you should also really round up the files to the disk block size (usually 4k), so let's round it up to 1M. A decent first-go model for the amount of bytes to add is half a block per file. You’re adding about 168kB. That model would predict that for 84 files. I guess there are quite a few more in those (at least) 18 directories.

d0mine 5y ago

It is just unnecessary breakage for minuscule reward

adtac 5y ago
>miniscule reward how so? I see lower maintenance burden and vulnerability surface area as big rewards
- johndfsgdgdfg 5y ago
  Internet is full of entitled narcissistic people. They can't imagine there're other important things in the world beside themselves and their needs.
  - phkahler 5y ago
    >> Internet is full of entitled narcissistic people. They can't imagine there're other important things in the world beside themselves and their needs. I completely agree with you, but I'm not sure which side of the dead batteries debate you're supporting with it! ;-)

Beltalowda 5y ago

On my system right now: % du -h --exclude=site-packages /usr/lib/python3.10 | tail -n1 41M /usr/lib/python3.10 The amount of savings seems to be about 0.83M: % ls -l \ **/*aifc* \ **/*asynchat* \ **/*asyncore* \ \ **/*cgi* \ **/*cgitb* \ **/*chunk* \ **/*crypt* \ **/*imghdr* \ **/*nntplib* \ **/*ossaudiodev* \ **/*pipes* \ **/*smtpd* \ **/*sndhdr* \ **/*spwd* \ **/*sunau* \ **/*telnetlib* \ **/*uu* \ **/*xdrlib* | awk '{ print $5 }' | paste -sd+ | bc 877283 This excludes the "msilib" and "nis" packages, which aren't on my system (I guess my distro excludes them?), and you should also really round up the files to the disk block size (usually 4k), so let's round it up to 1M. Is that significant? You decide. It doesn't seem all that significant to me given that the stdlib is 41M, so for space-constrained use-cases you're still not going to be able to copy/install all of the stdlib in the first place as it's still not even close to fitting on "devices with just a few hundred kilobyte of storage (e.g. BBC Micro:bit)" that the PEP mentions. I do think that removing these packages is a good idea, but "space savings" seems like a very weak argument.

loeg 5y ago
msilib and nis are probably Windows-only.
- jandrese 5y ago
  NIS is definitely not a Windows thing. Maybe the python module would appear if you installed NIS support on your system?
  - loeg 5y ago
    Oh, you're right. I was thinking NDIS for some reason. Probably the distribution does not support NIS and/or does not enable it in their Python builds.
Someone 5y ago
> you should also really round up the files to the disk block size (usually 4k), so let's round it up to 1M. A decent first-go model for the amount of bytes to add is half a block per file. You’re adding about 168kB. That model would predict that for 84 files. I guess there are quite a few more in those (at least) 18 directories.