Support Python 3.11

[nzw0301]

Motivation

Sub-task of optuna/optuna#3964 for tracking this repo.

Description

Add python 3.11 to github action's version matrix. An example PR is #160.

Alternatives (optional)

Additional context (optional)

I summarise the status of targets as follows:

• allennlp.yml
  • development has been stopped, we might not be able to support python 3.11
• base.yml: Add python 3.11 to version-matrix except for integration #160
• catboost.yml
  • wait for Support python 3.11 catboost/catboost#2213
• chainer.yml Add python 3.11 to a part of CI jobs #163
• checks.yml: fixed python 3.8
• dashboard.yml
• dask.yml Add python 3.11 to a part of CI jobs #163
• dask_ml.yml
  • blocked by numba
• fastai.yml
  • blocked by pytorch
• haiku.yml
  • blocked by tensorflow
• hiplot.yml Add python 3.11 to a part of CI jobs #163
• hydra.yml Add python 3.11 to version-matrix except for integration #160
• keras.yml
  • blocked by tensorflow
• lightgbm.yml
  • possibly not. https://github.com/microsoft/LightGBM/blob/master/.github/workflows/python_package.yml
• mlflow.yml
  • blocked by numba
• multi_objective.yml
  • blocked by pytorch
• mxnet.yml
  • it doesn't work at least my local env.
• pytorch.yml
  • wait for Support Python 3.11 pytorch/pytorch#86566
• ray.yml
  • Add python 3.11 to ray's version matrix #174
• rl.yml
  • blocked by pytorch
• samplers.yml: Add python 3.11 to version-matrix except for integration #160
• skimage.yml
  • wait for Python 3.11 wheels scikit-image/scikit-image#6517
• sklearn.yml Add python 3.11 to a part of CI jobs #163
• stale.yml fixed python 3.8
• tensorboard.yml
  • blocked by tensorflow
• tensorflow.yml
  • wait for Support Python 3.11 tensorflow/tensorflow#58032
• tfkeras.yml
  • blocked by tensorflow
• visualization.yml: Add python 3.11 to version-matrix except for integration #160
• wandb.yml: Add python 3.11 to a part of CI jobs #163
• xgboost.yml Add python 3.11 to a part of CI jobs #163

[Kaushik-Iyer]

Are all of them done?

[nzw0301]

@Kaushik-Iyer As in the issue description, we need to wait for third party libraries' python 3.11 support.

[github-actions]

This issue has not seen any recent activity.

[github-actions]

This issue has not seen any recent activity.

[hvy]

tensorflow now supports 3.11, see optuna/optuna#3964 (comment)

All examples blocked by tensorflow might be worth revisiting. While I haven't checked for possible errors, please let me mark this issue as contribution welcome for others to try picking it up. Please let me know if there are uncertainties.

[github-actions]

This issue has not seen any recent activity.

[github-actions]

This issue has not seen any recent activity.

[Alnusjaponica]

It seems Python 3.11 is now supported by tensorflow. See tensorflow/tensorflow#58032 for more detail.

[Alnusjaponica]

Same as PyTorch(pytorch/pytorch#86566) and Numba (numba/numba#8304)

[github-actions]

This issue has not seen any recent activity.

[Alnusjaponica]

It seems the development of MXNet has stopped before the release of python 3.11 and the test does not pass.
Therefore, it will be enough to close this issue after #214 is merged.

[Alnusjaponica]

It is possible to run MXNet tests in Python 3.11, but it is necessary to install Numpy<1.24.0. To add to the Python 3.11 job to MXNet CI, reversing the order of the dependency list in mxnet/requirements.txt suffices. This is because Numpy>=1.24.0 is actually installed before running pip install -r requirements.txt in the CI, and it is necessary to reinstall Numpy<1.24.0 before the CI installs MXNet. For more details, please refer to Alnusjaponica#1.

[github-actions]

This issue has not seen any recent activity.

[nzw0301]

FYI: MXNet has been archived since 18 Nov. 2023, so the incompatibility with numpy will not be addressed anymore on the MXNet side.

[github-actions]

This issue has not seen any recent activity.

[not522]

All except MXNet have been supported, and MXNet has finished development. Therefore, Python 3.11 support is considered complete. Thank you for your contributions!