this is interesting.... as I was going to ask when we would work on being 2.6 compatible (since I started looking at parsers, and may have other interests in potentially using 2.6+ only things).
On Tue, Apr 14, 2009 at 11:05 PM, mdipierro <mdipie...@cs.depaul.edu> wrote: > > There is a python 2.5 requirement mostly because that is what I > tested. > > This looks like a bug in the tar module that ships with 2.6.1. > > Massimo > > On Apr 14, 10:04 pm, John <ponti...@gmail.com> wrote: > > It is reproducible (at least on my machine). > > > > Same problem with Firefox 3 and Safari 4beta. The tar file placed in > > web2py/deposit exhibits the same problem as the file that is > > downloaded. Both files are identical as verified by md5 checksums, so > > it is not happing during the transfer, but with I am guessing the tar > > function. > > > > Switching over to the windows side, after setting up my app > > "manually", I am able to pack, and then verify the tar. No problems. > > > > Time passes...and I get an idea while writing this response. > > > > Looking like the problem is on the mac side I decided to check a > > couple things. Turns out I am running Python 2.6.1 (from macports and > > running web2py from source). If I use the "default" python 2.5.1, my > > tar problem goes away. > > > > It looks like a Python v2.6.1 vs v2.5.1 that causes this issue. Is > > there a Python 2.5 requirement for web2py, or is this a version > > difference bug? > > > > John > > > > On Apr 14, 10:22 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > > > > > Is this reproducible? Does the browser make a difference? > > > Can you try delete everything under web2py/deposit and try again? > > > > > Massimo > > > > > On Apr 14, 7:58 pm, John <ponti...@gmail.com> wrote: > > > > > > I have been experiencing some issues with "pack all", and attempting > > > > to deploy an app on a different web2py instance. > > > > > > Long version: (for others that might be experiencing the same thing) > > > > My dev machine is a mac and the other test bed box is a windows vm > > > > (not that it matters). I was seeing some odd behavior on the windows > > > > side after an import of my app, namely none of my jQuery stuff was > > > > working. Firebug was complaining about jQuery, so I verified that I > > > > could infact get to the jquery.js through the browser. My next > > > > thought was that something was up with the web2py_ajax.html. I was > > > > right, though not like I was thinking. Turns out the the file was > > > > empty (zero bytes). > > > > > > I go back to the mac side, and test the tar file generate by pack. > > > > Tar was not happy with the archive, in fact it stopped with > > > > web2py_ajax.html > > > > > > galt:Downloads john$ tar -tvf web2py.app.wammo.tar > > > > drwxr-xr-x john/staff 0 2009-04-14 18:49:29 ./ > > > > .... > > > > lots of files/dirs > > > > > > -rw-r--r-- john/staff 2098 2009-04-14 18:23:18 views/layout.html > > > > -rw-r--r-- john/staff 2243 2009-04-05 17:16:53 views/ > > > > web2py_ajax.html > > > > tar: Unexpected EOF in archive > > > > tar: Error is not recoverable: exiting now > > > > > > For what it is worth, it always seems to die with that same file. > > > > Also, the 'pack compiled' does not seem to exhibit the same problem. > > > > At least, it my few tests I seem to get a clean tar each time. > > > > > > I am running the web2py 1.61 (I also was seeing this in a previous > > > > version 1.57 IIRC, but didn't take the time to investigate) > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
