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
Replace import * when modules are imported only to be cloned #17153
Replace import * when modules are imported only to be cloned #17153
Conversation
A new Pull Request was created by @wddgit (W. David Dagenhart) for CMSSW_9_0_X. It involves the following packages: PhysicsTools/PatAlgos @cmsbuild, @cvuosalo, @slava77, @monttj, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here #13028 |
@@ -1,14 +1,14 @@ | |||
import FWCore.ParameterSet.Config as cms | |||
|
|||
from CommonTools.ParticleFlow.Isolation.electronPFIsolationDepositsPFBRECO_cff import * | |||
import CommonTools.ParticleFlow.Isolation.electronPFIsolationDepositsPFBRECO_cff as m |
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.
should this better be as _m
so that someplace else with electronPFIsolationDepositsPAT_cff import *
doesn't end up with a rogue m
?
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.
Yes. I agree that would be better. I will update the PR soon.
What I did was enough to keep unwanted things out of the Process object and the list of unscheduled modules. But you are right, the "m" symbol would show up in the symbol table of the importing modules, which is unnecessary and could cause problems if anyone tried to use it because of conflicts.
I updated the PR with the change from m to _m suggested by Slava. I do not know why, but I did not see the email I usually see after updating a PR, but it should be ready to be tested now. |
@cmsbuild please test @smuzaffar is this the normal behavior of the bot (to send no messages on a PR that had no other state changes like no tests were started and no labels were modified yet, but there was a new commit) |
The tests are being triggered in jenkins. |
@slava77 , no it is not a normal behavior. This only happens when there is no comment between new commit the time when bot had recognized the PR. |
Comparison job queued. |
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_9_0_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @smuzaffar |
No description provided.