[issue27493] logging module fails with unclear error when supplied a (Posix)Path

Changes by Berker Peksag : -- status: open -> closed ___ Python tracker ___ ___

[issue27493] logging module fails with unclear error when supplied a (Posix)Path

Roundup Robot added the comment: New changeset 5424252ce174 by Berker Peksag in branch 'default': Issue #27493: Fix test_path_objects under Windows https://hg.python.org/cpython/rev/5424252ce174 -- ___ Python tracker

[issue27493] logging module fails with unclear error when supplied a (Posix)Path

Martin Panter added the comment: Windows fails the test: http://buildbot.python.org/all/builders/AMD64%20Windows7%20SP1%203.x/builds/7989/steps/test/logs/stdio == ERROR: test_path_objects (test.test_logging.HandlerTest)

[issue27493] logging module fails with unclear error when supplied a (Posix)Path

Roundup Robot added the comment: New changeset fada654c5f72 by Vinay Sajip in branch 'default': Closes #27493: accepted Path objects in file handlers for logging. https://hg.python.org/cpython/rev/fada654c5f72 -- nosy: +python-dev resolution: -> fixed stage: needs patch -> resolved

[issue27493] logging module fails with unclear error when supplied a (Posix)Path

Vinay Sajip added the comment: > the answer would be "not at all". Not sure about that. If all logging did were to pass the path to lower levels such as open or abspath, that may be true. However, some handlers do path computations (e.g. the rotating file handlers) and so logging would need

[issue27493] logging module fails with unclear error when supplied a (Posix)Path

R. David Murray added the comment: It will be interesting to see how much logging itself needs to be aware of PEP 519 once the support is added to posixpath. ideally, to meet the goals of PEP 519, the answer would be "not at all". @richard: python uses duck typing: if it quacks like a duck,

[issue27493] logging module fails with unclear error when supplied a (Posix)Path

Vinay Sajip added the comment: > We could possibly add PEP 519 support to the logging module for Python 3.6 Seems like a reasonable enhancement for 3.6. -- stage: -> needs patch type: -> enhancement versions: +Python 3.6 -Python 3.5 ___ Python

[issue27493] logging module fails with unclear error when supplied a (Posix)Path

Richard added the comment: Yeah, figured as much. But thanks:) I'm kind of new to Python and was having some problems determining whether this is as it should be, or if it should be improved. After all, I could not find any documentation that states what the permitted variable-types are (for

[issue27493] logging module fails with unclear error when supplied a (Posix)Path

Berker Peksag added the comment: logging module doesn't support Path objects. You need to wrap STATUSLOG_PATH = Path('~/logFiles/Reseller/').expanduser() with str(). We could possibly add PEP 519 support to the logging module for Python 3.6. What do you think, Vinay? -- nosy:

[issue27493] logging module fails with unclear error when supplied a (Posix)Path

New submission from Richard: No idea if I should be reporting this here, but it came with the default installation, so here goes: On a mac, I supplied a basicConfig object to the logging class that contains a PosixPath instance for the "filename" attribute. consequently, it fails with the