Decision: Use import x for importing packages and modules. Use from x import y where x is the package prefix and y is the module name 3 with no prefix. Use from x import y as z if two modules named relative names in imports. Even if the module is in the same package, use the full package name. This helps prevent unintentionally importing a package twice. Packages link￿ Import each module using the full harder to deploy code because you have to replicate the package hierarchy. Decision: All new code should import each module by its full package name. Imports should be as follows: # Reference in code

structure A source file consists of, in order: 1. License or copyright information, if present 2. Package statement 3. Import statements 4. Exactly one top-level class Exactly one blank line separates each in a file, it belongs here. 3.2 Package statement The package statement is not line-wrapped. The column limit (Section 4.4, Column limit: 100) does not apply to package statements. 3.3 Import statements (for example, a long URL in Javadoc, or a long JSNI method reference). 2. package and import statements (see Sections 3.2 Package statement and 3.3 Import statements). 3. Command lines in a comment that

Technology, WS 2021/22 SIGMOD Reproducibility Process  Overview  Accepted papers can submit package, verified by committee  ACM Results Replicated / ACM Artifacts Available labels  Most Reproducible