Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/208#issuecomment-38415281
They are fully qualified, as there is only only possible path that will
define the package for a given file. For this reason I'm not sure if the
logic behind avoiding relative imports applies here.
There are just breaks placed in to implicitly include things from the
package object of parent packages. I think this is a useful construct to
include system-wide things like logging or type aliases without adding
verbosity to every file in the project.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
