Peter Harris added the comment:
Yeah it would make sense to accept any iterable, but I'm only proposing a
documentation fix not a feature enhancement.
--
___
Python tracker
<http://bugs.python.org/is
New submission from Peter Harris:
Documentation on python website says:
xml.etree.ElementTree.iterparse(source, events=None, parser=None)
Parses an XML section into an element tree incrementally, and reports what’s
going on to the user. source is a filename or file object containing XML
Peter Harris added the comment:
Yeah, I know that's what it's supposed to do. It does pop up the list
of names, but then crashes.
It happens no matter what has been input, even on an empty window.
However, if it works for everyone else, maybe I built T
New submission from Peter Harris :
Using Python3.1 built from svn, on RedHat EL4, with Tcl/Tk 8.5 built
from source.
Traceback:
--
File "/usr/mlocal/lib/python3.1/runpy.py", line 122, in
_run_module_as_main
"__main__", fname, loader, pkg_name)
F
Peter Harris <[EMAIL PROTECTED]> added the comment:
As far as I can tell, it is OK now. Thanks!
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
New submission from Peter Harris:
Python 3.0: Use bytes instead of str to construct the binary file,
don't try to .sort a dict's keys().
This patch is a tentative fix - in one place I've had to provide an
encoding from str to bytes and I've guessed UTF-8, which may be O
Peter Harris added the comment:
Also, a couple of instances of assuming dict.keys() is a list, and
trying to use .sort() on them.
Patch attached for both issues.
--
title: pygettext.py syntax error -> pygettext.py py3k errors
Added file: http://bugs.python.org/file9173/pygettext.d
New submission from Peter Harris:
Tools/i18n/pygettext.py contains a syntax error.
On line 665, there is an old u'' string for testing unicode on pre-3.0
python.
It should be OK to remove it.
--
components: Demos and Tools
messages: 59961
nosy: scav
severity: normal
st
New submission from Peter Harris:
line 221 'loating point' -> 'Floating point'.
Also, maybe double-check that __cmp__ method still has special meaning
in 3.0. My last patch took out mention of it because 3.0a1 seems not to
support comparisons using __cmp__ method,
New submission from Peter Harris:
Describe 3.0 comparison behaviour (but not in much detail)
--
components: Documentation
files: datastructures.diff
messages: 56212
nosy: scav
severity: normal
status: open
title: 3.0 tutorial/datastructures.rst patch
versions: Python 3.0
New submission from Peter Harris:
Cleanup (removal of 2.x references, long etc. ). I'm not 100% sure I've
got the rich-comparison stuff correct.
--
components: Documentation
files: stdtypes.diff
messages: 56186
nosy: scav
severity: normal
status: open
title: 3.0 library/st
New submission from Peter Harris:
I think this wording is a little clearer and removes implied reference
to earlier Python versions, while still giving a simplistic
tutorial-level idea of what the MRO is. YMMV, so please disregard if
I've made it worse.
--
components: Document
New submission from Peter Harris:
Remove reference to 'long' in tutorial/introduction.rst.
Patch attached.
--
components: Documentation
files: introduction.diff
messages: 56165
nosy: scav
severity: normal
status: open
title: 3.0 tutorial/introduction.rst mentions 'long&#x
New submission from Peter Harris:
Proposed cleanup patch for tutorial/interpreter.rst
--
components: Documentation
files: interpreter.diff
messages: 56164
nosy: scav
severity: normal
status: open
title: cleanup patch for 3.0 tutorial/interpreter.rst
versions: Python 3.0
14 matches
Mail list logo
