headers
Benjamin Peterson | 3 Oct 00:11
Gravatar

2to3 bug fixes

What should the policy on 2to3 bug fixes be for the maintenance
branch? I'm asking because I remember vaguely someone suggesting that
new 2to3 fixers could fit into that category.

So, should I only merge "pure" bug fixes, or do I get to stretch the
definition a little?

--

-- 
Cheers,
Benjamin Peterson
"There's no place like 127.0.0.1."
_______________________________________________
Python-Dev mailing list
Python-Dev <at> python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/python-python-dev%40m.gmane.org
Permalink | Reply |
headers
Guido van Rossum | 3 Oct 00:16
Favicon

Re: 2to3 bug fixes

On Thu, Oct 2, 2008 at 3:13 PM, Benjamin Peterson
<musiccomposition <at> gmail.com> wrote:
> What should the policy on 2to3 bug fixes be for the maintenance
> branch? I'm asking because I remember vaguely someone suggesting that
> new 2to3 fixers could fit into that category.
>
> So, should I only merge "pure" bug fixes, or do I get to stretch the
> definition a little?

We agreed that new fixers (and possibly other changes) to 2to3 are
fair game for bugfix releases.

--

-- 
--Guido van Rossum (home page: http://www.python.org/~guido/)
_______________________________________________
Python-Dev mailing list
Python-Dev <at> python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/python-python-dev%40m.gmane.org
Permalink | Reply |
headers
Victor Stinner | 3 Oct 00:36
Gravatar

Re: 2to3 bug fixes

Le Friday 03 October 2008 00:13:16 Benjamin Peterson, vous avez écrit :
> What should the policy on 2to3 bug fixes be for the maintenance
> branch? I'm asking because I remember vaguely someone suggesting that
> new 2to3 fixers could fit into that category.

Python3 removes os.getcwdu() and introduces os.getcwdb(). A fixer should 
replace "os.getcwdu()" to "os.getcwd()". See for example attached fixer 
(which also replaced "getcwdu()" to "getcwd()").

--

-- 
Victor Stinner aka haypo
http://www.haypocalc.com/blog/
Attachment (fix_getcwdu.py): application/x-python, 572 bytes
_______________________________________________
Python-Dev mailing list
Python-Dev <at> python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/python-python-dev%40m.gmane.org
Permalink | Reply |
headers
Benjamin Peterson | 3 Oct 01:06
Gravatar

Re: 2to3 bug fixes

On Thu, Oct 2, 2008 at 5:36 PM, Victor Stinner
<victor.stinner <at> haypocalc.com> wrote:
> Le Friday 03 October 2008 00:13:16 Benjamin Peterson, vous avez écrit :
>> What should the policy on 2to3 bug fixes be for the maintenance
>> branch? I'm asking because I remember vaguely someone suggesting that
>> new 2to3 fixers could fit into that category.
>
> Python3 removes os.getcwdu() and introduces os.getcwdb(). A fixer should
> replace "os.getcwdu()" to "os.getcwd()". See for example attached fixer
> (which also replaced "getcwdu()" to "getcwd()").

Once again, please post it to the tracker and assign it to me.

--

-- 
Cheers,
Benjamin Peterson
"There's nothing quite as beautiful as an oboe... except a chicken
stuck in a vacuum cleaner."
_______________________________________________
Python-Dev mailing list
Python-Dev <at> python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/python-python-dev%40m.gmane.org
Permalink | Reply |

Gmane