# It’s written in Python, a language I currently don’t know nor have a (current) inclination to learn. - That's not a real reason, but Python is cool, give it a try.

# It doesn’t do git without a plugin. - So what? A lot of open source software extends with plugins and that's a good thing.

# How do I get email notifications when something’s changed in the wiki? - Never tried to do that but you can use RSS.

# How do I get email notifications when code changes are uploaded? - Again never tried to do that, trac is not a SCM tool... but all modern SCMs have an option to send an e-mail upon a commit (even the good old cvs).

# Each project you want to manage with it gets its own separate install, which is very klunky. You have to log into each one separately (unless you set up a shared authentication system of some sort in the web server). - Yes that's something that trac doesn't do too good, but you can overcome it. Like use the same SVN repository for all your projects and just use the component field to indicate the project and you can create a new field call sub-components for a good drilldown... still not perfect but doable.

Even if you use a separate install for each project you can use a plugin to quickly switch between projects (if they all sit under the same directory) because authentication is shared there is no problem and you can still use the same SVN repository for all the projects.
If your layout is {project_name}/trunk it's easy, the url will point directly to the project. If it's trunk/{project_name} you can use directory based authorization to limit the access to the other projects.

# No task associations so you can’t do a parent-child dependency to indicate a completion hierarchy - There is a plugin to do it.

Again Trac isn't perfect but it DOESN'T SUCK!