Re: [web2py] Problems with online book?
hehe On 26 July 2011 19:55, Bruno Rocha rochacbr...@gmail.com wrote: May be it is a Marketing strategy, making you all to buy the printed version of the book! LOL... (or just Massimo updating something)
Re: [web2py] Re: Python 3 and the future of web2py
Agreed, I think web2py on Py3 is pointless. An entirely different project, called, let's say, web3py, which runs on Py3 is a different animal altogether... On 13 July 2011 15:50, Anthony abasta...@gmail.com wrote: The problem is, it would break backward compatibility. On Wednesday, July 13, 2011 12:54:57 AM UTC-4, Rahul wrote: Its true that there are existing python versions 2.6, 2.7.x but what I would like is Web2py support for Python 3. Reasons: 1. We should provide early support for Python 3 (regardless of what wsgi standard it will provide) because it may trigger a lot of python users to adopt Web2py as it might be the ONLY Full Stack Framework that will be supporting Python 3 2. Python 3.x is the future of Python (I see this to be very true) Eventually we would all be using Python 3.x in our production systems. 3. Lets progress rather than remaining stagnant with existing versions of Python only. I mean Why Not the latest Python ?? Cheers, Rahul D On Jul 12, 5:38 pm, pbreit pbreit...@gmail.com wrote: I suspect 2.6 is going to be popular for some time since that's what's in the current Ubuntu LTS (10.04).
Re: [web2py] Re: Python 3 and the future of web2py
Is it worth calling the prototype version *before* web3py: web3000py? Or would that be unbearably geeky? Sent from my iPad On 13 Jul 2011, at 5:21 PM, Massimo Di Pierro massimo.dipie...@gmail.com wrote: +1 On Jul 13, 9:28 am, Caleb Hattingh caleb.hatti...@gmail.com wrote: Agreed, I think web2py on Py3 is pointless. An entirely different project, called, let's say, web3py, which runs on Py3 is a different animal altogether... On 13 July 2011 15:50, Anthony abasta...@gmail.com wrote: The problem is, it would break backward compatibility. On Wednesday, July 13, 2011 12:54:57 AM UTC-4, Rahul wrote: Its true that there are existing python versions 2.6, 2.7.x but what I would like is Web2py support for Python 3. Reasons: 1. We should provide early support for Python 3 (regardless of what wsgi standard it will provide) because it may trigger a lot of python users to adopt Web2py as it might be the ONLY Full Stack Framework that will be supporting Python 3 2. Python 3.x is the future of Python (I see this to be very true) Eventually we would all be using Python 3.x in our production systems. 3. Lets progress rather than remaining stagnant with existing versions of Python only. I mean Why Not the latest Python ?? Cheers, Rahul D On Jul 12, 5:38 pm, pbreit pbreit...@gmail.com wrote: I suspect 2.6 is going to be popular for some time since that's what's in the current Ubuntu LTS (10.04).
Re: [web2py] Re: web2py deployement on windows
Sorry, I wasn't being specific. My idea was just to provide defaults with the startup of web2py to reduce a step. There is no literal accept button. Sent from my iPad On 12 Jul 2011, at 5:09 PM, mart msenecal...@gmail.com wrote: Hey, I havent't seen any 'accept' button... do you have SSL enabled with this config? Thanks, Mart :) On Jul 12, 2:18 am, cjrh caleb.hatti...@gmail.com wrote: I think we can fill in defaults for IP and port, and only require a user to hit accept if they agree. So that should make things even easier to just get started. Also, the time that the splash logo is displayed is actually a setting, it isn't busy working during that delay. I have been considering for a while putting a close button (think a small X somewhere) so that if you don't want to wait you can just go straight into the little config window.
Re: [web2py] Re: Admin security: https vs localhost
This can work. On 13 Jul 2011, at 2:55 AM, Anthony abasta...@gmail.com wrote: If you add a complexity requirement, make it for remote connections only. Anthony On Tuesday, July 12, 2011 6:32:48 PM UTC-4, Massimo Di Pierro wrote: we can make a delay default to 1 second and double it every failed attempt. we should add complexity. I would take a patch or add an issue in google code. On Jul 12, 8:01 am, cjrh caleb.h...@gmail.com wrote: I like the timeout/delay idea for a failed password, and I very much like the IP block after a number of failed attempts, but I am not too fond of a complexity requirement. During development on my local machine (bound to localhost), my standard admin password is a. I would have to have to deal with a complexity checker during development; and if we then say it will be enabled only for production but not dev, then we need more code and error-handling to manage the distinction, and it all becomes a lot of work. I think the safeguards that are currently in web2py are quite sufficient, and we can improve it a little bit more by penalizing brute force on the password, as pbreit pointed out is currently vulnerable.
Re: Re: Re: [web2py] Re: web2py 1.96.4 is OUT
On 11 June 2011 04:55, Pierre Thibault pierre.thibau...@gmail.com wrote: 2011/6/9 Pierre Thibault pierre.thibau...@gmail.com 2011/6/9 caleb.hatti...@gmail.com On , Anthony abasta...@gmail.com wrote: Do you have an app to reproduce the problem? I created an app named Castalia (note the capitalization) with a module /modules/selfgroup/castalia/config.py, which I think is the same structure and naming as Alessandro's app. In a controller action, I then did: from selfgroup.castalia import config and it seems to work fine, though I believe Alessandro was getting an import error at that point. But maybe I'm missing something. I think we should ask him to make a small test app for us that demonstrates the problem. Else we're guessing. Alessandro, can you send us the code having the unexpected behavior so the Windows guys can take a look? As I understand, you have to remove the capitalization to make it work because otherwise even if the capitalization match, it does not import properly. Right? -- OK, since we cannot reproduce the bug and we cannot know precisely what the bug is, we will consider the issue closed. Do you think there is something to add about this issue? I would agree with that. Anthony has tested the capitalization issue directly (it works), and I checked what happens on Windows with capitalized nested folders and import statements (they work if the capitalization is matched). I think we need a reproducible test case here.
Re: [web2py] Re: web2py 1.96.4 is OUT
On 11 June 2011 11:42, Pierre Thibault pierre.thibau...@gmail.com wrote: 2011/6/11 Alessandro Iob alessandro@gmail.com Hi Pierre, I'll send a test application to Anthony this weekend. I've experienced the same problem under OS X (with a case-insensitive file system) when I've changed the case from Castalia to castalia: web2py tried to include the controllers from old Castalia path and not from the new lowercase version. Obviously I've closed and restarted web2py before changing the application name. I think OS X has a filename cache of some kind. Alessandro OK, cool! I'll be the reference for questions on the code. If needed, you may write directly to my personal mail box. I don't follow everything on the web2py mailing list because there is too many messages so I may sometimes miss something. Ok, I am going to make a strategic exit here. I think you guys will be able to solve it, now that we know what to look for, and will have a test case. I looked over the code in custom_import and I couldn't find anything wrong regarding casing. kind regards Caleb
Re: [web2py] Re: New Features in Book
On 10 June 2011 12:47, anil manikyam anilmanikya...@gmail.com wrote: how i will send a mail to others using web2py Just post on the web2py Google Group.
Re: Re: [web2py] Re: web2py 1.96.4 is OUT
On , Pierre Thibault pierre.thibau...@gmail.com wrote: 2011/6/9 cjrh caleb.hatti...@gmail.com On Thursday, 9 June 2011 03:03:51 UTC+2, Massimo Di Pierro wrote:Users who have an opinion please share it now. This is important. Could you direct us to more details about the issue? My current understanding is shallow, but I agree with Pierre that platform-specific environment settings are very likely not the way to go here. I much prefer all cross-platform issues to be handled with the os and sub modules. Why can't we do that here? It seems we have no developer with Windows where is the problem. I am on Windows, still XP even. Is there a small zipped app that I could test quickly to see the problem?
Re: Re: Re: Re: [web2py] Re: web2py 1.96.4 is OUT
On , Anthony abasta...@gmail.com wrote: On Thursday, June 9, 2011 10:18:41 AM UTC-4, cjrh wrote: On , Massimo Di Pierro massim...@gmail.com wrote: So you suggest removing the case insensitive flag that was added in 1.96.4? Yes. In Alessandro's specific case, he should use: import app.Castalia.blah.blah.castialia But shouldn't he be able to just do 'import castalia' and have it work (again, for me it actually does work on Windows, but assuming it doesn't work on some systems, shouldn't it be fixed)? The issue seems to appear only when there is a repeated name in the chain. Could you test that too? My attachment has such a test-case ready to run. It seems that when a name is not repeated, the case-insensitive name matching works. This smells like a bug in Python, and probably needs to be fixed there.
Re: Re: Re: [web2py] Re: web2py 1.96.4 is OUT
On , Anthony abasta...@gmail.com wrote: Do you have an app to reproduce the problem? I created an app named Castalia (note the capitalization) with a module /modules/selfgroup/castalia/config.py, which I think is the same structure and naming as Alessandro's app. In a controller action, I then did: from selfgroup.castalia import config and it seems to work fine, though I believe Alessandro was getting an import error at that point. But maybe I'm missing something. I think we should ask him to make a small test app for us that demonstrates the problem. Else we're guessing.
