In pre 1.4 projects, it was common for projects to have multiple ways to import
stuff;
because the project path, and the path 1 level up were both in the python path.
This way, you can actually have 2 versions of the module imported,
and hence your singleton breaks (depending on the route taken t
On Mon, Nov 5, 2012 at 1:07 PM, drunksaint wrote:
> This model was running perfectly in the DEV deployement. When I moved to
> PROD in apache, this broke (as in there are multiple instances of scObj
> being created, so a score update from player-1's move on player-2 is not
> reflected in a differe
On Monday, November 5, 2012 7:07:23 PM UTC+1, drunksaint wrote:
> This model was running perfectly in the DEV deployement. When I moved to
> PROD in apache, this broke (as in there are multiple instances of scObj
> being created, so a score update from player-1's move on player-2 is not
> ref
I am currently using a DJango - apache installation (on mod_wsgi) to run a
website (project) which hosts an intranet cards game, whose rules are
complicated enogh that it requires only 1 master list+dict data structure
of scores for each user. Individual user's score can be impacted by other
4 matches
Mail list logo
