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 > tests directory. That’s probably just a matter of taste.
The biggest improvement we had to overall efficiency and happiness was splitting the model into it's own package. We have multiple Pyramid, Python, Celery, Twisted, etc apps all import a unified model. The model has it's own tests, each package/application has it's own tests against the model as well. Doing this centralized and simplified the management of the database across all the different components, and more importantly multiple levels of testing. The end result was a much more frictionless build/deploy. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/5f8b2416-76ef-482d-94ce-8d12758cad03%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
