IMO the only thing we need for configuration is a 100% compatible, no extra features version of Paster that is easier to read and extend, and that runs on Python 3.2. Call it 'baster'. It will understand Paster entry points, paste deploy .ini files and be able to 'baster serve'. The templating feature or 'baster shell' or other stuff I don't know about may have to be a separate command. If you want YAML or XML or ASN.1 configurations then you can turn those into a dict and pass it into a load_wsgi_server() function that is much more loosely coupled to ConfigParser than the current Paster.
In other words, the required and documented dependency should be extraordinarily boring and simple. Its author will hang his head in shame at releasing such a banal package. Instead, the awesome YAML SQL ZODB database-/dev/null fairy dust driven configuration tool can reuse 'baster' and its load_wsgi_server() function in a way that is not pleasant with Paste. -- 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.
