From 4299b9f5173c08d9e30630ba0543fc700fe60d78 Mon Sep 17 00:00:00 2001 From: Aleksey Veresov Date: Tue, 30 Sep 2025 13:30:57 +0200 Subject: [PATCH] Fix the incorrect statement about hsfs and hsml packages --- docs/user_guides/migration/40_migration.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/user_guides/migration/40_migration.md b/docs/user_guides/migration/40_migration.md index cbba2b44f..596c87c7e 100644 --- a/docs/user_guides/migration/40_migration.md +++ b/docs/user_guides/migration/40_migration.md @@ -19,11 +19,11 @@ A number of significant changes have been made in the Python API Hopsworks 4.0. Previously, in Hopsworks 3.X, there were 3 python libraries used (“hopsworks”, “hsfs” & “hsml”) to develop feature, training & inference pipelines, with the 4.0 release there is now -one single “hopsworks” python library that can should be used. For -backwards compatibility, it will still be possible to import both -the “hsfs” & “hsml” libraries but these are now effectively aliases -to the “hopsworks” python library and their use going forward should -be considered as deprecated. +one single “hopsworks” python library that should be used. For +backwards compatibility, it is still possible to import both +the “hsfs” & “hsml” packages directly, but the proper way to +import them is to use “hopsworks.hsfs” & “hopsworks.hsml”. +The direct imports will be deprecated later. Another significant change in the Hopsworks Python API is the use of optional extras to allow a developer to easily import exactly what is