Re: [I] Add backward compatibility re-exports and migration strategy for moved server modules [airflow]

2025-06-09 Thread via GitHub 


dosubot[bot] commented on issue #51555:
URL: https://github.com/apache/airflow/issues/51555#issuecomment-2957266467

   
   I couldn't find a list of the specific components moved to `airflow.core.*` 
as referenced in issue #51554. However, I can confirm that Apache Airflow's 
standard approach for backward compatibility is to re-export moved modules at 
their old import paths and issue DeprecationWarnings when those paths are used. 
This ensures all existing imports continue to work for the remainder of the 
current major version, with clear warnings guiding users to update their 
imports. Deprecated paths are typically removed in the next major release, 
following the documented deprecation policy 
([docs](https://airflow.apache.org/docs/apache-airflow/stable/release-process.html)).
   
   If you can provide the list of moved components or clarify which modules are 
affected, I can give more targeted guidance on implementing the re-exports and 
warnings.
   
   
   
   *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
   
   ---
   How did I do? 
[Good](https://app.dosu.dev/response-feedback/60276937-11b0-4655-b7a6-ddedd6872fe5?feedback_type=great_response)
 | 
[Irrelevant](https://app.dosu.dev/response-feedback/60276937-11b0-4655-b7a6-ddedd6872fe5?feedback_type=irrelevant_answer)
 | 
[Incorrect](https://app.dosu.dev/response-feedback/60276937-11b0-4655-b7a6-ddedd6872fe5?feedback_type=incorrect_sources)
 | 
[Verbose](https://app.dosu.dev/response-feedback/60276937-11b0-4655-b7a6-ddedd6872fe5?feedback_type=too_verbose)
 | 
[Hallucination](https://app.dosu.dev/response-feedback/60276937-11b0-4655-b7a6-ddedd6872fe5?feedback_type=hallucination)
 | [Report 
🐛](https://app.dosu.dev/response-feedback/60276937-11b0-4655-b7a6-ddedd6872fe5?feedback_type=bug_report)
 | 
[Other](https://app.dosu.dev/response-feedback/60276937-11b0-4655-b7a6-ddedd6872fe5?feedback_type=other)  [![Join
 
Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot) [!
 [Share on 
X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/airflow/issues/51555)


-- 
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: commits-unsubscr...@airflow.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[I] Add backward compatibility re-exports and migration strategy for moved server modules [airflow]

2025-06-09 Thread via GitHub 


kaxil opened a new issue, #51555:
URL: https://github.com/apache/airflow/issues/51555

   Provide backward compatibility for components moved to `airflow.core.*` 
through re-exports and establish migration timeline.
   
 - Components moved to `airflow.core.*` in separate issue
 - Existing code and providers rely on old import paths
 - Need smooth migration path without breaking changes
   
 ## Success Criteria
 - All existing imports continue to work
 - Clear deprecation warnings guide users to new imports


-- 
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: commits-unsubscr...@airflow.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org