Let's assume you're writing Go, Python, or any other language in which `import` is a reserved keyword. Let's assume also that you're writing a new package, whose purpose is to "import" data.
What do you name this package?
Our team went through this exercise semi-recently, and we're curious about how everyone else would think about it. Here's a (non-exhaustive) list of options we considered: imports, ingest, dataimport, ímport, impørt.
What does "importing data" exactly mean in your context? What is special about this data that your package can do something useful that's specific to the data? What is special about the importing task that your users wouldn't rather just `with open(filename) as f:`?
Not rhetorical questions. You presumably have real reasons to create the package; meditating on them will bring you closer to an understanding. The reason that naming things is one of the "hard CS problems" is that it requires actually paying attention to your own work and a solution can't be looked up elsewhere.
Agreed, I like `ingest` as well. It does somewhat violate principle d), but the other solutions violate more of those. And to your point, they're principles, not rules.
The misspellings of import sound like they’d be a nightmare. Something like ingest sounds much better.
To come up with other names I’d probably think about additional context. What is being imported, how is it being done? Can those concepts be spun into a name?
