[issue13315] Unable to deal with large tarfile
New submission from Dave Flogeras : I am trying to unpack boost_1_46_1.tar.bz2 (you can grab it here http://mirror.its.dal.ca/gentoo/distfiles/boost_1_46_1.tar.bz2) with the following code: import tarfile t = tarfile.open( "boost_1_46_1.tar.bz2" ); t.extractall() On OSX (both Lion and Snow Leopard, so python 2.7.1 and 2.6.1 resp.) this works as a normal user, but not as root failing with: Traceback (most recent call last): File "", line 1, in File "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/tarfile.py", line 2028, in extractall self.extract(tarinfo, path) File "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/tarfile.py", line 2065, in extract self._extract_member(tarinfo, os.path.join(path, tarinfo.name)) File "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/tarfile.py", line 2157, in _extract_member self.chown(tarinfo, targetpath) File "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/tarfile.py", line 2269, in chown os.chown(targetpath, u, g) OverflowError: signed integer is greater than maximum I have confirmed that Python is running as a 64bit application on OSX. On my 64bit Linux (gentoo) machine, this works both as a user and as root. I tried with Python 2.7.2 as well as downgrading to 2.7.1. This could be related to 1215928 -- messages: 146800 nosy: Dave.Flogeras priority: normal severity: normal status: open title: Unable to deal with large tarfile versions: Python 2.7 ___ Python tracker <http://bugs.python.org/issue13315> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13315] tarfile extract fails on OS X system python due to chown of gid=-1
Dave Flogeras added the comment: Thank you sirs. I've already got a workaround for this situation, and personally don't care to waste my time with apple. I'm satisfied that Python is handling bugs seriously and it will hopefully get into an apple release in the future. -- status: open -> closed ___ Python tracker <http://bugs.python.org/issue13315> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11278] raw_input() and input() not stripping EOL on win32
New submission from Dave Flogeras : >From the python prompt, raw_input() (2.7.1) and input (3.2.0) behave as >documented (they strip the trailing EOL chars) However the two line test program: x = raw_input() # or input() in 3.2.x print( repr( x )) And then run from the command line prompt, .\test.py, shows 'mytest\r' including the EOL char. -- messages: 129017 nosy: Dave.Flogeras priority: normal severity: normal status: open title: raw_input() and input() not stripping EOL on win32 versions: Python 2.7, Python 3.2 ___ Python tracker <http://bugs.python.org/issue11278> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11278] raw_input() and input() not stripping EOL on win32
Dave Flogeras added the comment: Ok, I'm actually not sure of what I just said. I might not be running the version I think I am, since windows behaves differently when using a program started with extensions vs. started with python. It might actually be that Python 2.7 is correct, but 3.2 is not. -- ___ Python tracker <http://bugs.python.org/issue11278> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
