"Fredrik Lundh" <fredrik@pythonware.com> writes: > and what good is that, really? why would the *users* of a > module I've written have to care about this? > > the Py_DEPRECATED approach (and the "grep" tool) is a much > better way to use everybody's time. Your users will care about it because your module fails to compile if the deprecated API is wrapped with Py_DEPRECATED, whereas it continues to compile and run when the warning is produced - the warning is annoying (and really meant for you only), but is the lesser evil. Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4