Matt Giuca matt.gi...@gmail.com added the comment:
OK since the patches I submitted are now eight months old, I just did an
update and re-applied them. I am submitting new patch files which don't
change anything, but are patches against revision 71822 (should be much
easier to apply).
I'd still
Matt Giuca matt.gi...@gmail.com added the comment:
Full method renaming patch.
--
Added file: http://bugs.python.org/file13756/doc+bytesmethods.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue3565
Martin v. Löwis mar...@v.loewis.de added the comment:
I think this patch is unacceptable for Python 3.1. It is an incompatible
change (removing a method), one would have to deprecate the method to be
removed first. I also agree with Benjamin that a wider-audience approval
of the deprecation
Matt Giuca matt.gi...@gmail.com added the comment:
I agree with that -- too big a change to make now.
But can we please get the documentation patch accepted? It's been
waiting here for eight months with corrections to clearly-incorrect
documentation.
--
Daniel Diniz aja...@gmail.com added the comment:
The doc patch is in scope for the Bug Day.
--
keywords: +easy
nosy: +ajaksu2
stage: - test needed
type: - feature request
versions: +Python 3.1 -Python 3.0
___
Python tracker rep...@bugs.python.org
Antoine Pitrou pit...@free.fr added the comment:
Benjamin, do you think this should be fixed in 3.1?
--
nosy: +benjamin.peterson, pitrou
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue3565
Benjamin Peterson benja...@python.org added the comment:
It would be nice to deprecate the old names in 3.1 and remove them in
3.2, but I think it should get approval on python-dev.
--
assignee: georg.brandl -
___
Python tracker
Matt Giuca matt.gi...@gmail.com added the comment:
Note that, irrespective of the changes to the library itself, the
documentation is out of date since it still uses the old
string/unicode nomenclature, rather than the new bytes/string. I
have provided a separate documentation patch which should
Changes by David W. Lambert lamber...@corning.com:
--
nosy: +LambertDW
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue3565
___
___
Python-bugs-list
Matt Giuca [EMAIL PROTECTED] added the comment:
Can I just remind people that I have a documentation patch ready here
(and has been for about a month)?
Of course the doc+bytesmethods.patch may be debatable and probably too
late to go in 3.0. But you should be able to commit doc-only.patch with
Matt Giuca [EMAIL PROTECTED] added the comment:
A similar issue came up in another bug
(http://bugs.python.org/issue3613), and Guido said:
IMO it's okay to add encodebytes(), but let's leave encodestring()
around with a deprecation warning, since it's so late in the release cycle.
I think
New submission from Matt Giuca [EMAIL PROTECTED]:
A few weeks ago I fixed the struct module's documentation which wasn't
3.0 compliant (basically renaming strings to bytes and unicode to
string). Now I've had a look at the array module, and it's got similar
problems.
Matt Giuca [EMAIL PROTECTED] added the comment:
(Fixed issue title)
--
title: array documentation, method names not 3.0 compliant - array
documentation, method names not 3.0 compliant
___
Python tracker [EMAIL PROTECTED]
Matt Giuca [EMAIL PROTECTED] added the comment:
I renamed tostring/fromstring to tobytes/frombytes in the array module,
as described above. I then grepped the entire py3k tree for tostring
and fromstring, and carefully replaced all references which pertain to
array objects.
The relatively minor
Changes by Matt Giuca [EMAIL PROTECTED]:
Removed file: http://bugs.python.org/file11122/doc+bytesmethods.patch
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3565
___
Matt Giuca [EMAIL PROTECTED] added the comment:
Oops .. forgot to update the array.rst docs with the new method names.
Replaced doc+bytesmethods.patch with a fixed version.
Added file: http://bugs.python.org/file11123/doc+bytesmethods.patch
___
Python
16 matches
Mail list logo
