Hi there,

I realise that the Pylons team have done a great job of allowing
Pylons to work with multiple templating engines, database interfaces
etc. but doesn't this kind of go against the One True Way philosophy
of Python? It seems completely backwards to me that Rails is based on
a language that borrows more than a little from Perl and is pretty
free-form, although Pylons is a free-form framework based such a
'railed' language as Python.

What I'd really like to ask is: Is Pylons going to get more 'railed'?

Some suggestions:

o By default, set the paste-script template to be configured for a
database driven application that uses SQLAlchemy and Mako.

No need to define the imports and initialise the models. Would allow
users to simply define Table classes. Other templates could be
accommodated for using different paste-script templates.

o Encourage easy internationalisation

At the moment the i18n folder contains one empty file. Do we create
language plugins (i.e. en.py) with a dict in a utf-8 text file which
could be referenced globally in the app? If so, how? The docs would
tell us the One True Way, would always deal with strings as unicode
and include config parameters for switching - I don't mind writing a
few extra functions, even if I don't intend on deploying elsewhere so
long as it was clear and consistent.

o Config variable available automatically

No need to import the CONFIG variable, would be automatically
available in a global namespace.

I'm sure that there are many other things that could be included in
the paste-script deployment but I haven't come across yet. But all of
the above would have made my time picking up Pylons much easier...

Brendan

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to