This is an old post. But I had this problem too. 'track_changes' works fine
in a brand new project. But i can't get it to work in my now quite large
project.
Eventually I found something that works. My module is called 'public.py'
and it lives where it should - in the 'web2py/applications/myap
I experienced this issue with the 1.99 series web2py. Not enough experience
with 2.1.1 to say for sure if it's still there. However, with 2.1.1, when I
insert print is_tracking_changes() I always see True. Will report any
inconsistencies if I see them in the future.
On Thursday, October 18, 201
I do notice the same problem here and it drive me crazy... I suspect that,
but since it seems to be intermittent, I wasn't sure...
I did what you ask and I get True all the time, but the change I had made
to module never been applied when page render.
Richard
On Mon, Oct 15, 2012 at 4:58 PM, Ma
yes, sorry, i meant in development time.
in one project i moved models to modules and shaved about 33% off of the
GAE production request time. another project is in test this week and i
will hopefully have numbers soon. note that when you don't need auth
(not all of my requests use auth) not
Hi...
When you say "now that i'm doing more and more in modules it does slow
things down"... are you talking about development time, right? is not
about the performace of you web2py app... is that?
The performance increase when using modules instead put code on models
worth all this extra work?
D
i use the persistent local datastore on GAE SDK as well. i have not tried
to turn on dynamic module re-loading on GAE, but i have a shell script that
starts/stops GAE and i just restart that. it's not as fast as
auto-reloading but it has been ok for me (though now that i'm doing more
and more
Oi Ricardo,
Thanks.
I add the option to use sql lite and databse keeps data when I restart
app engine SDK.
And about the module reloading... did you have any problems with it?
On Wed, May 9, 2012 at 5:54 PM, Ricardo Pedroso wrote:
> On Wed, May 9, 2012 at 8:35 PM, Alex Benfica wrote:
>>
>> I'm
On Wed, May 9, 2012 at 8:35 PM, Alex Benfica wrote:
>
> I'm having a seriuos problem having to stop and start Google App Engine SDK
> when I want edit modules, otherwise, they are not reloaded.
> The problem is that, doing this, I lose the entire database content on GAE
> SDK...
You can persist t
@Massimo- Thank you, I understand the practice but still not the
prescription. By turning the app on/off you mean disable/enable? Don't all
apps live in the same site-wide Python process, and wouldn't that mean that
the global objects would remain?
On Tuesday, May 1, 2012 9:40:00 AM UTC-4, Mass
Models and controllers are executed at every request therefore it is safe
to change them while the app is running. Web2py handles them the way it
does to allow you how replacement.
Python modules - in general - should not be replaced without turning the
app off and on again.
It really depends o
@Massimo- you're saying a production application should not reload modules,
but then what is the correct process for updating an app in production -
i.e. installing an app by overwriting an old one - if it has modules that
have changed?
On Sunday, April 29, 2012 12:02:52 PM UTC-4, Massimo Di Pi
@Massimo- you're saying a production application should not reload modules,
but then what is the correct process for updating an app in production -
i.e. installing an app by overwriting an old one - if it has modules that
have changed?
You're saying that an installing an app that overwrites an
@Massimo- The initial issue was about reloading modules for development not
production.
from gluon.custom_import import track_changes; track_changes(True)
was not consistently reloading modules on each request while we were
developing locally on the Rocket server, though I can't consistentl
Yes. because it depends on what module does. You should not do this in
production. Many "other" frameworks treat models and controllers and they
potentially suffer from this problem (depending on the module). This is why
in web2py models and controllers are not modules, to avoid this problem.
re
I would also like to comment that I suspect (unconfirmed) that reloading of
modules while references are still around appears to potentially cause
memory leaks.. during dev while modules are reloaded, our app's memory
usage grows significantly. With this disabled, we find a consistent
footprint
Let's clarify something
web2py always uses the most comment models/controllers/views.
web2py (as Python does) loads modules onces and keeps them in memory, even
when modules are shipped with the app.
The fact that
from gluon.custom_import import track_changes; track_changes(True)
overr
>
> @Bruno- Thanks for confirming this issue
> @Anthony - Thoughts?
>
Not sure what's going on. Perhaps Massimo or Pierre (creator of custom
importer) could weigh in.
Anthony
Got to say this is scary- we're about to go into production with our first
web2py app, and having erratic module behavior persist across server
restarts is not something we signed up for. Please let's address this.
On Sunday, April 29, 2012 9:12:55 AM UTC-4, Yarin wrote:
>
> @Bruno- Thanks for c
@Bruno- Thanks for confirming this issue
@Anthony - Thoughts?
>
@Bruno- Thanks for confirming this issue
@Anthony - Thoughts?
On Saturday, April 28, 2012 4:31:09 PM UTC-4, rochacbruno wrote:
>
> I have a similar problem.
>
> example:
>
> if I change this modules under this package:
> https://github.com/rochacbruno/Movuca/tree/master/modules/datamodel they
>
I have a similar problem.
example:
if I change this modules under this package:
https://github.com/rochacbruno/Movuca/tree/master/modules/datamodel they
never reloads, so I need to restart the server.
But if I change something in modules under this:
https://github.com/rochacbruno/Movuca/tree/mas
21 matches
Mail list logo
