Sjoerd Job Postmus

ok. Agreed.

@janos: more like, yes, it can parse a file. But... it's not code he would(should?) write in real software, because the "field_a" means nothing.

@janos: if he fixed the "not working" part, it is still somewhat "hypothetical" (fieldnames make no sense). Should that also be fixed before opening?

@N3buchadnezzar: unsure, but I hear a lot of positive talk about numpy and pandas. Haven't used them though.

@janos. Thanks :).

On the other hand, there are some tips I would like to give for that piece of code.

I'm looking at codereview.stackexchange.com/questions/136699/…, and I'm not sure what to do. The code seems hypothetical, and I'm quite certain it won't run.

Well, adding examples is one of the things I was happy about.

Yes, I'm happy with the 2k.

(yes, reviews in progess, is what I meant)

Good point, because yes, it does mess up reviews.

Sure, not altered after an answer is posted.

? How do you mean, should not be happening?

So it's not like they purposefully changed things after my review.

(or she, btw)

But he made a lot of changes while I was reviewing.

I was reviewing revision 4

I thought of a few edge-cases during writing my review. I'll add them as an appendix.

Ok, got it.

It provides an output, and the user probably thinks it is correct.

@Quill

@Edward: That makes sense. Yes, the user thought it works.

It's not 'does not compile'-broken.

Sorry, 'is incorrect'.

does that fall into the 'off-topic' category? Normally I'd think 'yes', but in this case I'm leaning towards 'no'.

the code as supplied by the user was incorrect...

Hi :). Just a question about codereview.stackexchange.com/questions/124510/…