potiuk commented on issue #55524: URL: https://github.com/apache/airflow/issues/55524#issuecomment-3286273031
> Echoing [@jabbera](https://github.com/jabbera) here. There’s no reason why any airflow context variables should collide with user code. They can all be named arbitrarily like __airflow_task_start_date_☺ or something and you would never have problems like these. One could also argue that anyone introducing their argument with "their" namespace. For example prefix it with their business specific prefix: `my_test_start_date` in this case for example. One of the reson reason is that it's historically like that and way easier to use and difficult to change otherwise. Occasional namespace breakage are not worth adding such complexity IMHO. But if you have a way how to introduce it without breaking millions of Dags here and have a good UX, you are absolutely welcome to contribute such change. But I highly doubt it's possible. For now possibly a PR to make error more obvious is a good idea (and also contributions are welcome). -- 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]
