* cmake modernization
- get rid of some warnings
- switch to what I hope is the correct way of doing things
- bump min cmake version to 3.16
- bump min boost version to 1.70
This builds on linux
* remove some usages of PYTHON_EXECUTABLE
* remove old-school python usage from coverage tests
* remove unused CI file
* bump boost version for windows builds to 1.84
* still trying to get the ci builds working
* typo
* eventually the CI will work
* robustify some tests
* misc adaptations/modernizations
plus a few changes to allow pytest discovery
* get the recap unittests running
* pytest config updates
* all tests pass
* integrate the pytest stuff into ctest
* integrate Projects dir
better cmake integration
* ci build env updates
* ignore more files
* remove six.py
* cleanup UnitTestPandasTools
* cleanup pytest
* remove obsolete use of rdkit.six from doctests
* update release notes
* mysterious CI fix
* add conftest to remove some tests
* remove the old python-based testing infrastructure
---------
Co-authored-by: Ric <ricrogz@gmail.com>
* remove all of the "from __future__" imports
* remove the first batch of rdkit.six imports/uses
* next step of rdkit.six removal
* removing xrange, range, and some maps
* next round of removals
* next round of cleanups
* fix inchi test
* last bits of "from rdkit.six" are gone
* and the last of the six stuff is gone
* strange importlib problem
* 1194: Review assignments of range in Python code
Task-Url: https://github.com/rdkit/rdkit/issues/1194
Either wrapped the range expression into a list or made sure that the
code is working with a range object.
* Refactored FeatFinderCLI script
* Revert "Refactored FeatFinderCLI script"
This reverts commit d9dcbce95d.
* Review rdkit.Chem.UnitTestSuppliers
* Replace optparse with argparse
* Change outDir default and fix variable name error
Windows git client, which converts line terminators to CR+LF
- added a conditional compilation clause to Code/RDBoost/import_array.h
to avoid a compilation error on Windows with Python3
