question about design decision on pyramid's core

Jonathan Vanasco

unread,

Mar 27, 2013, 1:44:49 PM3/27/13

to pylons-devel

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 ?

Michael Merickel

unread,

Mar 27, 2013, 2:05:27 PM3/27/13

to pylons-devel

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.

--
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...@googlegroups.com.
To post to this group, send email to pylons...@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.

Jonathan Vanasco

unread,

Mar 27, 2013, 2:10:42 PM3/27/13

to pylons-devel

thanks. makes sense.

i'm just trying to reverse engineer some templating flowthroughs.
most other things were logically grouped together.

Blaise Laflamme

unread,

Mar 27, 2013, 4:33:00 PM3/27/13

to pylons...@googlegroups.com

you're about t reverse-engineer mcdonc's brain... be careful ;)

Jonathan Vanasco

unread,

Mar 27, 2013, 7:07:02 PM3/27/13

to pylons-devel

On Mar 27, 4:33 pm, Blaise Laflamme <bla...@laflamme.org> 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 ).

Chris Rossi

unread,

Mar 27, 2013, 1:58:40 PM3/27/13

to pylons...@googlegroups.com

>>> import this

See 5th rule.

Chris

Mike Orr

unread,

Mar 30, 2013, 1:22:36 PM3/30/13

to pylons...@googlegroups.com

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.

--
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...@googlegroups.com.
To post to this group, send email to pylons...@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 <slugg...@gmail.com>

Reply all

Reply to author

Forward