Re: question about design decision on pyramid's core
I don't know officially, but Chameleon was added a lot earlier and the code may be inherited from BFG. Mako was added for the Pylons integration because Chameleon would have been too big a change for them. At the time it was thought that these would be the built-in template engines and others would be third-party. Since then mcdonc has talked about spinning those off too, as pyramid_chameleon and pyramid_mako, but that hasn't happened yet. On Wed, Mar 27, 2013 at 10:44 AM, 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/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. > > > -- Mike Orr -- 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.
Re: question about design decision on pyramid's core
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/templating , or did this just > happen randomly ? > > >>> import this See 5th rule. Chris -- 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.
Re: question about design decision on pyramid's core
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 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.
Re: question about design decision on pyramid's core
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 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.
Re: question about design decision on pyramid's core
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 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.
Re: question about design decision on pyramid's core
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 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.