consider using plaster for config files instead of pastedeploy

[mmerickel]

Related to #14, we've written a new library called plaster for abstracting the config format away from Pyramid so that people can write their own custom formats. This can be updated in a bw-compatible way by depending on plaster_pastedeploy. Plaster can also be used for other purposes like sharing a config file with your message queue that is written as a gearbox subcommand or standalone.

http://docs.pylonsproject.org/projects/plaster/en/latest/

Again, I just wanted to bring it to your attention and am interested in your thoughts on using it.

[amol-]

Looks like plaster might solve some of the long standing problems of PasteDeploy and keep being compatible, thanks for pointing it out.

I'm willing to move gearbox to Plaster even though it might take some time before I'm able to, there is a bunch of other already started things that I need to complete before switching to this one. If anyone is willing to contribute a first port meanwhile it might be a good starting point we can refine with time.