Move overrides for registrations to debug
Review Request #2023 - Created April 2, 2015 and submitted
|areitz, patricklaw, zundel|
Move overrides for registrations to debug.
These are only useful at INFO if you're worried about accidentally overwriting existing aliases... but even in that case, it's unlikely for overwriting two similar-named but differently-typed to "just work". You kind of have to do it intentionally.
Internally we're overriding both
jar... I'd like to upstream the latter soon, but the former has a lot of deps that can't be upstreamed.
I'm concerned that the info messages could be of utility if someone is doing this accidentally. Could there be an override=True or something like that on the second registration where we could indicate that we expect an alias to already exist?