Thanks! I'm really eager try web2py (and Python). I can give it a shot on Ubuntu 9.04 this weekend (if I meet my current project's aggressive deadline).
On Jun 21, 11:08 am, mdipierro <[email protected]> wrote: > I am uploading a fix to this problem for authentication now. It will > be in trunk in a couple of minutes, please give it a try. > > Massimo > > On Jun 21, 9:39 am, Faye <[email protected]> wrote: > > > > > On Jun 20, 11:02 pm, mdipierro <[email protected]> wrote: > > > > "officially" we say we only support 2.5 because if people use 2.6 only > > > syntax they app will not work on 2.5. "technically" web2py runs on 2.6 > > > with only one known issue: The cgi module that parses form variables > > > behaves differently in 2.5 and 2.6. If you do a POST and you also have > > > variables defined in the URL they behave in different ways. You have > > > to be careful about this in your own code. To my knowledge the only > > > part of web2py code that is affected is redirection after login. I was > > > planning to change the code tomorrow in trunk so that is behaves the > > > same in 2.5 and 2.6. > > > Thanks! I appreciate the quick answers from you and JohnMC. > > > I'm looking forward to trying out web2py once the Python 2.6 issues > > are addressed. I'd be new to Python, so it'll take at least a couple > > hours before I become proficient enough to start debugging > > compatibility issues. ;) > > > > > 2. Are web2py security fixes/updates timely and backwards > > > > compatible? We can't upgrade to major new (incompatible) versions > > > > just to get security fixes. > > > > We do not distinguish between security fix releases and major releases > > > because we NEVER broke and NEVER will break backward compatibility. > > > That is why we "official" support 2.5 and not 2.6. You should always > > > upgrade to the latest version of web2py. If we involuntarily break > > > something we treat it as a bug. Let us know and we fix it immediately. > > > This is great and will be an important factor in making the decision > > to switch from Rails to web2py. > > > > > 3. What is web2py's release & support policy? How long is each major > > > > version of web2py supported with secuirty & bug fixes before being > > > > retired? An official policy like Ubuntu would help ease concerns on > > > > the enterprise because it makes planning ahead easy. > > > > We try to have biweekly releases. 1.xx.0, we have bug fix releases > > > 1.xx.yy when needed. > > > This is great, especially in keeping with maintaining backward > > compatibility. > > > I hope web2py makes it into the Debian/Ubuntu repository before the > > next Ubuntu LTS is released. That way, we can get security updates > > automatically (provided the package maintainer isn't asleep). > > > > > 4. What is web2py's recommended plugin/library to use Paypal IPN? > > > > This needs to be stable--not bet--since it deals with monetary > > > > transactions. > > > > I do not know. I have never used paypal with web2py. I strongly > > > recommend using google checkout instead and this library: > > > > http://web2py.appspot.com/plugin_checkout/default/checkout > > > > It is very solid. It was used to run the PyCon 2009 conference > > > registration. We did not miss one transaction (800 payments). It > > > includes level 2 notifications. i.e. google informs your app about all > > > stages of a payment process including cancellations and refunds. It is > > > very secure because all communications between google and your app are > > > encrypted, authenticated, initiated by google, google re-tries if your > > > app does not respond. > > > Sounds like Google Checkout works the same way as Paypal IPN! We're > > going to look into it and probably support both. > > > > > FWIW, one important reason looking for alternatives to Ruby On Rails > > > > is security. We want to easily fix underlying security issues with > > > > the language and the framework. But we don't see a way to get > > > > automatic & fast security updates on Ruby On Rails without backwards > > > > compatibility concerns. > > > > One again. We promise our users not to break backward compatibility > > > this is a policy. > > > We never had any security related bug (as far as I can remember). > > > Even better than I had hoped! Looking forward to the Python 2.6 > > fixes. > > > Thanks again for the reply. I'm pretty sure web2py will gain many > > users and teachers based on what I've seen so far. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
