@fay https://github.com/python/cpython/pull/139566 this is actually a reasonable response to be clear. but the incredibly poor documentation of the buffering arguments to the open() function is kind of remarkable
@fay https://github.com/python/cpython/pull/139566 this is actually a reasonable response to be clear. but the incredibly poor documentation of the buffering arguments to the open() function is kind of remarkable
@fay have i mentioned the buffer overflow clearly introduced by a well-known racist that "core" devs tried to close and then said was a GIL issue
@hipsterelectron i think you've alluded to it but i don't know what it is
@fay in particular observe the comments modified, especially in Objects/abstract.c, in which a clause indicating the ability to return 0 is removed
@fay it makes me feel really nihilistic and that's obviously unhelpful. i wanted to base my build system off of cpython like pants did but this makes me question if that can ever be made secure
@fay cpython is completely captured by intelligence agencies
@hipsterelectron i have a hanlon razor bias but tbh who knows these days lol
@fay it's not a single incident. the METADATA format in wheels refuses to use json as i introduced several years ago to pip and instead relies upon an unspecified format that allows dependencies to be injected. i am completely done with making excuses
A space for Bonfire maintainers and contributors to communicate