Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
It saves a small amount of memory, and a small amount of disk space if you distribute any archive form containing only the
.pyofiles. (If you useasserta lot, and perhaps with complicated conditions, the savings can be not trivial and can extend to running time too).So, it’s definitely not useless — and of course it’s being used (if you deploy a Python-coded server program to a huge number N of server machines, why ever would you want to waste N * X bytes to keep docstrings which nobody, ever, would anyway be able to access?!). Of course it would be better if it saved even more, but, hey — waste not, want not!-)
So it’s pretty much a no-brainer to keep this functionality (which is in any case trivially simple to provide, you know;-) in Python 3 — why add even “epsilon” to the latter’s adoption difficulties?-)