Introduces static attribute Operation.unpacked_args_to_init

[kaushikcfd]

Passing unpacked args is generally helpful if the class derived from
Operation has its constructor implemented via a dataclass.

[coveralls]

Coverage increased (+0.004%) to 96.449% when pulling fe05c21 on kaushikcfd:unpacked_args_to_init into 390b2d3 on HPAC:master.

[kaushikcfd]

Added a regression that checks for the new feature, so the coverage should go back up. However, unsure about the performance regression, I don't think we are doing anything very expensive than what was already there.

[wheerd]

Looks good, the tests are failing with Python 3.6 though because of the dataclasses. @hbarthels what do you think, can we drop support for Python 3.6? I think it is close to end of life anyways.

[kaushikcfd]

Looks good, the tests are failing with Python 3.6 though because of the dataclasses.

For Py3.6 CI we could add dataclasses as a requirement. Wdyt?

[wheerd]

@kaushikcfd I merged it and created a new release. Thank you for your PR and sorry for the delay!

[hbarthels]

Sorry for not joining this conversation earlier.

Looks good, the tests are failing with Python 3.6 though because of the dataclasses. @hbarthels what do you think, can we drop support for Python 3.6? I think it is close to end of life anyways.

Yes, I'm fine with dropping support for Python 3.6.

However, unsure about the performance regression, I don't think we are doing anything very expensive than what was already there.

I don't think this is an actual performance regression. A few times already, I observed that a test failed because it exceeded the time limit, even if there were no changes that affected the test. I suspect that those are more or less random performance fluctuations. Perhaps we should increase the time limit for all test by a little.