Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update {keras} -> {keras3} transition plans #229

Merged
merged 1 commit into from
May 29, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 3 additions & 9 deletions _posts/2024-05-21-keras3/introducing-keras3.Rmd
Original file line number Diff line number Diff line change
@@ -277,7 +277,7 @@ for example usage.

### Migrating from `{keras}` to `{keras3}`

`{keras3}` is ultimately a preview of the future `{keras}` package.
`{keras3}` supersedes the `{keras}` package.

If you're writing new code today, you can start using `{keras3}` right
away.
@@ -297,14 +297,8 @@ hesitate to ask on <https://github.com/rstudio/keras/issues> or
The `{keras}` and `{keras3}` packages will coexist while the community
transitions. During the transition, `{keras}` will continue to receive
patch updates for compatibility with Keras v2, which continues to be
published to PyPi under the package name `tf-keras`.

`{keras3}` is intended as a transition package name. In a future update,
the `{keras}` package will begin emitting a package startup message,
announcing a deprecation period. After a notice period in the `{keras}`
package, `{keras3}` will be renamed to `{keras}`. At that time `{keras}`
(v2) will no longer be supported, and `{keras3}` will be an alias for
`{keras}`.
published to PyPi under the package name `tf-keras`. After `tf-keras` is
no longer maintained, the `{keras}` package will be archived.

## Summary