This is interesting and I have not seen it before. I am tempted to say this is a python issue. Could also be a locking issue.
On Thursday, 31 January 2013 20:24:40 UTC-6, nite...@gmail.com wrote: > > I have two computers that I work on: a 32-bit netbook and a 64-bit > desktop. Sometimes I will rsync my entire working copy of the web2py > application I'm working on from one machine to the other, rather than > getting a fresh copy. When I do this from the netbook to the desktop, the > web2py server starts normally (no error messages), but when I try to access > the application, the web browser hangs forever. One really strange side > effect is that it also attempts to open a connection to the IP address > 64.99.64.32. (I'm not sure what significance this IP has, but if you Google > it you see a number of other pieces of software that also appear to use it > when things go wrong.) > > Anyhow, the first thing I tried -- deleting all the .pyc files -- had no > effect, so I did a full diff between the directory tree from the netbook, > versus a fresh copy checked out directly to the 64-bit machine, and the > only thing that differed was the ./web2py/applications/*/cache/cache.shelve > files. I deleted them, and everything worked normally again. > > Is this a known issue? Is it Python's fault for not knowing that a .shelve > file came from the wrong architecture? Or should I just be doing a "make > clean" from web2py every time I'm on a different machine (I notice that > removing all the cache directories is in there)? > > ~Felix. > -- --- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
