Use pytest for testing? about gmpy HOT 6 CLOSED

I think that would be great. In the past, I tried to minimize the need for external libraries when compiling gmpy2. But the development world has changed.

Case

from gmpy.

I tried to minimize the need for external libraries when compiling gmpy2

pytest will be a requirement only for testing.

from gmpy.

pytest will be a requirement only for testing.

Understood.

from gmpy.

I like the pytest format.

I've started to add MPFR 4.2.x specific functions. What is the best way to handle version dependent tests?

I've thought of the following options:

1. A version specific file with the version check done in runtests.py. I don't like adding complications to runtests.py.

2. Place them in the same file (test_mpfr.py) and surround the tests with a version check. This keeps runtests.py simple but can make test_mpfr.py larger and (possibly) more difficult to understand.

3. Create a file called test_mpfr_v420.py that contains tests for functions added in MPFR 4.2.0 and add a single version check at the beginning of the file.

I prefer option 3 but I'm open to any other options.

from gmpy.

That depends on the number of tests. You can use skip or skipif decorators to exclude either a single test function or an entire test file. Separate test file, probably, does make sense if there are many tested functions and/or if we want keep that file forever. But I would expect that at some point new functions will be mandatory, so option 2 sounds better (or we can split test_mpfr.py to several pieces based on functionality tested, e.g. arithmetics, elementary functions, etc).

from gmpy.

Thank you 😄 👍
Do you have any plans to release final 2.2.0 soon? 🤔
(just asking 😋 )

from gmpy.