jscheffl commented on PR #35612: URL: https://github.com/apache/airflow/pull/35612#issuecomment-1811359588
> > The way I’m thinking is `ObjectStoragePath` is long enough for people to want to `from ...` import it, and the name they get there is not specific enough. But `Path` is _so_ vague (it even clashes with pathlib.Path) people will be forced to do a fully qualified import (which is ergonomic enough as long as the import path is short) that eliminates the vagueness of the name. > > Ah you mean allowing both? Sorry, late to the party. Agree on that `ObjectStoragePath` as too many letters (getting an o15h :-D) and `Path` would be great but raises a lot of dis-ambiguation with `pathlib.Path`(so should NOT be done!). My previous favority was to name it `StoragePath` because it might be not solely _Object_-Storage being used. Can be actually "any" Storage, also FileStorage, correct? As `StoragePath` we only have s9h letters and is a compromise between o15h and p2h :-D -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
