On Sun, Mar 13, 2011 at 12:32 AM, Eric Ongerth wrote:
> +1. If I chose Pylons over Django and TurboGears (not to mention
> Rails) for its flexibility, light weight, and pluggability, Pyramid
> offers more of those qualities than Pylons and with better docs, plus
> built-in authorization/authentic
+1. If I chose Pylons over Django and TurboGears (not to mention
Rails) for its flexibility, light weight, and pluggability, Pyramid
offers more of those qualities than Pylons and with better docs, plus
built-in authorization/authentication support rather than the Pylons
situation with that.
On
Another vote to start with Pyramid. I've been using 'it' since repoze.bfg
1.1 and am constantly being pleasantly surprised. Now that there is a bigger
development community, even more docs, and more beginner friendly additions,
I can't think of any reason not to use it right away.
iain
On Fri, M
sure you can start with pyramid. pyramid 1.0 is already production
ready with its awesome docs.
On Mar 4, 5:10 am, Ravi wrote:
> Hi Group:
> I have started a new web based project and it is in its
> early stage. So with pylons merging with pyramids, I have two
> questions:
>
> 1) do
begin*
On Fri, Mar 4, 2011 at 11:07 AM, Joe Dallago wrote:
> Go with Pyramid. You have to think about your application 2-3 years
> down the road. You might be fine writing it in Pylons now, but as
> people start to convert, support will being to dwindle.
>
> On Thu, Mar 3, 2011 at 9:10 PM, Ravi
Go with Pyramid. You have to think about your application 2-3 years
down the road. You might be fine writing it in Pylons now, but as
people start to convert, support will being to dwindle.
On Thu, Mar 3, 2011 at 9:10 PM, Ravi wrote:
> Hi Group:
> I have started a new web based proj
Hi Group:
I have started a new web based project and it is in its
early stage. So with pylons merging with pyramids, I have two
questions:
1) do you all suggest starting with Pyramids ? Or shall I wait for
some more months ?
2) Are there any DO/DON'T that I should follow for make sur
