@tenderlovemaking (aaron patterson) implemented a patch for this For rubyinstaller2 the issue is fixed with 3.4.4 release, and the fix will be backported to 3.3.9 and 3.2.9 whenever they get released I believe semantic versioning prevents doing this until ruby 3 is released (many years from now) but i agree that this issue should be added to the ruby 3 roadmap. I'm also considering whether we can have a general default, e.g Set by an environment variable or global within ruby, e.g We could also consider adding keyword arguments to file.open and so on.
So it looks like ruby is now looking at the wrong location and no longer finding __pioinfo Short term we'll be rolling out a fix that for this function that undoes this optimization, which should fix this specific error for the many ruby users in the wild. Suggesting a rename (eregon) namespace seems to confuse many people (that feature is not about namespacing, modules do that, but about multiple execution contexts with their own $load_path, $loaded_features, copy of core classes, etc) Can we think of another name for that feature How about context or ruby::context? I really feel like proposing to change all these octal constants to hexadecimal, in order to bring them into the current century and align them with all the other data surrounding character encoding.
So i propose explicitly dropping support for windows older than vista/2008 8/server 2012
OPEN
