RetroSearch Browse

Fri Apr 17 03:41:49 CEST 2015 · https://mail.python.org/pipermail/python-dev/2015-April/139183.html

On Fri, Apr 17, 2015 at 4:32 AM, Facundo Batista
<facundobatista at gmail.com> wrote:
> Hola!
>
> I'm asking this because quite some time passed since I was active in
> the development of our beloved language.
>
> I'm trying to not break any new rule not known by me.
>
> I opened a bug recently [0], somebody else proposed a patch that I
> like. However, that patch has no test. I will do a test for that code,
> but then what?
>
> Shall I just commit and push? Or the whole branch should be proposed
> for further reviewing?

Hi,

Since writing a test for that patch is simple, I'd just commit it to
the default branch.

--Berker

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2015-April/139183.html below:

[Python-Dev] How to behave regarding commiting