A RetroSearch Logo

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

Search Query:

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

[Python-Dev] How to behave regarding commiting

[Python-Dev] How to behave regarding commiting [Python-Dev] How to behave regarding commitingFacundo Batista facundobatista at gmail.com
Fri Apr 17 03:32:35 CEST 2015
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?

Thank you!!

[0] http://bugs.python.org/issue23887

-- 
.    Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
Twitter: @facundobatista
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4