On Mon, Mar 21, 2011 at 11:08 AM, Alice Bevan–McGregor <al...@gothcandy.com> wrote: > On 2011-03-20 23:23:02 -0700, Mike Orr said: > >> On Sun, Mar 20, 2011 at 8:12 PM, Joe Dallago <jd.dall...@gmail.com> wrote: >>> >>> This issue has been previously discussed, I just wanted to make sure >>> that everyone agrees. At the moment the docs refer to "paster >>> templates" and renderered templates(mako, chameleon, jinja) using the >>> same name. I propose that we change the official nomenclature used to >>> describe "paster templates" to "skeleton," and leave the word >>> "template" to describe rendered templates. Any objections? I will >>> start going through the docs as soon as I get the ok from everyone. >> >> Yes. I already did that in the Akhet manual but I had to introduce it >> with "template" and use "template" in the PyPI description for ppl who >> might not recognize it. The sooner we can get away from "template" >> completely, the better. >> >> -- >> Mike Orr <sluggos...@gmail.com> > > ±0 — skeleton describes what it is less than, say, blueprint. A Linux > /etc/skel is static, for one. Blueprints often reference other blueprints, > too.
I like the word blueprint better than skeleton, actually. I would have suggested it but you had already taken the name. I don't think we can use your implementation classes directly, because they make a several fundamental changes compared to PasteDeploy/PasteScript that I don't think Pyramid is ready to commit to at this point. Such as using alacarte, being another namespaced package, adding several dependencies, etc. I've heard your packages are also Python 3-only? I think what we'll probably do is make a new implementation of Paste* but keep the features and API mostly the same, at least that's what a few developers are working on. Would you mind if we use the term "blueprint" in this "paster create" replacement? -- Mike Orr <sluggos...@gmail.com> -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-devel@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.
