I think the reason is the same as why we add `from __future__ import 
absolute_import` elsewhere - to explicitly disable implicit intra-package 
import behavior in Python 2 for forward-compatibility with Python 3. 
@RobbeSneyders, were some tests affected by this?

Related:
http://python-future.org/imports.html
https://www.python.org/dev/peps/pep-0302/

[ Full content available at: https://github.com/apache/beam/pull/6424 ]
This message was relayed via gitbox.apache.org for [email protected]

Reply via email to