[issue21944] Allow copying of CodecInfo objects

New submission from Robert Lehmann: CodecInfo objects as retrieved from codecs.lookup currently throw an exception when trying to copy or pickle them. I have attached a patch with a fix and tests. -- components: Library (Lib) files: copy_codecinfo.patch keywords: patch messages

[issue14961] map() and filter() methods for iterators

Robert Lehmann added the comment: Your proposal seems two-fold: (a) make map/filter lazy and (b) have them as methods instead of functions. It seems Tim borrowed Guido's time machine and already implemented (a) in Python 3.x, see http://docs.python.org/py3k/library/functions.html#ma

[issue13435] Copybutton does not hide tracebacks

New submission from Robert Lehmann : The recently added copybutton.js (r18bbfed9aafa) does not work with the 2.7 docs since they are deployed with JQuery 1.2 (which is shipped with Sphinx 0.6). Copybutton is an unobtrusive Javascript feature which adds a little button to all doctests that

[issue12325] regex matches incorrectly on literal dot (99.9% confirmed)

Robert Lehmann added the comment: I can not reproduce either of your findings. Could you provide us with your version information? re version 2.2.1, _sre 2.2.2, Python 2.6.6, Debian sid here. Also tested with Python 2.7.2rc1 (same RE). >>> import re >>> re.compile(r&q

[issue10576] Add a progress callback to gcmodule

Robert Lehmann added the comment: A few issues I'd like to raise: (1) Multiple callback chains. Is there any code in your existing use case of GC callbacks where you don't check for the phase argument and follow different code paths depending on it? If not, having two callb

[issue10562] Change 'j' for imaginary unit into an 'i'

Robert Lehmann added the comment: > I wonder whether there are many examples where scientific data is written in > a form that Python's complex() constructor couldn't currently read, but would > be able to read if it accepted 'i' in place of 'j'. I co

[issue10598] curses fails to import on Solaris

Robert Lehmann added the comment: I have attached a fix and a regression test. -- keywords: +patch nosy: +lehmannro Added file: http://bugs.python.org/file19903/issue10598.patch ___ Python tracker <http://bugs.python.org/issue10

[issue9042] Gettext cache and classes

Robert Lehmann added the comment: Wouldn't constructing the key as a tuple of (class_, mofile) be much cleaner than making up an artificial key? -- nosy: +lehmannro ___ Python tracker <http://bugs.python.org/i

[issue1766304] improve xrange.__contains__

Robert Lehmann added the comment: Thanks for your feedback. I added a few tests and changed the bits you criticized. -- Added file: http://bugs.python.org/file14945/range.patch ___ Python tracker <http://bugs.python.org/issue1766

[issue1766304] improve xrange.__contains__

Robert Lehmann added the comment: I revised the patch for Python 3.1 and added notices to Misc/NEWS and the range documentation. (Changing Type to resource usage.) -- nosy: +lehmannro type: feature request -> resource usage Added file: http://bugs.python.org/file14939/range.pa

[issue5483] [PATCH]Add FastDbfilenameShelf: shelf nerver sync cache even when writeback=True

Robert Lehmann added the comment: I addressed the other bug you were experiencing in issue6932. -- ___ Python tracker <http://bugs.python.org/issue5483> ___ ___

[issue6932] Open shelves fail when Python exits

Changes by Robert Lehmann : -- keywords: +patch Added file: http://bugs.python.org/file14913/shelve-warning.patch ___ Python tracker <http://bugs.python.org/issue6

[issue6932] Open shelves fail when Python exits

New submission from Robert Lehmann : I'm reopening issue5483 by Zhigang Wang (zhigang) as a separate bug. Shelves that are still open when Python terminates will try to sync. If writeback=True, this pickles cached items. In this example, serialization of Test() re-imports __main__, whi

[issue5754] Shelve module writeback parameter does not act as advertised

Robert Lehmann added the comment: I think you're misquoting Python's shelve module documentation in your first sentence. The documentation says: "By default modified objects are written only when assigned to the shelf [...]. If the optional writeback parameter is set to Tr

[issue5483] [PATCH]Add FastDbfilenameShelf: shelf nerver sync cache even when writeback=True

Robert Lehmann added the comment: If I understand you correctly, your proposal is the following: use Shelf.cache to cache *all* objects instead of only keeping live references. Your patch retains the cache forever instead of purging it on sync. (All these changes only apply with writeback=True

[issue6916] Remove deprecated items from asynchat

New submission from Robert Lehmann : The patches in issue1736190 deprecated fifo and simple_producers. These are safe for removal in Python 3.0. I attached a patch purging fifo and simple_producers from py3k code and tests. The docs are mostly trivial as well but also touched by my other issue

[issue6911] Document changes in asynchat

Robert Lehmann added the comment: I found another bug: async_chat.push still talks about automatically creating a simple_producer, which is no longer true. I added a fix to the patch. -- Added file: http://bugs.python.org/file14893/asynchat-docs.patch

[issue6911] Document changes in asynchat

Robert Lehmann added the comment: Excuse me -- fifo and simple_producer are indeed documented and need a deprecation notice. New patch attached (plus reworded paragraph about async_chat.__init__). -- Added file: http://bugs.python.org/file14889/asynchat-docs.patch

[issue6911] Document changes in asynchat

New submission from Robert Lehmann : asynchat.async_chat grew a _collect_incoming and a _get_data method in 2.6. The constructor has been extended to conform to asyncore.dispatcher's. This should be documented. Apart from that, fifo and simple_producer have been deprecated

[issue6908] Minor markup error in hashlib docs

New submission from Robert Lehmann : The documentation for hashlib.hash.digest_size/block_size (notice the hash) renders as documentation for hashlib.*_size, which does not exist. Fixed by explicitly declaring membership; patch attached. -- assignee: georg.brandl components

[issue6574] List the __future__ features in a table

Changes by Robert Lehmann : Added file: http://bugs.python.org/file14886/future.patch ___ Python tracker <http://bugs.python.org/issue6574> ___ ___ Python-bugs-list mailin

[issue6574] List the __future__ features in a table

Robert Lehmann added the comment: Implemented proposed changes. Additionally, I'd change line 13 to state either "future statements" or "`future`:ref:" instead of "future_statements", which does not make sense in normal, unmarked text. -- Added fil

[issue6574] List the __future__ features in a table

Robert Lehmann added the comment: I composed a list of __future__ features and linked the respective PEPs. Even though the language reference would be a better place to store such general information (being PEP'd and all) I found the library reference's __future__.py documentati

[issue6105] json.dumps doesn't respect OrderedDict's iteration order

Robert Lehmann added the comment: This only seems to be the case with the C implementation of json (_json). >>> json.encoder.c_make_encoder = None >>> json.dumps(OrderedDict(items)) '{"one": 1, "two": 2, "three": 3, "four":

[issue6019] Minor typos in ctypes docs

New submission from Robert Lehmann : There are a few errors in the ctypes documentation covering function calls using the example of `libc.printf`. It's basically just typos but they are really confusing when trying to understand the examples. Patch to trunk is attached. Corrections s

[issue5034] itertools.fixlen

Robert Lehmann added the comment: When I started writing this patch this was actually what I intended. But having ``fixlen(range(3), 2)`` return 0 1 2 struck me as odd. Renaming the function to `pad` would help there indeed. It depends on which use case is more common: either fixing an

[issue5034] itertools.fixlen

New submission from Robert Lehmann : As raised recently on python-ideas [1]_, an itertools method fixing iterators to a certain length might be handy (where fixing is either cutting elements off or appending values). I appended a patch implementing this feature in Python/C, unit tests and

[issue4059] sqlite3 docs incomplete

New submission from Robert Lehmann <[EMAIL PROTECTED]>: The sqlite3 documentation misses Row and Cursor.description. Additionally it does not use the best markup in all places (missing links, basically, and forgotten .. class:: statements). A patch is attached. -- as

[issue4058] markup in What's New in 2.6

New submission from Robert Lehmann <[EMAIL PROTECTED]>: The markup in the Doc/whatsnew/2.6.rst document is somewhat messy in some places. I fixed indentation (spaces to tabs -- made some things readable in the docutils output but not in the source), code samples ("->" notati

[issue3669] sqlite3.Connection.iterdump docs pythonicity

New submission from Robert Lehmann <[EMAIL PROTECTED]>: The `sqlite3` docs are a little unpythonic. When using `str.join` on `Connection.iterdump`, the example in the docs manually unpacks the generator using a LC. I propose this'd be improved. Patch attached. Same applies to th

[issue2816] Quote-type recognition bug

Robert Lehmann <[EMAIL PROTECTED]> added the comment: It seems "single-quoted" doesn't mean the actual quotation sign used but rather how many you used. Compare the multiline triple quote syntax: $ cat foo.py """bar $ python foo.py File "foo.py",

[issue2529] list/generator comprehension parser doesn't match spec

Robert Lehmann <[EMAIL PROTECTED]> added the comment: Your example is parsed as [e for i in (j in ['a','b','c'])] and since `j` is not defined, you get a NameError. If it was defined, you would still be iterating a boolean (which is not defined). Grammatica

[issue2201] Documentation Section 4.4

Robert Lehmann added the comment: In the example code from the tutorial you gave, there was still a comma separator between the string 'equals' and the reference `x`. This is missing when you entered the code, that's why Python is throwing an exception there. -- n

[issue2120] broken links in advocacy HOWTO

Robert Lehmann added the comment: Right, the second link requires a tilde -- I just tried the first one (which works without). You should change all lines to be 80 characters wide maximum, though (can quickly be done by any commiter, not worth a new patch IMO). The dash thing looks okay

[issue2120] broken links in advocacy HOWTO

Robert Lehmann added the comment: Aye, this patch removes the spaces and re-aligns the paragraph of the latter link. -- nosy: +lehmannro Added file: http://bugs.python.org/file9434/spaces.patch __ Tracker <[EMAIL PROTECTED]> <http://bugs.p

[issue1758] Wrong link in documentation

Robert Lehmann added the comment: This problem has been removed in the current version of the documentation (http://docs.python.org/dev/install/index.html) -- old docs aren't updated. It has an own section now (http://docs.python.org/dev/bugs.html). Issue can be closed. --