Michael Kavulich

Another note here while I'm wrapping my head around things: I noticed all of the framework code for dealing with pointers is still present (for example, the "pointer" attribute added...

On the subject of third-party libraries for unit conversion, I did a bit of research and found a few potential logical choices: - **[unitpy](https://pypi.org/project/unitpy/)**. I believe this is the suggestion...

@nusbaume Rather than have a specific threshold I wonder if it would be possible to just not allow the pylint score to decrease? That way we're either doing no harm,...

@gold2718 Did you still have unresolved concerns on this PR?

@peverwhee Thanks again for listing this all out and organizing the pros and cons. After some time to digest the topic, I've come up with some (mildly rambly) thoughts: Off...

Details on optional arguments are included in https://github.com/NCAR/ccpp-doc/pull/73, see the preview [here](https://mike-k-tech-doc.readthedocs.io/en/latest/CompliantPhysicsParams.html#input-output-variable-argument-rules)

I have done some investigation, and I'll just post some information about the current state of CCPP with regards to this issue, as well as a proposed solution. ## Current...

Okay, following discussion at today's ccpp-framework meeting, I will procede with implementing this solution imposing hard limits on these string lengths in prebuild (and capgen if a simple combined change)....

Is this resolved by #383?

Just checking in on this PR based on our conversations with some developers last week: we had decided we would continue discussing unresolved concerns on this PR. As a reminder,...