-
Notifications
You must be signed in to change notification settings - Fork 28
Populate correct meta information in load_file, deprecate taking file objects #310
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
Open
tmadlener
wants to merge
8
commits into
key4hep:main
Choose a base branch
from
tmadlener:fix-file-dunder-load-file
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
78682e2
to
509295d
Compare
closing and opening again to check if that triggers CI |
tmadlener
commented
Apr 30, 2025
421636d
to
d23279d
Compare
74b8360
to
3037db5
Compare
tmadlener
commented
Jun 6, 2025
Comment on lines
+105
to
+108
warnings.warn( | ||
"load_file will remove support for handling TextIOWrapper. Please switch to pasing os.PathLike", | ||
FutureWarning, | ||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure this is used anywhere. It might be possible to remove this entirely and clean the implementation up a bit more.
Only possible if we still have access to the path. If we don't inject this than files that use __file__ will always show up as coming from utils.py >>> print(__file__) >>> <k4fwcore-prefix>/python/k4FWCore/utils.py
Deprecate handling a filehandle
3037db5
to
0d371f9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
BEGINRELEASENOTES
load_file
sets the correct__file__
and__spec__
information for files that are loaded with itload_file
and always pass a path-like objectENDRELEASENOTES
Setting the correct
__file__
is necessary as that is quite frequently used for some special casing, or also to add things tosys.path
relative to the path of the loaded file, e.g. herePutting out the correct file name was lost in #213
Finally it looks like a simple change in
k4run
makes it trivial to pass in path-like objects rather than open file handles (which we didn't bother to close before).