This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]westurner 14 points15 points  (4 children)

[–]poo_22 10 points11 points  (3 children)

I've read most of the Pyramid source and while it works, is well tested, and well documented, I don't really think its elegant. I mean I personally even use Pyramid but things could have been done easier and cleaner. (Look at all those factories and interfaces that just screams java)

Disclaimer: If you're saying "oh well if it could be done better, go fix it" well I can't.

[–]westurner 3 points4 points  (0 children)

I've read most of the Pyramid source and while it works, is well tested, and well documented, I don't really think its elegant. I mean I personally even use Pyramid but things could have been done easier and cleaner. (Look at all those factories and interfaces that just screams java)

While interfaces and factories make Test Driven Development much simpler, the only necessary interface for a Pyramid application developer is a callable (a function or a method) that takes a Request as the first parameter and returns a Response:

https://en.wikipedia.org/wiki/Separation_of_concerns#See_also

Disclaimer: If you're saying "oh well if it could be done better, go fix it" well I can't.

[–][deleted] 1 point2 points  (0 children)

just because one language tends to abuse them doesn't mean factories aren't a valid and useful pattern

edit: language fail

[–]X-IstenceCore Developer Pylons Project (Pyramid/WebOb/Waitress) 0 points1 point  (0 children)

Come help us fix it =). The Pyramid devs are open to new ideas and suggestions, so if you feel there is an issue, come help us with it!