[issue17453] logging.config.fileConfig error

2013-05-21 Thread Łukasz Langa
Changes by Łukasz Langa luk...@langa.pl: -- resolution: - works for me stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17453 ___

[issue17453] logging.config.fileConfig error

2013-04-05 Thread Hervé Coatanhay
Hervé Coatanhay added the comment: Yes it does. I fixed my configuration generation and everything is running as expected. Thanks. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17453

[issue17453] logging.config.fileConfig error

2013-04-02 Thread Łukasz Langa
Łukasz Langa added the comment: Treating as empty values was a bug in configparser pre 3.2 (it made it impossible to store as a value). Simply change [section] option = to [section] option = Does that solve your problem? -- ___

[issue17453] logging.config.fileConfig error

2013-03-30 Thread Vinay Sajip
Changes by Vinay Sajip vinay_sa...@yahoo.co.uk: -- nosy: -vinay.sajip ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17453 ___ ___

[issue17453] logging.config.fileConfig error

2013-03-30 Thread Éric Araujo
Éric Araujo added the comment: Unless the 2.7 configparser docs mention that two quotes are parsed as an empty string, I think this is an implementation accident, should not be relied upon and 3.x should not be changed to match it. Values in configparser files are not Python strings: we

[issue17453] logging.config.fileConfig error

2013-03-29 Thread Vinay Sajip
Vinay Sajip added the comment: Removing myself from nosy, as it appears to be a ConfigParser issue. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17453 ___

[issue17453] logging.config.fileConfig error

2013-03-19 Thread Łukasz Langa
Changes by Łukasz Langa luk...@langa.pl: -- assignee: - lukasz.langa versions: +Python 3.2, Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17453 ___

[issue17453] logging.config.fileConfig error

2013-03-18 Thread Hervé Coatanhay
New submission from Hervé Coatanhay: In python 2.7 this code works: import logging.config import StringIO a=[loggers] ... keys = root ... [logger_root] ... handlers = ... [formatters] ... keys = ... [handlers] ... keys = ... logging.config.fileConfig(StringIO.StringIO(a)) whereas in

[issue17453] logging.config.fileConfig error

2013-03-18 Thread Ned Deily
Changes by Ned Deily n...@acm.org: -- nosy: +vinay.sajip ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17453 ___ ___ Python-bugs-list mailing list

[issue17453] logging.config.fileConfig error

2013-03-18 Thread Vinay Sajip
Vinay Sajip added the comment: What is your intent in setting up a configuration like that? How do you expect it to behave? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17453 ___

[issue17453] logging.config.fileConfig error

2013-03-18 Thread Radu Voicilas
Radu Voicilas added the comment: Even though it seems kind of weird to have all those keys set to the empty string, I still think that configparser should handle this case, which might be relevant for some other uses cases (not logging configs). The attached patch should take care of this.

[issue17453] logging.config.fileConfig error

2013-03-18 Thread Hervé Coatanhay
Hervé Coatanhay added the comment: My complete configuration is this: [loggers] keys = app_admin,root,app_test_py3 [logger_root] handlers = [formatters] keys = app_admin,app_test_py3 [handlers] keys = app_admin,app_test_py3 [logger_app_admin] propagate = 1 handlers = app_admin qualname =

[issue17453] logging.config.fileConfig error

2013-03-18 Thread R. David Murray
Changes by R. David Murray rdmur...@bitdance.com: -- nosy: +lukasz.langa ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17453 ___ ___