Answered by:
Cannot import azureml.pipeline.steps 1.1.5 on Python 3.8.2 AMD64

Question
-
Works in other versions of Python.
Python 3.8.2 (tags/v3.8.2:7b3ab59, Feb 25 2020, 23:03:10) [MSC v.1916 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import azureml.pipeline.steps
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "C:\Users\vassilyl\.python_venv\one.azureml.38\lib\site-packages\azureml\pipeline\steps\__init__.py", line 26, in <module>
from .automl_step import AutoMLStep, AutoMLStepRun
File "C:\Users\vassilyl\.python_venv\one.azureml.38\lib\site-packages\azureml\pipeline\steps\automl_step.py", line 11, in <module>
from azureml.automl.core import dataprep_utilities, dataset_utilities
File "C:\Users\vassilyl\.python_venv\one.azureml.38\lib\site-packages\azureml\automl\__init__.py", line 5, in <module>
import azureml.automl.core
File "C:\Users\vassilyl\.python_venv\one.azureml.38\lib\site-packages\azureml\automl\core\__init__.py", line 16, in <module>
_handle_legacy_shared_package_imports()
File "C:\Users\vassilyl\.python_venv\one.azureml.38\lib\site-packages\azureml\automl\core\_shared_package_legacy_import.py",
line 80, in _handle_legacy_shared_package_imports
_import_all_legacy_submodules(
File "C:\Users\vassilyl\.python_venv\one.azureml.38\lib\site-packages\azureml\automl\core\_shared_package_legacy_import.py",
line 105, in _import_all_legacy_submodules
module = pkgutil.importlib.import_module(curr_package.__name__ + '.' + name)
File "C:\Users\vassilyl\AppData\Local\Programs\Python\Python38\lib\importlib\__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "C:\Users\vassilyl\.python_venv\one.azureml.38\lib\site-packages\azureml\automl\core\shared\win32_helper.py", line 675,
in <module>
Win32Helper = _Win32Helper()
File "C:\Users\vassilyl\.python_venv\one.azureml.38\lib\site-packages\azureml\automl\core\shared\win32_helper.py", line 228,
in __init__
self.assign_process_to_job_object(self.job_object)
File "C:\Users\vassilyl\.python_venv\one.azureml.38\lib\site-packages\azureml\automl\core\shared\win32_helper.py", line 359,
in assign_process_to_job_object
raise self.get_error('AssignProcessToJobObject')
azureml.automl.core.shared.win32_helper.Win32Exception: Win32Exception:
Message: Win32 AssignProcessToJobObject API call failed: [WinError 6] The handle is invalid.
InnerException None
ErrorResponse
{
"error": {
"code": "System",
"inner_error": {
"code": "Os"
},
"message": "Win32 AssignProcessToJobObject API call failed: [WinError 6] The handle is invalid."
}
}
>>>---
>pip show azureml-pipeline-steps
Name: azureml-pipeline-steps
Version: 1.1.5...
Friday, March 13, 2020 8:27 AM
Answers
-
Hi,
This appears to be a bug; the product team is working on a resolution. Thanks.
Regards,
GiftA-MSFT.
If a post helps to resolve your issue, please click “Mark as Answer” and/or “Vote as helpful”. By marking a post as Answered and/or Helpful, you help others find the answer faster. Thanks.
- Proposed as answer by RohitMungi-MSFTMicrosoft employee Friday, April 3, 2020 6:51 AM
- Marked as answer by VassilyL Friday, April 3, 2020 12:29 PM
Wednesday, March 18, 2020 6:32 AM
All replies
-
Hi,
Thanks for reaching out. We will forward this feedback to the product team team and share updates as soon as we have more information. Thanks.
Regards,
GiftA-MSFT.
If a post helps to resolve your issue, please click “Mark as Answer” and/or “Vote as helpful”. By marking a post as Answered and/or Helpful, you help others find the answer faster. Thanks.
Saturday, March 14, 2020 1:04 AM -
Hi,
This appears to be a bug; the product team is working on a resolution. Thanks.
Regards,
GiftA-MSFT.
If a post helps to resolve your issue, please click “Mark as Answer” and/or “Vote as helpful”. By marking a post as Answered and/or Helpful, you help others find the answer faster. Thanks.
- Proposed as answer by RohitMungi-MSFTMicrosoft employee Friday, April 3, 2020 6:51 AM
- Marked as answer by VassilyL Friday, April 3, 2020 12:29 PM
Wednesday, March 18, 2020 6:32 AM -
Does not reproduce in v1.5 anymoreThursday, May 21, 2020 1:26 PM