> Anyway, this person also posted on mod_python list. One of the things
> I highlighted there was that mod_python for some configurations is
> multithreaded and as such they may not be properly protecting
> variables if they are storing them at global scope. They haven't
> responded to any comments
> req.write(str(lab.game.settings.daemons))
> del lab.game.settings
> req.write(str(lab.game.settings.daemons))
> lab.game.settings = lab.game.InitGame()
> req.write(str(lab.game.settings.daemons))
>
Sorry, that should have been:
req.write(str(lab.g
On Apr 4, 10:41 am, Jon Clements wrote:
> On 3 Apr, 23:58, Aaron Scott wrote:
>
> > > are you an experienced python programmer?
>
> > Yeah, I'd link to think I'm fairly experienced and not making any
> > stupid mistakes. That said, I'm fairly new to working with mod_python.
>
> > All I really wan
On 3 Apr, 23:58, Aaron Scott wrote:
> > are you an experienced python programmer?
>
> Yeah, I'd link to think I'm fairly experienced and not making any
> stupid mistakes. That said, I'm fairly new to working with mod_python.
>
> All I really want is to have mod_python stop caching variables. This
Aaron Scott wrote:
> Yeah, I'd link to think I'm fairly experienced and not making any
> stupid mistakes. That said, I'm fairly new to working with mod_python.
>
> All I really want is to have mod_python stop caching variables. This
> seems like it should be easy enough to do, but I can't for the
> are you an experienced python programmer?
>
Yeah, I'd link to think I'm fairly experienced and not making any
stupid mistakes. That said, I'm fairly new to working with mod_python.
All I really want is to have mod_python stop caching variables. This
seems like it should be easy enough to do, bu
are you an experienced python programmer?
a lot of newbies post here with problems related to unexpected results
because they make "the usual" mistakes about list mutability and default
function arguments.
i suspect that's not the case here, but it seemed worth mentioning, just
in case.
andrew
Huzzah, another post.
I just discovered that even physically deleting the variable doesn't
work.
The module storylab.game has the class InitGame, which contains
"daemons = {}".
A user runs the code, resulting in some values in "daemons":
"{'berry2': , 'berry3': , 'berry1': }". These are pickled.
Okay, I'm at my wit's end. I have a Python app, running via
mod_python. There are variables in this app that, when changed, save
their changes to a pickled file tied to a session ID. Then, when the
page is accessed again, the variables are loaded from the respective
file.
But, when one user uses t
Is there a way to make a Python app running in mod_python with zero
persistence? I have an app that should be resetting its variables
every time you access it, but sometimes -- and only sometimes -- the
variables persist through a couple refreshes. They'll even persist
through multiple browsers, so
10 matches
Mail list logo
