Scott Leerssen added the comment:
I just assumed it was fixed based on the 2.7.12 release notes. I missed the
comment on msg277117 which describes the same problem, so clearly this is a
known issue and I'll look forward to seeing the fix in 2.7.13. Thanks
Scott Leerssen added the comment:
It looks like there may still be an issue in Python 2.7.12 on Windows 2008 R2
(Datacenter Edition). On an Amazon instance (tried t2.micro and m4.large) we
are seeing the following:
In 2.7.11 (correct)
C:\Users\Administrator>python
Python 2.7.11 (v2.7
Scott Leerssen added the comment:
Regarding whether or not to include the fix in 2.7, I'd like to suggest that it
be included there as well. It will be quite some time before the project on
which I work moves to Python 3, and I just hit the same issue.
--
nosy: +Scott.Leerssen
New submission from Scott Leerssen sleers...@gmail.com:
I'm opening this as a continuation of issue10761 since it was closed as fixed,
and there's a bit more work to do there.
The fix for issue10761 was incomplete. It did not handle the case where the
symlink being overwritten did
Scott Leerssen sleers...@gmail.com added the comment:
It turns out that my fix was at least one byte short of complete. If the
target pathname is a broken symlink, os.path.exists() returns False, and the
OSError is raised. I should have used os.path.lexists(). Also, I believe the
same
Scott Leerssen sleers...@gmail.com added the comment:
here is a diff of a better fix based on the previous patch:
Index: tarfile.py
===
--- tarfile.py (revision 49758)
+++ tarfile.py (working copy)
@@ -2239,12 +2239,14
Scott Leerssen sleers...@gmail.com added the comment:
tests that verify the bug/fix:
def test_extractall_broken_symlinks(self):
# Test if extractall works properly when tarfile contains symlinks
tempdir = os.path.join(TEMPDIR, testsymlinks)
temparchive
Scott Leerssen sleers...@gmail.com added the comment:
oops... I left some of my local edits in those tests. be sure to fix the
TEMPDIR use if you add these into the tarfile tests.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
Scott Leerssen sleers...@gmail.com added the comment:
It happens on RedHat and CentOS 5, but I suspect it would happen on any Unix
variant. Here's a test that exacerbates the issue:
#
# test_tarfile.py
#
# Description:
# tests for python tarfile module
#
# $Id$
#
import os
import
Scott Leerssen sleers...@gmail.com added the comment:
I just hit the same issue. This seems to work:
Modified:Lib/tarfile.py
===
---Lib/tarfile.py 2011-04-26 20:36:33 UTC (rev 49502)
+++Lib/tarfile.py 2011-04-26 21:01
On Apr 13, 2005, at 12:41 PM, [EMAIL PROTECTED] wrote:
From: Scott Leerssen [EMAIL PROTECTED]>
Date: April 13, 2005 12:29:35 PM EDT
To: python-list@python.org
Subject: unstatisfied symbols building Python 2.4.1 on HP-UX 10.20
I'm trying to build Python 2.4.1 on HP-UX 10.20 and
I'm trying to build Python 2.4.1 on HP-UX 10.20 and get the following
during linking:
/usr/ccs/bin/ld: Unsatisfied symbols:
PyThread_acquire_lock (code)
PyThread_exit_thread (code)
PyThread_allocate_lock (code)
PyThread_free_lock (code)
PyThread_start_new_thread (code)
12 matches
Mail list logo
