Hi Anthony

Many thanks for your response.

As I mentioned to Dave S above, I deliberately (and specifically) chose 
this example of downloading the MacOs version (for Normal Users) directly 
from the web2py website and compiling - and then reloading - the 'Welcome' 
application to demonstrate the problem as simply and clearly as I thought 
possible.

I therefore tried to - tautology alert! - *exactly mimic* what any standard 
user would expect to do and see what would happen. So I - deliberately - 
did not restart the web server or reload routes or anything else for that 
matter. (However, as it happens when I did restart the web server the 
problem still remained).

Anyway, I am still a bit puzzled!

Cheers
 

On Tuesday, 12 September 2017 02:22:59 UTC+1, Anthony wrote:
>
> Did you reload routes or restart the web server?
>
> On Monday, September 11, 2017 at 8:31:32 PM UTC-4, [email protected] 
> <javascript:> wrote:
>>
>> Today I came across some unusual behaviour in web2py when I tried to 
>> install a compiled web2py application. Coming home I decided to see if I 
>> could replicate the same problem on my Mac (running macos Sierra) and found 
>> some equally unusual behaviour.
>>
>> *The problem can be easily demonstrated:*
>>
>> 1. From the web2py website *I downloaded the Mac version of web2py* (for 
>> Normal Users) currently version 2.15.4-stable+timestamp.2017.09.02.04.02.22 
>> (Running on Rocket 1.2.6, Python 2.7.3) 
>>
>> 2. From the web2py administrative interface *I then compiled the 
>> ‘welcome’ application* which is a standard application which comes with 
>> web2py
>>
>> *3. I then ‘Packed’ this newly created compiled version of the standard 
>> 'welcome' application*
>>
>> 4. I then *Uploaded and installed this newly created compiled 
>> application using a different name for the application*
>>
>> 5. The original uncompiled ‘welcome’ application still works but the 
>> compiled version of the same application gives:
>>
>> invalid view (default/index.html)
>>
>> Obviously all of this is done on the same (i.e. one) machine with the 
>> same web2py version, Python etc and yet the compiled version will not work 
>> but the uncompiled version will. 
>>
>> Am I missing something obvious?
>>
>>

-- 
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
--- 
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to