On Sunday, May 26, 2019 at 6:17:53 AM UTC-4, hynek wrote:
>
>
> t I’ve started putting separate features into separate sub-packages and it
> made my maintenance experience much more pleasant thanks to the locality of
> common contexts. As for tests, I just mirror the structure in my global
>
> On 26. May 2019, at 11:57, Nejc Zupan wrote:
>
> And I’m glad I did it. The codebase of the new project (while ~4x smaller
> than the old) is
> vastly more readable and navigate-able. The only drawback that I found so far
> is that it is a bit harder to
> ask my editor, for example, “I
> On 25 May 2019, at 18:56, Theron Luhn wrote:
>
> You’ve organized the modules by sections of the website, and the relevant
> views and models in each section. I usually do the inverse, split my app
> into views, models, templates, etc. I’d be interested to see what “best
> practice” is
On Sat, May 25, 2019 at 9:56 AM Theron Luhn wrote:
>
> Very nice! Several years ago I asked on this mailing list for some example
> Pyramid applications, this would have been a great one to look at.
>
> You’ve organized the modules by sections of the website, and the relevant
> views and
Very nice! Several years ago I asked on this mailing list for some example
Pyramid applications, this would have been a great one to look at.
You’ve organized the modules by sections of the website, and the relevant views
and models in each section. I usually do the inverse, split my app into
Hey all!
TL;DR: I’m working on a RealWorld.io backend implementation in Pyramid. I’d
like to ask fellow pharaohs and mummies to review my code so that I don’t teach
people bad patterns: https://github.com/niteoweb/pyramid-realworld-example-app
RealWorld.io is a community effort of implementing a
