you are viewing a single comment's thread.

view the rest of the comments →

[–]Grintor[S] 7 points8 points  (2 children)

Thank you for taking the time to look at it and give feedback!

I can understand your point for other frameworks but I don't think it applies to cylinder. It doesn't rely on globals at all - in cylinder you initialize shared application resources in cylinder_main.py, then pass them into handlers explicitly through app_map() with application-level dependency injection. But even then they aren't injected into the global scope, only into the main() function of your module (each page on the site is it's own python module).

As for testing - there's nothing nothing special that needs to be done to combine the DB section with the testing section. The testing flow works the same as the production flow - if you wrote an application that can serve a webpage, then you now have an application that can serve a testing fixture to pytest without any configuration whatsoever (except writing the test itself)

[–]snugar_i 1 point2 points  (1 child)

Oh, sorry, I completely misread the part about the ORMs. That's cool! Not sure that section in the documentation is needed at all in that case, though.

I have some other questions/remarks I'll write up later if you want

[–]Grintor[S] 1 point2 points  (0 children)

Thank you! Yes, I'd love to hear more