[Python-Dev] How to behave regarding commiting (original) (raw)
Facundo Batista facundobatista at gmail.com
Fri Apr 17 03:32:35 CEST 2015
- Previous message (by thread): [Python-Dev] Not being able to compile: "make: *** [Programs/_freeze_importlib] Error 1"
- Next message (by thread): [Python-Dev] How to behave regarding commiting
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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
- Previous message (by thread): [Python-Dev] Not being able to compile: "make: *** [Programs/_freeze_importlib] Error 1"
- Next message (by thread): [Python-Dev] How to behave regarding commiting
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]