You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Logging to stdout is an undesirable default for a library, especially since tools that use the library will want to control what is written to stdout. For example, imagine a command line program that fetches records from FeatureStore or metadata about training runs and writes the data to stdout so that it can be parsed by other tools like grep or jq or awk.
>>> import sagemaker
sagemaker.config INFO - Not applying SDK defaults from location: /etc/xdg/sagemaker/config.yaml
sagemaker.config INFO - Not applying SDK defaults from location: /home/username/.config/sagemaker/config.yaml
Expected behavior
I would expect this to be written to stderr so that it doesn't interfere with regular program output.
Screenshots or logs
If applicable, add screenshots or logs to help explain your problem.
System information
A description of your system. Please provide:
SageMaker Python SDK version: '2.198.0'
Framework name (eg. PyTorch) or algorithm (eg. KMeans): N/A
Framework version: N/A
Python version: 3.8
CPU or GPU: Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz
Custom Docker image (Y/N): N
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
import logging
# have to do this before importing sagemaker otherwise it logs
# config info to stdout
logging.getLogger("sagemaker.config").addHandler(logging.NullHandler())
logging.getLogger("sagemaker").addHandler(logging.NullHandler())
import sagemaker
Describe the bug
Logging to stdout is an undesirable default for a library, especially since tools that use the library will want to control what is written to stdout. For example, imagine a command line program that fetches records from FeatureStore or metadata about training runs and writes the data to stdout so that it can be parsed by other tools like
grep
orjq
orawk
.This is most likely caused by this line.
To reproduce
This writes to
stdout
:Expected behavior
I would expect this to be written to
stderr
so that it doesn't interfere with regular program output.Screenshots or logs
If applicable, add screenshots or logs to help explain your problem.
System information
A description of your system. Please provide:
'2.198.0'
3.8
Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: