JvR> So, making join() a builtin makes a whole lot of sense. Not JvR> doing this because people sometimes use a local reference to JvR> os.path.join seems awfully backward.
I agree. Have we agreed on the semantics and signature of builtin join() though? Is it just string.join() stuck in builtins?
(let's leave the __join__ slot and other super-generalized variants for 2.2)