[issue29351] absolute imports for logging

Changes by Vinay Sajip : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bug

[issue29351] absolute imports for logging

Vinay Sajip added the comment: > No, we cannot consider these changes under any circumstances for 2.7 because > ... Well, it would change import behaviour in a backwards-incompatible way, wouldn't it? -- ___ Python tracker

[issue29351] absolute imports for logging

Markus Gerstel added the comment: Yes, this is indeed the same for other stdlib modules, too. Logging is just the first one that came to attention in our investigations. I haven't prepared any other patches yet though, because your answer could easily be "No, we cannot consider these changes u

[issue29351] absolute imports for logging

Vinay Sajip added the comment: There's nothing particular about logging here, is there? Any of the 2.7 stdlib modules will exhibit similar behaviour, since that __future__ import is not in general defined in the stdlib modules, other than in the test suite. --

[issue29351] absolute imports for logging

Changes by Dries Desmet : -- nosy: +dries_desmet ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue29351] absolute imports for logging

Changes by Markus Gerstel : -- nosy: +vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue29351] absolute imports for logging

New submission from Markus Gerstel: Running 'import logging' causes at minimum 46 failing 'open' and 12 failing 'stat' calls because python looks for packages inside python/Lib/logging which will never be there, in particular: sys, os, time, cStringIO, traceback, warnings, weakref, collections