It is very annoying. Take this as an example. 'patch' is a module (library) that is meant to be used from other programs. Therefore it can not (should not) setup handlers for itself.

>>> import patch
>>> patch.PatchSet().parse('7745')
No handlers could be found for logger "patch"

Is it the same for Python 3?

Forgot to mention that bundled NullHandler doesn't work in Python 2.7 and from what I can see it is not covered with tests for this version.

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "patch.py", line 124, in fromstring
    return PatchSet( StringIO(s) )
  File "patch.py", line 196, in __init__
    self.parse(stream)
  File "patch.py", line 512, in parse
    warning("error: no patch data found!")
  File "C:\Python27\lib\logging\__init__.py", line 1152, in warning
    self._log(WARNING, msg, args, **kwargs)
  File "C:\Python27\lib\logging\__init__.py", line 1258, in _log
    self.handle(record)
  File "C:\Python27\lib\logging\__init__.py", line 1268, in handle
    self.callHandlers(record)
  File "C:\Python27\lib\logging\__init__.py", line 1307, in callHandlers
    if record.levelno >= hdlr.level:
AttributeError: type object 'NullHandler' has no attribute 'level'

Nevermind the last message - I was specifying NullHandler as a class, not as an instance.

This is not a valid issue. The approach to use is documented:

http://docs.python.org/2.6/library/logging.html#configuring-logging-for-a-library
http://docs.python.org/2.7/howto/logging.html#configuring-logging-for-a-library

I'd say this is a pretty valid issue with "won't fix" or "workaround available" resolution.

The question - is the same behavior preserved for Python 3?

Python 3 has exactly the same documentation:
http://docs.python.org/3.3/howto/logging.html#configuring-logging-for-a-library