3 ms·
What's next? A default socket timeout of X seconds for security reasons? What a joke and rather scary that apparently everyone or the majority on the internal s
by Phil_Latio 4y ago
What's next? A default socket timeout of X seconds for security reasons? What a joke and rather scary that apparently everyone or the majority on the internal side agrees with this change.
- linspace 4y agoI find it completely unpythonic. Python has become too important to do the right thing, there is money on the table.
- LtWorf 4y agoI think python is now completely owned by a couple big companies that decide everything. By this logic they should also block me from running benchmarks on too big lists, because I'm dossing myself.
- krick 4y agoThis. I don't really understand CPython decision-making process, but it just seems like a common sense that anybody who would find this a good idea surely must be a very junior developer who shouldn't be allowed to commit directly to the master branch of your local corporate project just yet… But basically breaking a perfectly logical behaviour just like that in a language used by millions of people… To me it's absolutely shocking.
- sidewndr46 4y agoYou would also need a limit on how large of a file can be written by python. Otherwise you could have a web server that takes an upload and stores it on disk which could fill the disk of the host machine. We can't expect developers to check for this, so Python must be patched to not write files larger than 2 kilobytes.