Thomas W. Barr added the comment:
A fair point. I was thinking that we could query the OS about whatever
filesystem the path is on, but this wouldn't work for a file that hasn't
been created yet.
The issue with extractall() isn't just that it can extract over existing
files, i
Thomas W. Barr added the comment:
Even if we can't fix things for this release, presumably it's not too
late to fix things for 2.7, right?
Yes, there certainly are cases where you might want to have creative
usage of symlinks and stored paths to allow overwriting existing files,
a
Thomas Vander Stichele added the comment:
Attaching a reworked patch of the patch attached in
http://bugs.python.org/issue1169193
This worked for me on f-11, with python 2.6
--
keywords: +patch
nosy: +thomasvs
Added file: http://bugs.python.org/file15383/distutils.bdist_rpm.patch
Thomas Vander Stichele added the comment:
Hi Toshio,
I'd probably also go for the wildcarding, but you'd still need to
'change' the INSTALLED_FILES file to do so, so you'd still use the same
mechanism.
--
___
Python tracker
Thomas Vander Stichele added the comment:
Ok, so this patch can go in as is except for changing .gz to * ?
--
___
Python tracker
<http://bugs.python.org/issue644
Thomas Vander Stichele added the comment:
What do you mean, it's frozen ? Without the patch you're already breaking a
third party tool, namely rpm. What other tool worth caring about that uses
bdist_rpm could possibly get broken by fixing an obvious bug ? Why is it so
impossible
1801 - 1806 of 1806 matches
Mail list logo