> On Mar 3, 2026, at 08:49, Tom Keffer <[email protected]> wrote:
>
> There is no change in the code base, only in the test suite. Frankly, I don't
> know why we release the test suite as part of a packaged distribution.
since we are shipping pure python, we don't distribute a source package, only a
'binary' package. but that 'binary' package *is* the sources, so its probably
good that the test code is in there in case anyone needs to run the tests - no
need to download a source package or tarball and risk version mismatch or
fat-fingering.
if you want to use non-backward-compatible python constructs only in the unit
tests, we could tell the precompiler to *not* traverse the test code. but that
would be dangerous.
for wee projects (like weewx :) i usually put all of the unit tests in a single
directory 'tests' tree rooted at the base of the project, instead of putting a
'tests' directory in each python module directory. but that is not as
important now that pytest does the file/directory matching that we used to have
to do in shell scripts and make targets.
(and of course do not call any directory or file 'test', even if no one uses sh
anymore :)
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/weewx-user/040E846C-EA7E-4AE3-8530-62F1C8FD52B5%40gmail.com.
