jorisvandenbossche commented on pull request #8255: URL: https://github.com/apache/arrow/pull/8255#issuecomment-704931662
> I think we use FutureWarning instead of DeprecationWarning? (because the latter is silent by default) I have a slight preference for using DeprecationWarning here, at first. Reasoning: DeprecationWarning is still visible if you are using the functionality directly (eg if you call `pa.serialize()` yourself in an interactive environment or a main script, you will see it by default, since Python 3.7 or so), but not visible if you are using some library that is using the deprecated functionality. This gives developers of libraries using this functionality the chance to fix those warnings, before their users see warnings they cannot do anything about. My idea was then to bump it from DeprecationWarning to FutureWarning in the next release, for example. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
