We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
print
Doing a quick search for print( in tests/ returns more than 700 instances of printing in tests, e.g. as seen here:
print(
tests/
rucio/tests/test_replica_recoverer.py
Lines 206 to 217 in 767dbc5
Printing is useful for debugging, but once a test has been written and has the proper assertions, print statements should likely be removed.
print affects performance, as tested here: https://stackoverflow.com/questions/13288185/performance-effect-of-using-print-statements-in-python-script - we might be able to gain some performance in test speed by removing these calls.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Doing a quick search for
print(
intests/
returns more than 700 instances of printing in tests, e.g. as seen here:rucio/tests/test_replica_recoverer.py
Lines 206 to 217 in 767dbc5
Printing is useful for debugging, but once a test has been written and has the proper assertions, print statements should likely be removed.
print
affects performance, as tested here: https://stackoverflow.com/questions/13288185/performance-effect-of-using-print-statements-in-python-script - we might be able to gain some performance in test speed by removing these calls.The text was updated successfully, but these errors were encountered: