feluelle commented on PR #25785: URL: https://github.com/apache/airflow/pull/25785#issuecomment-1221253655
I totally agree with that breaking changes are not always easy to identify, but in my opinion we are on a much safer side when we define public as being the only user exposed access level and we see internal and private as not.. I personally have never used any private or internal function from an external python library before. If I use it I would comment it and pin the version. And I truly believe that this is and should be the standard. Also I see "Internal" as being internal to the library - not potential being external. What is the problem of using public instead of internal? I think it makes sense that move the discussion to the mailing list. -- 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]
