Possible package name conflict between TTU provider and new Teradata provider #5
Description
Teradata just recently released an official provider package, which was merged into the Airflow repo within the past week. I notice that the PyPI package name they assigned is apache-airflow-providers-teradata, which is also the name of this TTU provider.
I first came across this while following Teradata's quickstart guide, and finding the package I got from pip didn't appear to be the same one they were documenting. The package name is also referenced directly in the docs for their provider.
It seems like it would be desirable to avoid this ambiguity, but I'm not honestly sure what action should be taken, on your end or theirs. eg, I don't know if PyPI supports renaming existing packages, if you wanted to -- it seems to me that something like apache-airflow-providers-ttu could make sense and follow the typical conventions, as it matches the inner Python module name. But I thought as the maintainer, you might want to be aware in any event.
Apologies if this has already been logged somewhere -- didn't see it.