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
My problem (with appy.pod) still persists in v2.2.1 so I'm locked to
v2.0.9...
--
Can i get the complete traceback?
On Wednesday, 17 October 2012 22:59:43 UTC-5, Donatas Burba wrote:
I have noticed another issue. With version 2.1.1 I can't use appy.pod
anymore. It means I can generate only one pdf file, every other try gives
me error (that I'm using python which can't
Also, where is appy.pod installed? In python site-packages, in web2py
site-packages, or in the app modules?
On Wednesday, 17 October 2012 22:59:43 UTC-5, Donatas Burba wrote:
I have noticed another issue. With version 2.1.1 I can't use appy.pod
anymore. It means I can generate only one pdf
In the app modules
2012 m. spalis 18 d., ketvirtadienis 15:36:17 UTC+3, Massimo Di Pierro rašė:
Also, where is appy.pod installed? In python site-packages, in web2py
site-packages, or in the app modules?
On Wednesday, 17 October 2012 22:59:43 UTC-5, Donatas Burba wrote:
I have noticed
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
Traceback (most recent call last):
File /var/www/advokatai/gluon/restricted.py, line 209, in restricted
exec ccode in environment
File
I am now seeing this issue again on 2.1.1. I'm getting True from
is_tracking_changes() but a change in one of my modules isn't showing in
the browser.
On Tuesday, October 16, 2012 4:15:42 AM UTC+8, David Marko wrote:
I have a module in my app that i was working on extensively today. I
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,
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,
I have noticed another issue. With version 2.1.1 I can't use appy.pod
anymore. It means I can generate only one pdf file, every other try gives
me error (that I'm using python which can't access uno). I think that
problem is in custom_import.py, so I was forced to return back to 2.0.9,
where
Which version? Make sure you are using 2.1.1 because we changes something
in this respect.
On Monday, 15 October 2012 15:15:42 UTC-5, David Marko wrote:
I have a module in my app that i was working on extensively today. I
realised that web2py doesnt reload it correctly when change tracking
Using the latest trunk ... Updated today
--
Can you do
from gluon.custom_import import *
track_changes(True)
print is_tracking_changes()
does it print True all time? It should.
On Monday, 15 October 2012 15:43:49 UTC-5, David Marko wrote:
Using the latest trunk ... Updated today
--
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
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?
Do
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)
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...
Is there a way to edit web2py modules and get then reloaded each time I run
On Wed, May 9, 2012 at 8:35 PM, Alex Benfica alexbenf...@gmail.com 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...
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 rmdpedr...@gmail.com wrote:
On Wed, May 9, 2012 at 8:35 PM, Alex
I think I've figured out the issue I was having with the auto reloader- the
modules I import into the app do in fact reload, it was their dependancies
that weren't- so if made a change on a module that was being imported only
by another module, the changed module wasn't reloaded.
The solution
@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
@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
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
@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,
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
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.
@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
@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
never
@Bruno- Thanks for confirming this issue
@Anthony - Thoughts?
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
@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
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)
from gluon.custom_import import track_changes; track_changes(True)
On Saturday, 28 April 2012 14:43:42 UTC+1, Yarin wrote:
For dev purposes, it would be nice to be able to reload modules without
having to restart the server- or to have a setting that automatically
reloads on each request-
On Saturday, April 28, 2012 10:24:21 AM UTC-4, simon wrote:
from gluon.custom_import import track_changes; track_changes(True)
And note that only reloads when the module changes, not on every request.
Anthony
Awesome- thanks!
On Saturday, April 28, 2012 10:24:21 AM UTC-4, simon wrote:
from gluon.custom_import import track_changes; track_changes(True)
On Saturday, 28 April 2012 14:43:42 UTC+1, Yarin wrote:
For dev purposes, it would be nice to be able to reload modules without
having to restart
Anthony- is this a performance hit, or can it be left on?
On Saturday, April 28, 2012 10:39:00 AM UTC-4, Anthony wrote:
On Saturday, April 28, 2012 10:24:21 AM UTC-4, simon wrote:
from gluon.custom_import import track_changes; track_changes(True)
And note that only reloads when the module
I've been trying this and it is *not* working.
I put this exact line:
from gluon.custom_import import track_changes; track_changes(True)
in my 0.py model file, before any other code. But still any changes I make
in my modules do not take effect until I restart server- or if they do it
is
On Saturday, April 28, 2012 1:50:25 PM UTC-4, Yarin wrote:
Anthony- is this a performance hit, or can it be left on?
It has to check the modification time of each file upon import, so may be a
small performance hit.
Anthony
Hmm, it's working for me. Can you post a module and some code for which
it's not working?
Anthony
On Saturday, April 28, 2012 2:40:35 PM UTC-4, Yarin wrote:
I've been trying this and it is *not* working.
I put this exact line:
from gluon.custom_import import track_changes;
@Anthony- There's really nothing specific to post, its a general thing, and
not the first time i've dealt with it- just that this code fix doesn't
change anything. Moreover, now I'm experiencing some truly odd behavior.
1. I have a module that was throwing an error, and fixing it doesn't
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:
41 matches
Mail list logo
