On Fri, Jan 8, 2016 at 12:55 AM, Torsten Irländer wrote:
> But I wasn't aware of that
> this
> could be a topic for a talk. Actually I thought this is kind of a hack but
> is
> seems to be not bad :D.
Organizing business logic has been a perennial issue for Pyramid and
Pylons developers forever.
Am Donnerstag, 7. Januar 2016 17:39:56 UTC+1 schrieb Paul Everitt:
> For the O’Reilly video series on Pyramid (and for the proposed PyCon talk
> with @mmerickel), I emphasized route factories. Move the location of the
> model instance out of the view and into the framework, namely, a context
Well I guess it does help me, because the way you describe doing it is
exactly how I currently have it implemented
On Wed, Jan 6, 2016 at 8:30 PM, Karl O. Pinc wrote:
> On Wed, 6 Jan 2016 13:35:18 -0800 (PST)
> Danuel Williams wrote:
>
> > Currently I am developing an application where I initia
For the O’Reilly video series on Pyramid (and for the proposed PyCon talk with
@mmerickel), I emphasized route factories. Move the location of the model
instance out of the view and into the framework, namely, a context variable
passed into the view.
I then moved more helper-style logic into t
In my experience, the standard scaffold way is perfect for most uses.
If your codebase grows very large, or you start needed to run non-pyramid
services, you may need to rethink things.
One of my projects outgrew the typical 'views' approach. Now, we prototype
the functionality onto the views
On Wed, 6 Jan 2016 13:35:18 -0800 (PST)
Danuel Williams wrote:
> Currently I am developing an application where I initialize some
> mapped tables from my DB via ORM (SqlAlchemy) within a module, and
> then I import these tables into the views I need and then perform
> operations on them within th