State of Tick in 2023

[PhilipDeegan]

Issues:

• Sparse array serialization segfaults on various platforms with various versions of python
• Various deprecation warnings for csc/csr_matrix
• A number of tests are only failing on OSX

Tests to be disabled generally:

grep -A 1 -r "\.skip" .
./tick/survival/tests/convolutional_sccs_test.py:    @unittest.skip("issue with StratifiedKFold")
./tick/survival/tests/convolutional_sccs_test.py-    def test_LearnerSCCS_fit_KFold_CV(self):
--
./tick/solver/tests/sdca_test.py:    @unittest.skip("Is failing by a small amount - to assess")
./tick/solver/tests/sdca_test.py-    def test_sdca_identity_poisreg(self):
--
./tick/random/tests/random_test.py:    @unittest.skip("Needs checking with scipy benchmark")
./tick/random/tests/random_test.py-    def test_uniform_int_random(self):
--
./tick/random/tests/random_test.py:    @unittest.skip("Needs some clarity around what we should assert")
./tick/random/tests/random_test.py-    def test_poisson_random(self):

For the moment I will be configuring Github actions to only show the builds which do in fact finish. This is not ideal, but considering the state of things I think it's best to have something that we know consistently works for people to make PRs against. Once this is done I can try adding python3.10 on all platforms and checking if it builds ok.

[oresthes]

Are there any plans for maintaing this package in the long term?

[PhilipDeegan]

@oresthes I'm aiming to get a new release on pypi/pip in the near future