Skip to content

Conversation

@veluca93
Copy link
Contributor

Depends on cms-dev/isolate#4.

@wil93
Copy link
Member

wil93 commented Mar 21, 2015

oh-god-i-need-it-i-need-it

👍

@dario2994
Copy link

👍

1 similar comment
@Harniver
Copy link

👍

@gabrfarina
Copy link

This is very helpful indeed!

@walypala23
Copy link

👍

1 similar comment
@Alice94
Copy link

Alice94 commented Mar 22, 2015

👍

@giomasce
Copy link
Member

I'm having a look at this. The contribution is mostly good and welcome, but the code quality definitely needs some improvement.

  • All our code should be compliant to PEP8 and accepted by pyflakes. Your patch introduces important errors: please, fix them. BTW, do you use our fantastic Git hooks?
  • Although I am a big fan of colored output (and CMS logs color scheme was indeed an idea of mine), I definitely cannot stand with magic constants and ANSI commands in the code. Please use the methods starting from https://github.com/cms-dev/cms/blob/master/cms/log.py#L147 to include colors in the terminal output (small patches may be required for what you want to do).

I will add more specific feedback in diff comments.

@veluca93
Copy link
Contributor Author

It was basically a quick-and-dirty improvement to use during the stage - I
will clean it up as soon as possible.

Most decisions were made considering if something had actually been used
during our experience - for example supporting only GroupMin, aka subtasks,
and (something else), that is assumed to mean a subtask-less task (and thus
mapped in something that has the same score output); this, in fact, covers
all the cases we actually used in our stages.
On Mar 22, 2015 10:28 PM, "Giovanni Mascellani" [email protected]
wrote:

I'm having a look at this. The contribution is mostly good and welcome,
but the code quality definitely needs some improvement.

All our code should be compliant to PEP8 and accepted by pyflakes.
Your patch introduces important errors: please, fix them. BTW, do you use
our fantastic Git hooks
https://github.com/cms-dev/cms/wiki/Developerhints#git-hooks?

Although I am a big fan of colored output (and CMS logs color scheme
was indeed an idea of mine), I definitely cannot stand with magic constants
and ANSI commands in the code. Please use the methods starting from
https://github.com/cms-dev/cms/blob/master/cms/log.py#L147 to include
colors in the terminal output (small patches may be required for what you
want to do).

I will add more specific feedback in diff comments.


Reply to this email directly or view it on GitHub
#414 (comment).

@giomasce
Copy link
Member

It definitely seemed to be quick-and-dirty. Let me just notice that there is not much point to creating a PR and adding half a dozen +1 to it if you are aware that it still requires work...

However, other than the hundreds of details that I pinpointed, it appears to be ok (you may also want to squash the commits together, since there is more or less nothing that separates them).

@giomasce giomasce self-assigned this Mar 22, 2015
@veluca93
Copy link
Contributor Author

I agree on that - I had some peer pressure :P
On Mar 22, 2015 11:20 PM, "Giovanni Mascellani" [email protected]
wrote:

It definitely seemed to be quick-and-dirty. Let me just notice that there
is not much point to creating a PR and adding half a dozen +1 to it if you
are aware that it still requires work...

However, other than the hundreds of details that I pinpointed, it appears
to be ok (you may also want to squash the commits together, since there is
more or less nothing that separates them).


Reply to this email directly or view it on GitHub
#414 (comment).

@wil93
Copy link
Member

wil93 commented Mar 22, 2015

Let me just notice that there is not much point to creating a PR and adding half a dozen +1 to it if you are aware that it still requires work

That was the buzz of having a really nicer cmsMake that we all locally patched immediately, and the +1 wave was a display of that (just some CMS love 😄)

On a side note: I was under the impression that cmsMake was almost a separated piece of CMS and didn't really require its code standards, I see that I was wrong (BTW: it would be awesome to brainstorm a polygon-like cmsMake, or convince polygon authors to release their code 😛)

@stefano-maggiolo
Copy link
Member

Well, I admit that the code quality is much lower, but that's not a good reason to include more code with low code quality :)

@giomasce
Copy link
Member

Definitely +1 for Stefano.

@giomasce
Copy link
Member

Merged, at last. Backers, please be happy! :-)

@giomasce giomasce closed this Apr 26, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

9 participants