Mike Müller

Hi @wpbonelli, thanks for the tip. Using the Chocolatey route worked. It compiled on the first try. But many tests fail. ## Unit tests ``` ERROR REPORT: 1. IMSLINEAR7AR RCLOSE...

Running the tests with the nightly build `mf6.5.0.dev1_win64` from February 11, 2024, looks much better: ``` ==================== short test summary info ======================================= FAILED test_gwf_npf01_75x75.py::test_mf6model[0-npf01a_75x75] - KeyError: 'mf2005' FAILED test_gwf_npf01_75x75.py::test_mf6model[1-npf01b_75x75] -...

@wpbonelli I used `get-modflow` to install `mf2005` and `mfnwt`. They are available at the command line, but `pytest` does not find them. I copied them into `bin\downloaded`, where `pytest` finds...

Any news? The missing highlighting of built-ins really limits the use for teaching. The green color is important to explain the concept of built-ins. Some interesting, new extensions work only...

Looks like 4.1.3 fixes this problem.

`pycodestyle` doesn't complain about a `__new__` method without a docstring. Ruff should be consistent and not consider `__new__` an ordinary public method that requires a dosctring.

@dhruvmanila Thanks for the hint. Mixed up "code" and "doc".

Hi @mjr-deltares I had the same though shortly after I posted this. I updated my script as shown below, calling `.update()` at each time step. Still the same result, i.e....

Hey @langevin-usgs, it works. :) Edited the wrong file. I had two files with similar names. All examples work. Takes much longer to run since I update at each time...

Not yet. @mjr-deltares What do think about turning my little scripts into proper tests with better, automatic reporting? I can make a PR. What project would this belong to, to...