On Tue, Sep 30, 2008 at 10:59 AM, <[EMAIL PROTECTED]> wrote: > On 02:32 pm, [EMAIL PROTECTED] wrote: >> If 2.6 weren't pretty much released already I'd ask to add >> os.getcwdb() there, as an alias for os.getcwd(), and add a 2to3 fixer >> that converts os.getcwdu() to os.getcwd(), leaves os.getcwd() alone >> (benefit of the doubt) and leaves os.getcwdb() alone as well (a strong >> indication the user meant to get bytes in the 3.x version of their >> code. (Similar to using bytes instead of str in 2.6 even though they >> mean the same thing there -- they will be properly separated in 3.x.) > > In the absence of a 2.6 getcwdb, perhaps the fixer could just drop the > "benefit of the doubt" case? It could always be added to 2.7, and the > parity release of 2to3 could have a --2.7 switch that would modify the > behavior of this and other fixers.
I'm not sure what you're proposing. *My* proposal is that 2to3 changes os.getcwdu() calls to os.getcwd() and leaves os.getcwd() calls alone -- there's no way to tell whether os.getcwdb() would be a better match, and for portable code, it won't be (since os.getcwdb() is a Unix-only thing). -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
