Local autotests - TypeError: unexpected keyword argument errors

[cnicol-gwlogic]

Can anyone provide advice on what I've done wrong with my local autotest setup? I am seeing these errors almost universally across all tests (windows 11, python 3.9, develop branch flopy as of PR #2179:

I (think I) followed the guidance in here and here to no avail. It seems like a version issue to me (of something related to the autotest processes) - I've googled for it, and found similar but not exactly the same issues. I reverted pytest to 8.0.0 (from latest) to check but get the same issue.

Any tips? Thanks.

As an aside, some of the guidance needs to be updated for Ruff rather than Black etc. I'm happy to have a go at that once I sort out this local issue of mine, so I can flag for it for others.

[mwtoews]

A quick answer is that you'll need to upgrade your modflow-devtools to at least v1.1.0 when the strict parameter was added.

[cnicol-gwlogic]

Thanks for this @mwtoews I had quite an old version of modflow-devtools. I am however still getting a similar error:

Any further thoughts? Cheers.

[cnicol-gwlogic]

For others: solution seems to be to downgrade pytest to pre 8.0 (i.e. 7.4.4, per here). Thanks @mwtoews , @wpbonelli

[mwtoews]

You probably have pytest-cases installed somewhere, which interferes with pytest-8.x (#2077). Remove pytest-cases and try again.

[cnicol-gwlogic]

@mwtoews boom! You're spot on - thankyou. After removing pytest-cases, pytest 8.2.0 is working.

[wpbonelli]

edit echoing @mwtoews above @cnicol-gwlogic that looks like an old version of modflow-devtools, where the has_pkg() function is coming from. Updating should solve it. Maybe it ought to have a mention in the developer docs..

And that's my omission re: the ruff/black transition. Thanks for raising — I can do it if you like, with some extra info on test depenencies?

[cnicol-gwlogic]

Thanks @wpbonelli go for it with the guidance updates. Thanks a lot for the quick reply too. Cheers.