On Mon, 2010-09-20 at 14:58 -0700, Mike Orr wrote: > > > > AFAIK, Ben doesn't want to do that. He wants all the docs presented in > > terms of Pylons, not punting to the BFG docs for anything at all. > > BFG is bigger than all the other Pylons dependencies combined. We > can't have 30% of the Pylons manual referring to BFG features that > aren't normally used in Pylons apps, especially if Pylons has a more > specific way to enable it.
I don't really know the subset of BFG APIs that Ben wants pointed at by a Pylons facade. But whether it be 5% of BFG or 95%, that subset will likely need its own documentation, so the problem really is the same. > It sounds like we need a preprocessor to import documentation sources > and sanitize foreign cross-references. Can that be done as a Sphinx > plugin? Nobody knows without spending the time. - C -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-de...@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
