Taavi Burns added the comment:
I'm not sure my vote means much, but the spec file didn't work for me on CentOS
5 anyway (weird issue with the -dev RPM trying to find "python2.72.7"). I think
I'd prefer a README with suggested places to look for a working spec file than
Taavi Burns added the comment:
The diff against 3.3.
--
Added file: http://bugs.python.org/file28824/python-3.3.spec.diff
___
Python tracker
<http://bugs.python.org/issue17
New submission from Taavi Burns:
Looking at the Misc/RPM/python-X.X.spec files, they seem to be slightly out of
date. Near the top of the file is a config_binsuffix configuration setting that
is "2.6" for both the 2.7 and 3.3 branches!
I suspect that it should be updated with the v
Taavi Burns added the comment:
Gak, sorry, didn't mean to change the status and resolution!
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.
Taavi Burns added the comment:
Ah, yes, I could have been more clear that I wasn't even looking at the source
code itself. :)
Thanks!
--
resolution: fixed ->
status: closed -> open
versions: -Python 3.2, Python 3.4
___
Python tra
Taavi Burns added the comment:
The issue of churn is totally fair.
I'd still advocate for the attached patch, as it's tiny and fixes an
inconsistency between the function signature and the docs that are referring to
that signatur
New submission from Taavi Burns:
The documentation says "**kwds" instead of "**kwargs", which is what the
function signature uses.
I noticed some other (internally-consistent) occurrences in string.rst. Is
there any interest in replacing "**kwds" generally with
