Skip to content
New issue

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

DM-37987: Update to support python 3.11 #145

Merged
merged 6 commits into from Feb 27, 2023
Merged

DM-37987: Update to support python 3.11 #145

merged 6 commits into from Feb 27, 2023

Conversation

timj
Copy link
Member

@timj timj commented Feb 13, 2023

Checklist

  • ran Jenkins
  • added a release note for user-visible changes to doc/changes

@codecov
Copy link

codecov bot commented Feb 13, 2023

Codecov Report

Base: 92.38% // Head: 92.42% // Increases project coverage by +0.04% 🎉

Coverage data is based on head (be22c41) compared to base (097e31a).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #145      +/-   ##
==========================================
+ Coverage   92.38%   92.42%   +0.04%     
==========================================
  Files          41       41              
  Lines        2638     2654      +16     
==========================================
+ Hits         2437     2453      +16     
  Misses        201      201              
Impacted Files Coverage Δ
python/lsst/utils/logging.py 90.99% <100.00%> (+1.40%) ⬆️
tests/test_logging.py 98.85% <100.00%> (+0.01%) ⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

python/lsst/utils/logging.py Outdated Show resolved Hide resolved
python/lsst/utils/logging.py Outdated Show resolved Hide resolved
python/lsst/utils/logging.py Show resolved Hide resolved
Python 3.11 no longer needs you to understand internal
logging call stacks that are involved -- stacklevel=1
always now means the caller of the logging method.
Previously you could not ask for stacklevel=2 and expect your
caller file to be used in the log message.
python/lsst/utils/logging.py Outdated Show resolved Hide resolved
Now only used in one place so can check the python version
directly.
@timj timj merged commit 0b64b56 into main Feb 27, 2023
@timj timj deleted the tickets/DM-37987 branch February 27, 2023 21:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants