On Jun 20, 7:17 am, "Biswas, Pinakee" <pina...@vvidiacom.com> wrote:
> 1. I think there is no controller in Pyramid and I think the ViewsYes.
> probably plays the role (for what is there in Pylons). In Pylons, I could
> have multiple controllers (or python files/modules in controller folder to
> say in crude way). I think in Pyramid, it would probably be the same (new
> python modules) but route needs to be defined. The view.py is provided when
> a Project is created.
views in Pyramid are similar to Controllers in Pylons.
There is also a pyramid_handlers package (
Pyramid is a lot more configurable than Pylons, so you can have both
/views.py is just a file that was created by an application scaffold.
You can replace it with /views/__init__.py
It is only read when you `config.scan("cliquedin.views")` on
> 2. In Pylons, lib folder contained 3rd party code and any other codeYour Pyramid application is really just a Python package. It expects
> that doesn't fit in the main application. Is there anything similar in
> Pyramid? Or any similar convention?
certain files in certain places, and those files to do certain things
-- but you have plenty of namespaces to work with.
I prefer to structure my lib folder like this:
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.