None of those are public APIs so it probably just wasn't a big concern. Pyramid's source in general is entirely flat aside from the config subpackage. Scaffolds and scripts are things you would never import in your own code.
On Wed, Mar 27, 2013 at 12:44 PM, Jonathan Vanasco <jonat...@findmeon.com>wrote: > looking at the source, I see: > > * pyramid/chamelon_text.py > * pyramid/chamelon_zpt.py > * pyramid/mako_templating.py > > was there any reason for these being on the top-level, and not under a > consolidated namespace like pyramid/templating , or did this just > happen randomly ? > > -- > You received this message because you are subscribed to the Google Groups > "pylons-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to pylons-devel+unsubscr...@googlegroups.com. > To post to this group, send email to pylons-devel@googlegroups.com. > Visit this group at http://groups.google.com/group/pylons-devel?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-devel+unsubscr...@googlegroups.com. To post to this group, send email to pylons-devel@googlegroups.com. Visit this group at http://groups.google.com/group/pylons-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
