trac.log: dead code - logger_factory()

[anatoly techtonik <techtonik@…>]

This code is not referenced from anywhere. It is dead and can be removed - source:/branches/0.12-stable/trac/log.py@10847:67-70#L64​

[Remy Blank]

Right about now Simon should jump out of nowhere and claim that ~800 plugins rely on that function ;)

[Remy Blank]

(And enhancements go to 0.13.)

[Christian Boos]

Replying to rblank:

Right about now Simon should jump out of nowhere and claim that ~800 plugins rely on that function ;)

He he ;-)

But that was the plan, so it's fine (#9918).

[anatoly techtonik <techtonik@…>]

Right about now Simon should jump out of nowhere and claim that ~800 plugins rely on that function ;)

He he ;-)

But that was the plan, so it's fine (#9918).

Is there objective stats on those ~800 plugins? Online grep interface? =)

[osimons]

BTW, I'm not making that number up…

$> svn ls http://trac-hacks.org/svn/ | wc -l
782

And I know plenty of other plugins (including some of mine) that are not published on Trac-Hacks.

Anyway, it was all just meant as a pointer to the fact that there is a lot of legacy code out there that depend on Trac internals… The dead code is likely a left-over of some deprecated call-behaviour, and I cannot see that any of those plugins will still be working with recent Trac versions anyway - not with the current eagerness to break APIs and move things around to suit Trac internals… ;-)

[Christian Boos]

I wonder if we couldn't add a trac/compat.py module where we could easily move all the old code… something like:

from trac import log

def logger_factory(logtype='syslog', logfile=None, level='WARNING',
                   logid='Trac', format=None):
    return log.logger_handler_factory(logtype, logfile, level, logid, format)[0]

log.logger_factory = logger_factory

That way, people could get a cheap way to keep their plugin working, and it would also serve as a way to document what has changed for those who want to adapt their code. That would help to keep the rest of the codebase clean, yet give a safety net for plugins. Of course, this will only work to compensate for removed functions or methods, not for signature changes, but that would still be something.

[osimons]

We already have trac.util.compat, but in this case it makes more sense just to remove the code. There is no actual behavior change or code removal, it is just another way calling the same code. If you need to update to import from other module, it should not require much more effort just to change your call syntax instead.

+1 for removing in trunk, no compat.

[Remy Blank]

Nuked in [11061].