Pyramid is repoze.bfg with some of the good things from Pylons added in. Pyramid is much more extensible with hooks. TurboGears will still be a full-stack, Pyramid + their choices for form library, templating, etc. Pyramid is still very light and makes very few assumptions.
I think it is better since you've brought together three frameworks and that collective mindshare is going to collaborate rather than compete.
Spend some time reading the pyramid docs - it it totally agnostic for template engines, authentication/authorization, http session implementation, etc. very pluggable.
I will say though, that at this point 1.0alpha8, a noob will probably get frustrated, but someone who has worked with pylons / repoze / sqlalchemy can connect the dots.
Also, with every alpha release, you can also see the changes to the documentation, which is looking more like django docs (i.e. good)
Django fills a certain niche and if it matches your problem, it is a no brainer. If you need a more flexible web framework, look at pyramid.
This blog post seems to indicate that Pylons is going more in the direction of most frameworks with its talk of "full stack" and choosing defaults. Is Pylons going to become a reimplementation of Django? It's a little weird. I don't know why Pylons thinks this is better as a single project.