question about design decision on pyramid's core

2013-03-27 Thread Jonathan Vanasco
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 messag

Re: question about design decision on pyramid's core

2013-03-27 Thread Michael Merickel
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 wrote: > looking at

Re: question about design decision on pyramid's core

2013-03-27 Thread Jonathan Vanasco
thanks. makes sense. i'm just trying to reverse engineer some templating flowthroughs. most other things were logically grouped together. -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To unsubscribe from this group and stop receiving emails f

optimizing whitespace in mako templates

2013-03-27 Thread Jonathan Vanasco
I've been working on a method to optimize whitespace with Mako templates -- instead of collapsing insignificant whitespace after Pyramid renders the view_callable, it's stripped when Mako first compiles the template. I'm trying to figure out the best way to integrate this with Pyramid. At first I

Re: question about design decision on pyramid's core

2013-03-27 Thread Blaise Laflamme
you're about t reverse-engineer mcdonc's brain... be careful ;) On Wednesday, 27 March 2013 14:10:42 UTC-4, Jonathan Vanasco wrote: > > thanks. makes sense. > > i'm just trying to reverse engineer some templating flowthroughs. > most other things were logically grouped together. > -- You rec

Re: question about design decision on pyramid's core

2013-03-27 Thread Jonathan Vanasco
On Mar 27, 4:33 pm, Blaise Laflamme wrote: > you're about t reverse-engineer mcdonc's brain... be careful ;) ha! i just needed to figure out the mako integration , which was pretty straightforward ( see the other thread ). -- You received this message because you are subscribed to the Google

Re: question about design decision on pyramid's core

2013-03-27 Thread Chris Rossi
On Wed, Mar 27, 2013 at 1:44 PM, Jonathan Vanasco 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/templa