[issue2904] Cross-referencing to a method using an alternate title don't work with add_function_parentheses=True
New submission from Leandro Lucarella <[EMAIL PROTECTED]>: When using cross-references to a method using an alternate title, like :meth:`some title ` and configuration option add_function_parentheses is True, the link is not generated (if this option is False, it works fine. -- assignee: georg.brandl components: Documentation tools (Sphinx) messages: 67023 nosy: georg.brandl, llucax severity: normal status: open title: Cross-referencing to a method using an alternate title don't work with add_function_parentheses=True type: behavior versions: 3rd party __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2904> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2954] [PATCH] Make bisect module functions accept an optional comparison callable
New submission from Leandro Lucarella <[EMAIL PROTECTED]>: bisect module functions should accept a comparison callable to customize the way items are compared to do the binary search. Attached is a patch to the Python implementation of bisect module. -- components: Library (Lib) files: bisect.py.cmp.patch keywords: patch messages: 67271 nosy: llucax severity: normal status: open title: [PATCH] Make bisect module functions accept an optional comparison callable type: feature request versions: Python 2.1.1, Python 2.1.2, Python 2.2, Python 2.2.1, Python 2.2.2, Python 2.2.3, Python 2.3, Python 2.4, Python 2.5, Python 2.6 Added file: http://bugs.python.org/file10420/bisect.py.cmp.patch __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2954> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2954] [PATCH] Make bisect module functions accept an optional comparison callable
Leandro Lucarella <[EMAIL PROTECTED]> added the comment: A key argument (like list.sort) can be useful too (I can make a patch if you like). __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2954> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2954] [PATCH] Make bisect module functions accept an optional comparison callable
Leandro Lucarella <[EMAIL PROTECTED]> added the comment: Is there any way to find the duplicated issue to see the resolution and find out why it has been rejected? Thank you. ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2954> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2295] cPickle corner case - docs or bug?
Leandro Lucarella <[EMAIL PROTECTED]> added the comment: I'm having the same problem here. Error is: cPickle.PicklingError: Can't pickle qos.Device: it's not the same object as qos.Device If I use pickle module, it works fine. If I use cPickle module but with protocol=0, it works fine (protocol=1 or protocol=2 both fail). I'm trying to make a simple example that reproduce the problem, but I couldn't do it yet (small tests seems to work). So for now, I just can only offer the complete source code of my project[1] (see branch "python-bug-2295"). Not that the bug is exposed by the commit b0ef5dd[2], and it's only exposed in the "qos" module (other modules works fine). To see the backtrace it should be enough to download the project (you can download a tarball[3] or use git via git protocol[4] -preferred- or http[5]) and execute ./pymind [1] http://git.llucax.com.ar/?p=software/pymin.git;a=shortlog;h=refs/heads/python-bug-2295 [2] http://git.llucax.com.ar/?p=software/pymin.git;a=commitdiff;h=b0ef5ddfd5b04ecb09a18fb6f253c9f8a7db48a8 [3] http://git.llucax.com.ar/?p=software/pymin.git;a=snapshot;h=f19fc5b4f5eeda18a24b1f5a2d042fd206c9ed0f;sf=tgz [4] git clone git://git.llucax.com.ar/software/pymin.git [5] git clone http://git.llucax.com.ar/git/software/pymin.git -- nosy: +llucax ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2295> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2295] cPickle corner case - docs or bug?
Leandro Lucarella <[EMAIL PROTECTED]> added the comment: I've noted that the problem goes away if I move the pymin/services/* directories (i.e., the packages in pymin/services) to another place (for example, a services directory in the root of the project). I still can't make a simple test to reproduce the problem. ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2295> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3136] [PATCH] logging.config.fileConfig() compulsivly disable all existing loggers
New submission from Leandro Lucarella <[EMAIL PROTECTED]>: When using logging.config.fileConfig() in a large project, with several nested loggers, is very counterintuitive and annoying that this function disable all non-configured-via-fileConfig() loggers, because it forces the config file to configure *all* the loggers there, which makes the file unmaintainable, and throws the beauty of hierarchical loggers to the trash. Attached is a sample patch that adds a new option "disable_existing_loggers" to fileConfig() function (defaulting to True, to make it backward-compatible) to control this behavior. If you like the idea I can update the documentation and add some testcases too. You can see a simple example about the problem and solution here: log.py: http://pastebin.lugmen.org.ar/4204 log.ini: http://pastebin.lugmen.org.ar/4205 without the patch, the output is: logger:DEBUG: log debug logger:INFO: log info logger:WARNING: log warning logger:ERROR: log error logger:CRITICAL: log critical With the patch (and passing disable_existing_loggers=False to fileConfig()) yields this output: logger:DEBUG: log debug logger:INFO: log info logger:WARNING: log warning logger:ERROR: log error logger:CRITICAL: log critical logger.sublogger:DEBUG: sublog debug logger.sublogger:INFO: sublog info logger.sublogger:WARNING: sublog warning logger.sublogger:ERROR: sublog error logger.sublogger:CRITICAL: sublog critical As one could expect when reading the logging module docs: """ getLogger() returns a reference to a logger instance with the specified if it it is provided, or root if not. The names are period-separated hierarchical structures. Multiple calls to getLogger() with the same name will return a reference to the same logger object. Loggers that are further down in the hierarchical list are children of loggers higher up in the list. For example, given a logger with a name of foo, loggers with names of foo.bar, foo.bar.baz, and foo.bam are all children of foo. Child loggers propagate messages up to their parent loggers. Because of this, it is unnecessary to define and configure all the loggers an application uses. It is sufficient to configure a top-level logger and create child loggers as needed. """ -- components: Library (Lib) files: logging.config.disable_existing_loggers.patch keywords: patch messages: 68388 nosy: llucax severity: normal status: open title: [PATCH] logging.config.fileConfig() compulsivly disable all existing loggers versions: Python 2.5 Added file: http://bugs.python.org/file10657/logging.config.disable_existing_loggers.patch ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue3136> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3136] [PATCH] logging.config.fileConfig() compulsivly disable all existing loggers
Leandro Lucarella <[EMAIL PROTECTED]> added the comment: The problem is you can't always do that call before using the loggers. In my case, I get the logging config file via command-line arguments (using optparse), but before I can't even know what logging config file to load, I have log calls. Please reopen the bug, the actual solution is not flexible enough. ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue3136> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3136] [PATCH] logging.config.fileConfig() compulsivly disable all existing loggers
Leandro Lucarella <[EMAIL PROTECTED]> added the comment: Thank you very much ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue3136> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3136] [PATCH] logging.config.fileConfig() compulsivly disable all existing loggers
Leandro Lucarella <[EMAIL PROTECTED]> added the comment: Here is a patch to add some documentation on the new fileConfig() argument. Is not much, but it's better than nothing =) Added file: http://bugs.python.org/file10662/logging.config.disable_existing_loggers.doc.patch ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue3136> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
