Pyramid is only actually dependent on PasteScript for the paster command and scaffolds, so whether Paste gets ported or not isn't a big deal. The paster command is used to generate scaffolds, start servers and the convenient ability to "paster request" simulate a request into a conforming WSGI app.
If we are interested in porting PasteScript it's definitely an undertaking because there is a large amount of code unused by a basic Pyramid application. It'd probably be worth taking the opportunity to look into some fairly large bw-incompat changes to PasteScript to knock its capabilities into something more manageable. For example, it currently uses Cheetah to do templates which is not py3k compatible whereas Jinja2 is compat and more actively developed/supported. PasteDeploy has been ported, so hopefully INI file syntax can remain relatively unchanged minus the fact that it may be unlikely paste.httpserver is ported. -- Michael -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
