Skip to content

Commit 230949f

Browse files
authored
Merge pull request #229019 from harneetvirk/main
Announcement for end of support for Python 3.7 for sdkv1
2 parents d74211e + 58423d9 commit 230949f

File tree

1 file changed

+41
-29
lines changed

1 file changed

+41
-29
lines changed

articles/machine-learning/v1/azure-machine-learning-release-notes.md

Lines changed: 41 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -20,42 +20,54 @@ __RSS feed__: Get notified when this page is updated by copying and pasting the
2020
`https://learn.microsoft.com/api/search/rss?search=%22Azure+machine+learning+release+notes%22&locale=en-us`
2121

2222

23-
## 2023-13-02
23+
## 2023-03-01
24+
25+
### Announcing end of support for Python 3.7 in Azure Machine Learning SDK v1 packages
2426

27+
+ **Feature deprecation**
28+
+ **Deprecate Python 3.7 as a supported runtime for SDK v1 packages**
29+
+ On December 4, 2023, Azure Machine Learning will officially stop supporting Python 3.7 for SDK v1 packages and deprecate it as a supported runtime. For more details, please read our page on [Azure SDK for Python version support policy](https://github.com/Azure/azure-sdk-for-python/wiki/Azure-SDKs-Python-version-support-policy)
30+
+ As of the deprecation date of December 4, 2023, the Azure Machine Learning SDK v1 packages will no longer receive security patches and other updates for the Python 3.7 runtime.
31+
+ The current Python 3.7 versions for Azure Machine Learning SDK v1 will still function. However, in order to continue receiving security updates and remaining qualified for technical assistance, Azure Machine Learning strongly advises that you move your scripts and dependencies to a supported version of the Python runtime.
32+
+ As a runtime for Azure Machine Learning SDK v1 files, we advise using Python version 3.8 or later.
33+
+ Additionally, Python 3.7 based Azure Machine Learning SDK v1 packages will no longer be qualified for technical assistance.
34+
+ Use Azure Machine Learning support to get in touch with us if you have any concerns.
35+
36+
## 2023-13-02
2537

2638
### Azure Machine Learning SDK for Python v1.49.0
2739
+ **Breaking changes**
2840
+ Starting with v1.49.0 and above, the following AutoML algorithms will not be supported.
29-
+ Regression: FastLinearRegressor, OnlineGradientDescentRegressor
30-
+ Classification: AveragedPerceptronClassifier.
41+
+ Regression: FastLinearRegressor, OnlineGradientDescentRegressor
42+
+ Classification: AveragedPerceptronClassifier.
3143
+ Use v1.48.0 or below to continue using these algorithms.
3244
+ **Bug fixes and improvements**
33-
+ **azureml-automl-dnn-nlp**
34-
+ Logs to show the final values applied to the model and hyperparameter settings based on both the default values and the user-specified ones.
35-
+ **azureml-contrib-automl-dnn-forecasting**
36-
+ Nonscalar metrics for TCNForecaster will now reflect values from the last epoch.
37-
+ Forecast horizon visuals for train-set and test-set are now available while running the TCN training experiment.
38-
+ Runs will not fail anymore because of "Failed to calculate TCN metrics" error. The warning message that says "Forecast Metric calculation resulted in error, reporting back worst scores" will still be logged. Instead we raise exception when we face inf/nan validation loss for more than two times consecutively with a message "Invalid Model, TCN training did not converge.". The customers need be aware of the fact that loaded models may return nan/inf values as predictions while inferencing after this change.
39-
+ **azureml-core**
40-
+ Azure Machine Learning workspace creation makes use of Log Analytics Based Application Insights in preparation for deprecation of Classic Application Insights. Users wishing to use Classic Application Insights resources can still specify their own to bring when creating an Azure Machine Learning workspace.
41-
+ **azureml-interpret**
42-
+ updated azureml-interpret package to interpret-community 0.28.*
43-
+ **azureml-mlflow**
44-
+ Updating azureml-mlflow client with initial support for MLflow 2.0
45-
+ **azureml-responsibleai**
46-
+ updated azureml-responsibleai package and notebooks to raiwidgets and responsibleai v0.24.0
47-
+ **azureml-sdk**
48-
+ azureml-sdk and azureml-train-automl-client now support Python version 3.10
49-
+ **azureml-train-automl-client**
50-
+ azureml-sdk and azureml-train-automl-client now support Python version 3.10
51-
+ **azureml-train-automl-runtime**
52-
+ Clean up missing y before training
53-
+ Clean up nan or empty values of target column for non-streaming scenarios
54-
+ Forecast horizon visuals for test-set are now available while running the training experiment.
55-
+ **azureml-train-core**
56-
+ Added the support to customer to provide custom run id for hyperdrive runs
57-
+ **azureml-train-restclients-hyperdrive**
58-
+ Added the support to customer to provide custom run id for hyperdrive runs
45+
+ **azureml-automl-dnn-nlp**
46+
+ Logs to show the final values applied to the model and hyperparameter settings based on both the default values and the user-specified ones.
47+
+ **azureml-contrib-automl-dnn-forecasting**
48+
+ Nonscalar metrics for TCNForecaster will now reflect values from the last epoch.
49+
+ Forecast horizon visuals for train-set and test-set are now available while running the TCN training experiment.
50+
+ Runs will not fail anymore because of "Failed to calculate TCN metrics" error. The warning message that says "Forecast Metric calculation resulted in error, reporting back worst scores" will still be logged. Instead we raise exception when we face inf/nan validation loss for more than two times consecutively with a message "Invalid Model, TCN training did not converge.". The customers need be aware of the fact that loaded models may return nan/inf values as predictions while inferencing after this change.
51+
+ **azureml-core**
52+
+ Azure Machine Learning workspace creation makes use of Log Analytics Based Application Insights in preparation for deprecation of Classic Application Insights. Users wishing to use Classic Application Insights resources can still specify their own to bring when creating an Azure Machine Learning workspace.
53+
+ **azureml-interpret**
54+
+ updated azureml-interpret package to interpret-community 0.28.*
55+
+ **azureml-mlflow**
56+
+ Updating azureml-mlflow client with initial support for MLflow 2.0
57+
+ **azureml-responsibleai**
58+
+ updated azureml-responsibleai package and notebooks to raiwidgets and responsibleai v0.24.0
59+
+ **azureml-sdk**
60+
+ azureml-sdk and azureml-train-automl-client now support Python version 3.10
61+
+ **azureml-train-automl-client**
62+
+ azureml-sdk and azureml-train-automl-client now support Python version 3.10
63+
+ **azureml-train-automl-runtime**
64+
+ Clean up missing y before training
65+
+ Clean up nan or empty values of target column for non-streaming scenarios
66+
+ Forecast horizon visuals for test-set are now available while running the training experiment.
67+
+ **azureml-train-core**
68+
+ Added the support to customer to provide custom run id for hyperdrive runs
69+
+ **azureml-train-restclients-hyperdrive**
70+
+ Added the support to customer to provide custom run id for hyperdrive runs
5971

6072
## 2022-12-05
6173

0 commit comments

Comments
 (0)