This release is a pre-release and may not be stable for production use.
Keras 3: A new multi-backend Keras
Keras 3 is a new multi-backend implementation of the Keras API, with support for TensorFlow, JAX, and PyTorch.
Installation
Install with pip
Keras 3 is available on PyPI as keras. Note that Keras 2 remains available as the tf-keras package.
- Install
keras:
pip install keras --upgrade
- Install backend package(s).
To use keras, you should also install the backend of choice: tensorflow, jax, or torch.
Note that tensorflow is required for using certain Keras 3 features: certain preprocessing layers
as well as tf.data pipelines.
Local installation
Minimal installation
Keras 3 is compatible with Linux and MacOS systems. For Windows users, we recommend using WSL2 to run Keras. To install a local development version:
- Install dependencies:
pip install -r requirements.txt
- Run installation command from the root directory.
python pip_build.py --install
Adding GPU support
The requirements.txt file will install a CPU-only version of TensorFlow, JAX, and PyTorch. For GPU support, we also
provide a separate requirements-{backend}-cuda.txt for TensorFlow, JAX, and PyTorch. These install all CUDA
dependencies via pip and expect a NVIDIA driver to be pre-installed. We recommend a clean python environment for each
backend to avoid CUDA version mismatches. As an example, here is how to create a Jax GPU environment with conda:
conda create -y -n keras-jax python=3.10
conda activate keras-jax
pip install -r requirements-jax-cuda.txt
python pip_build.py --install
Configuring your backend
You can export the environment variable KERAS_BACKEND or you can edit your local config file at ~/.keras/keras.json
to configure your backend. Available backend options are: "tensorflow", "jax", "torch". Example:
export KERAS_BACKEND="jax"
In Colab, you can do:
import os
os.environ["KERAS_BACKEND"] = "jax"
import keras
Note: The backend must be configured before importing keras, and the backend cannot be changed after
the package has been imported.
Backwards compatibility
Keras 3 is intended to work as a drop-in replacement for tf.keras (when using the TensorFlow backend). Just take your
existing tf.keras code, make sure that your calls to model.save() are using the up-to-date .keras format, and you're
done.
If your tf.keras model does not include custom components, you can start running it on top of JAX or PyTorch immediately.
If it does include custom components (e.g. custom layers or a custom train_step()), it is usually possible to convert it
to a backend-agnostic implementation in just a few minutes.
In addition, Keras models can consume datasets in any format, regardless of the backend you're using:
you can train your models with your existing tf.data.Dataset pipelines or PyTorch DataLoaders.
Why use Keras 3?
- Run your high-level Keras workflows on top of any framework -- benefiting at will from the advantages of each framework, e.g. the scalability and performance of JAX or the production ecosystem options of TensorFlow.
- Write custom components (e.g. layers, models, metrics) that you can use in low-level workflows in any framework.
- You can take a Keras model and train it in a training loop written from scratch in native TF, JAX, or PyTorch.
- You can take a Keras model and use it as part of a PyTorch-native
Moduleor as part of a JAX-native model function.
- Make your ML code future-proof by avoiding framework lock-in.
- As a PyTorch user: get access to power and usability of Keras, at last!
- As a JAX user: get access to a fully-featured, battle-tested, well-documented modeling and training library.
Read more in the Keras 3 release announcement.
4 maintainers
Metadata
4 maintainers
Release files for keras-nightly 3.0.3.dev2024010703
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| keras-nightly-3.0.3.dev2024010703.tar.gz | 737.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| keras_nightly-3.0.3.dev2024010703-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.8 MB
Release files / keras-nightly-3.0.3.dev2024010703.tar.gz
| Download URL | keras-nightly-3.0.3.dev2024010703.tar.gz |
|---|---|
| Size | 737.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e3716f48ec095916ac0e4bf7f807af7a4219bee290aa57cf8a0cdbc397b65814
|
|
BLAKE2b-256 checksum How to use checksums |
be79bc40f138941b5f3933ed8ff758435f33204ff9b0d49cd0cfc0449336d051
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.7
|
Release files / keras_nightly-3.0.3.dev2024010703-py3-none-any.whl
| Download URL | keras_nightly-3.0.3.dev2024010703-py3-none-any.whl |
|---|---|
| Size | 1.0 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5e7c0284a5d084b1331b585efe220beb484068951bdd457505ef2f4e66ee05d2
|
|
BLAKE2b-256 checksum How to use checksums |
501e02229a00da8dfde4da814c5e7a68cb5bc201df164fa2487725e62a24f1e7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.7
|
Security for keras-nightly 3.0.3.dev2024010703
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
