got a great suggestion from kelsey blair who works on python at twitter to: - if a dependency spec in a BUILD file or on the command line matches case-insensitively (and/or by levenshtein/edit distance?), - raise an error that points to the correct file or target spec @hundreds-father-404 and anyone else: do you have thoughts on this proposed feature? we're not planning to try to backport this, it would just be a new pants feature.

We actually do this for

!

ignores now: https://github.com/pantsbuild/pants/blob/master/src/python/pants/engine/internals/graph.py#L612

hm yes. the extension of this (which would be easier to write) would be some sort of lint to potentially warn on incorrectly capitalized imports in python source files. not sure if mypy does this already

that’s probably less of a concern than in general giving a good error message on a missing import when using dep inference

dep inference no-ops when we can’t infer a dep or when there are >1 owner for that import

are we planning to modify that behavior later? i would like it to just error out in that case maybe

Not planning on it. Part of the thinking is that you will already get an error from

ModuleNotFoundError

and can then add an explicit dep Generally, dep inference is written to be as conservative as possible. We’d rather have false negatives than false positives

Out of curiosity, is the case-insensitively bit working around APFS defaults of case insensitivity?

all of that aligns with my goals, except we error at build time instead of maybe erroring at runtime, if the failing module is actually loaded

Aha. The feature might be good but also that's a Python thing too. You could also edit the requirement.txt to use all lowercase and that would work since these project names are normalized per spec.

thank you i didn't remember which names came from where