thank you Graham

very interesting and helpful overview

I decided to test more and stay with pylons at least for the current
and next few projects

By the way web2py was not mentioned in the list. Have you had any
chance to test it ?

cheers

daniel



On Jun 4, 2:47 pm, Graham Higgins <[email protected]> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 4 Jun 2010, at 12:09, daniel wrote:
>
> > Actually they are scaring largely much behind authkit
>
> Fortunately, it'd be relatively easy to swap out Authkit in favour of  
> a different auth'n'auth implementation if required, so there's not too  
> much to worry about there.
>
> > my questions are :
>
> (timely, I'd say)
>
> > 1. Is still wise starting new long term projects based on Pylons ?
>
> In my technical opinion [1], you need have no doubts on that score. I  
> view Pylons as an excellent choice for a web app development framework  
> in both the short and the long term. And, as we have seen recently on  
> this list [2], it has had some significant, hitherto-unadvertised,  
> take-up by some serious players.
>
> James' direct involvement with Pylons development would seem to have  
> ceased a couple of years ago (about the same time he wrote the text on  
> that page, I suspect). You may wish to ascertain this for yourself by  
> looking through the commit records in the Pylons project development  
> history here: <http://bitbucket.org/bbangert/pylons/changesets>
>
> The fact that Pylons development has continued apace and unaffected  
> since then stands as its own attestation to the cohesion, skill and  
> commitment of Ben, Phil, Ian, Mike and the other (all-too-often-
> unsung) contributors from the community.
>
> > 2. How strong and motivated remains the Pylons development community ?
>
> (see above but ..) I'd say "very" and I'd also say that the strength  
> of motivation is reasonably immediately discernible from public  
> sources [2, again]. There's a lot of informal background scattered  
> across posts to this list and if you have specific concerns you might  
> find some reassurance there.
>
> One particular characteristic of this community which I personally  
> appreciate (but which may act to mislead people at times) is a  
> distinct and deliberate absence of evangelism. IMO, that attests to a  
> very level-headed engineering perspective and a solid understanding of  
> where Pylons is located in the landscape of Python-based web app  
> development frameworks.
>
> (Again, personally ...) I decided to reinforce my own commercial  
> commitment to Pylons with an investment of my time in contributing to  
> Pylons' development (mainly documentation and bug-fixing). I've also  
> learned, from personal communication with others in the Pylons-using  
> community, that there is a consistent and persistent level of interest  
> in helping to support the broad-scale Pylons effort by relieving the  
> dev team of some of the less technically-demanding chores but nothing  
> concrete has emerged yet --- we all have day jobs :-)
>
> > 3. Which are, if any, the long term python web frameworks to
> > eventually consider as alternative to pylons ? (should I re-evaluate
> > django , which I don't like technically so much but it seems can count
> > on larger stable development community)
>
> In the absence of the context of a set of requirements, recommendation  
> turns into profitless speculation, so I shall evade the issue entirely  
> and simply provide a link to key info: 
> <http://wiki.python.org/moin/WebFrameworks
>  >
>
> Amongst the frameworks where I "know" (in the modern, net sense of the  
> term) the developers: TurboGears deserves a half-facetious mention  
> (half-facetious because it's based on Pylons ... but see [3]).  
> Agendaless' repoze.bfg [4] is worth your attention, as is Grok [5].  
> And Plone remains a serious candidate.
>
> You will probably be interested in Marco, a speculative successor to  
> Pylons/BFG (ono).
> Here's the repos overview <http://bitbucket.org/chrism/marco/overview>  
> and here's some ill-organised-but-at-least-collated-in-one-spot  
> narrative background:http://bel-epa.com/notes/Marco/
>
> HTH.
>
> [1]http://bel-epa.com/gjh/cv.pdf
> [2]http://groups.google.com/group/pylons-discuss/browse_thread/thread/fa...
> [3]http://blip.tv/file/get/Pycon-PyCon2010HowPythonTurboGearsAndMongoDBA...
> [4]http://bfg.repoze.org/
> [5]http://grok.zope.org/
>
> - --
> Cheers,
>
> Graham
>
> http://www.linkedin.com/in/ghiggins
>
> -----BEGIN PGP SIGNATURE-----
>
> iEYEARECAAYFAkwI9d8ACgkQOsmLt1Nhivx9CwCbBfMt17yieT9w+xISrDprN/ln
> Q/EAnRo6fBtxe5oO6op+GGT2litj2iECiQCVAgUBTAj131nrWVZ7aXD1AQJSWQP+
> OqH/ILK6C9aRUHbxmdyfm0IBAPU9bEXuFgaB9d2tysXre/mobMSNAg9Qz/4DKCnb
> DCwqL0Qin6bNgphoX9gZArCNqpOgQJXOuZlHTc8xCK2YEO/LUx3cSTVIUiUlBD9S
> BYS1l6/6tsM47QwuPfnbmIIkk4FWJYQTvlfqAVhd66Y=
> =6+Vk
> -----END PGP SIGNATURE-----

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/pylons-discuss?hl=en.

Reply via email to